Expand Configuration and Management Manual (G06.24+)

Expand Configuration and Management Manual—523347-008
2-1
2 Expand Overview
The Expand subsystem enables you to connect as many as 255 geographically
dispersed NonStop servers to create a network with the reliability, capacity to preserve
data integrity, and potential for expansion of a single NonStop server.
This section provides a high-level overview of the Expand subsystem by describing the
following major features and capabilities:
•
Network Transparency on page 2-1
•
Multiple Communications Environments on page 2-5
•
Distributed Control on page 2-7
•
Automatic Message Routing on page 2-7
•
Fault-Tolerant Operation on page 2-8
•
Network Management on page 2-9
•
Online Expansion and Reconfiguration on page 2-10
•
Network Security on page 2-11
Network Transparency
To a user or an application, every server in an Expand network appears to be part of a
single server. When accessing a file or other resource on a server in an Expand
network, a user or an application does not need to know which route to take to reach
the destination or whether the destination is local or remote.
Interactive Access
When accessing a remote file or another resource interactively on an Expand network,
you use the same command or utility that you would normally use to perform the task
on your local server. For example, if you wanted to use the File Utility Program (FUP)
DUP command to copy a file named file1 in volume $myfiles, subvolume
subvol1, to a file named file2 in volume $yrfiles, subvolume subvol2, on your
local server, you would use the following command:
>fup dup $myfiles.subvol1.file1,$yrfiles.subvol2.file2
If you wanted to copy the same file to a remote server called \remote, you would use
the following command:
>fup dup $myfiles.subvol1.file1,\remote.$yrfiles.subvol2.file2
In most cases, the only difference between accessing remote and accessing local
resources is that you must specify the name of the remote server when accessing a
remote resource.