In the source and target relationship, the source server
is defined as a client node of the target server. To set up this relationship,
a number of steps must be performed at the two servers.
About this task
In the following example (illustrated in Figure 1), the source server
is named TUCSON and the target server is named MADERA.
- At Tucson site:
- Define the target server:
- MADERA has a TCP/IP address of 127.0.0.1:1845
- Assign the password CALCITE to MADERA.
- Assign TUCSON as the node name by which the source server TUCSON
will be known by the target server. If no node name is assigned, the
server name of the source server is used. To see the server name,
you can issue the QUERY STATUS command.
- Define a device class for the data to be sent to the target server.
The device type for this device class must be SERVER, and the definition
must include the name of the target server.
- At Madera site:
Register the source server as a client
node. The target server can use an existing policy domain and storage
pool for the data from the source server. However, you can define
a separate management policy and storage pool for the source server.
Doing so can provide more control over storage pool resources.
- Use the REGISTER NODE command to define the source server as a
node of TYPE=SERVER. The policy domain to which the node is assigned
determines where the data from the source server is stored. Data from
the source server is stored in the storage pool specified in the archive
copy group of the default management class of that domain.
- You can set up a separate policy and storage pool for the source
server.
- Define a storage pool named SOURCEPOOL:
define stgpool sourcepool autotapeclass maxscratch=20
- Copy an existing policy domain STANDARD to a new domain named
SOURCEDOMAIN:
copy domain standard sourcedomain
- Assign SOURCEPOOL as the archive copy group destination in the
default management class of SOURCEDOMAIN:
update copygroup sourcedomain standard standard type=archive
destination=sourcepool
- After issuing these commands, ensure that you assign the source
server to the new policy domain (UPDATE NODE) and activate the policy.
Figure 1. Communication configuration
for virtual volumes