Administrator's Guide

Setting Up Source and Target Servers

In the source/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:

• At the Source Server:

  1. Define the target server by using the DEFINE SERVER command. The command example below, does the following:

     • Defines a target server named TARGET1

     • Assigns to TARGET1 the TCP/IP address 9.115.2.223:1919

     • Assigns to TARGET1 the password CACTUS.

     • Assigns ARIZONA as the node name by which the source server will be known at 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 server target1 commmethod=tcpip password=cactus
     hladdress=9.115.2.223 lladdress=1919 nodename=arizona
     

  2. 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. For example, to define a device class named TARGETCLASS, issue the following command:

     define devclass targetclass devtype=server servername=target1
     

• At the Target Server:

  You must 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.

  1. 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.

     For example, to define the source server as a node named ARIZONA with a password of CACTUS (the values assigned in the DEFINE SERVER command), issue the following command:

     register node arizona cactus domain=standard type=server 
     

  2. If you choose, you can set up a separate policy and storage pool for the source server. Ensure that the REGISTER NODE command assigns the source server to the new policy domain. Here is an example:

     1. Define a storage pool named SOURCEPOOL:

        define stgpool sourcepool autotapeclass maxscratch=20
        

     2. Copy an existing policy domain STANDARD to a new domain named SOURCEDOMAIN:

        copy domain standard sourcedomain
        

     3. Assign SOURCEPOOL as the archive copy group destination in the default management class of SOURCEDOMAIN:

        update copygroup sourcedomain standard standard type=archive
          destination=sourcepool