Table 49 Required Configuration Files (HyperSwap) (continued)
RemarksDescriptionItem
Set this item before starting a copy
operation.
The following route lists are required:Route list definition file and command
device definition file
• A route for normal operations
From the local storage system to
the remote storage system
The name of the route list for monitoring
HyperSwap must be different from the
name of the route list for working
• A route for local storage system
failures
From the primary storage system to
the remote storage system
around local storage system troubles.
Do not use these route lists at the same
time.
• Routes for primary host failures
From the remote storage system to
the primary storage system
From the remote storage system to
the local storage system
This item is not necessary if you use
Remote Web Console to set up logical
paths.
The following path sets are required
for logical paths.
Path set definition files
• An inter-control unit logical path
(bidirectional) must be established
between the primary and local
storage system.
• An inter-disk controller logical path
(bidirectional) must be established
between the primary and remote
storage system.
• An inter-disk controller logical path
(bidirectional) must be established
between the local and remote
storage system.
Preparing the configuration files (HyperSwap)
Table 50 (page 179) shows how to prepare the configuration files at each site.
Table 50 How to Prepare the Configuration Files at Each Site (HyperSwap)
How to PrepareContentsFile Type
On the Secondary SiteOn the Primary Site
Transfer from the primary
site
Perform a local scanThe primary site
configuration
Disk configuration
definition file
Perform a local scanTransfer from the secondary
site
The secondary site
configuration
Defining a 2DC configuration with HyperSwap and Cnt-Ac J Z 179