Table 2. Server System Configuration Information (continued)
Server System
Record the names of the client nodes on which you will install and configure the storage agent. This
information will be needed when you register the nodes, set the policy for them, and place any needed
restrictions on them. See “Client Node Information” for further details.
Obtain Device Information

Note: If you are configuring a FILE Library, you do not need to obtain device

information. Proceed to “Step 3. Configuring Devices for the Storage Agent
to Access” on page 26.
On the system where the storage agent is installed, obtain device (tape and disk)
information. You will use the device information from the storage agent when
defining paths for the server that functions as the library manager in “Step 3.
Configuring Devices for the Storage Agent to Access” on page 26. In the z/OS
environment, you would use the information for an AIX server because the z/OS
servers cannot function as library managers.
On the system where the storage agent is installed, use SMIT and issue the
following commands to obtain information about tape devices.

v For IBM devices:

Select Devices -> Tape Drive -> List All Defined Tape Drives

v For other devices:

Devices -> Tivoli Storage Manager -> Optical R/W Disk Drive or Tape Drive or
Library/Medium Changer -> List All Defined devices
Client Node Information
Because you will need to take into account node registration and policy
information, determine the client nodes that will be using the storage agent. In a
typical environment, however, a storage agent is only used by a single node: the
client node residing on the same system as the storage agent. Consider these
recommendations when determining which client nodes will use the storage agent:

v Yo u will need to verify that those nodes are registered. If they are not, you will

need to register them.

v Yo u will also need to verify the policy information for those nodes. The copy

group for backup and archive must point to a storage pool that has a LAN-free
path for a particular storage agent. LAN-free paths exist when drive paths are
defined and available for the storage pool. The procedure in the installation and
configuration chapter will create such a path, thus allowing LAN-free data
transfer for the node. You can issue the VALIDATE LANFREE command on the
server to view the destinations that are capable of LAN-free data movement.

Detailed information about this command is available in the Administrator’s

Reference.

v After you have verified the registration and policy information for the nodes,

you can place restrictions on when a node can use the LAN-free path.
Chapter 2. Planning 15