Tivoli Header

Managed System for SAN Storage Agent User's Guide


Establishing Communications among Client, Storage Agent, and Server

For a pictorial representation of what you will accomplish during the next two steps, see Figure 5 .

Step 2. Client System

The sections in this step describe installation of TSM client, API, and storage agent software.

Install or Upgrade the Client and API Software

  1. Check that the client system meets the prerequisites for client software. See the User's Guide for the client. Install the client software and API if it is not already installed on the system, or upgrade the software to the latest level as necessary. The latest levels can be downloaded from the Tivoli Storage Manager Web site at http://www.tivoli.com/support/storage_mgr/tivolimain.html.
  2. Modify the TSM options file (dsm.sys).

    For information about the dsm.opt and dsm.sys files, see Backup-Archive Installation and User's Guide.

    1. Edit the dsm.sys file to specify the communications method between the TSM client and server. For example:
      COMMmethod TCPip
      TCPServeraddress tsmsrver.tucson.ibm.com
      TCPPort 1502
      
      Note:
      For illustrative purposes a tcpport of 1502 is used in the examples, however, the default tcpport is 1500.
    2. Edit the dsm.opt file to specify the server name of the dsm.sys stanza edited in step a. For example:
      servername tsmsrver
      
    3. Add the following options to the same dsm.sys stanza edited in step a. These options specify that the client will use SAN-attached devices; when the path is available, during backup, restore, archive, and retrieve processing.
      enablelanfree yes
       
      LANFREECommmethod TCPIP
      LANFREETCPPort 1500
      

      or

      LANFREECommmethod SharedMem
      LANFREESHMPORT 1510
       
      
  3. If your are using a TDP client, configure the API by performing the following procedure:
    1. Set up the environment variables. The TSM API uses unique environment variables to locate files.
      • DSMI_CONFIG is the fully qualified name for the client user option file.
      • DSMI_DIR points to the path containing dsm.sys, dsmtca, and the subdirectory en_US.
      • en_US subdirectory must contain dsmclientV3.cat.
      • DSMI_LOG points to the path for the dsierror.log file

      The following are examples on how to set up these environment variables.

      export DSMI_CONFIG=/usr/tivoli/tsm/client/api/bin/dsm.opt
      export DSMI_DIR=/usr/tivoli/tsm/client/api/bin
      export DSMI_LOG=/home/user_a/logdir 
      
      Note:
      The quickest method to set the environment variables is to add these variables to the user's .profile file.
    2. Edit the dsm.sys file to specify the communications method between the TSM API and server.
      1. If a dsm.sys file does not exist in the directory specified by DSMI_DIR, create a symbolic link to the dsm.sys file in the TSM client installation directory. For example:
        ln -s /usr/tivoli/tsm/client/ba/bin/dsm.sys /usr/tivoli/tsm/client/api/bin/dsm.sys
        
      2. Edit an existing stanza in the dsm.sys file or create a new stanza to specify the options for connecting to the TSM server. For example:
        SErvername         tsmsrver
        COMMmethod         TCPip
        TCPPort            1502
        TCPServeraddress   tsmsrver.tucson.ibm.com
        
        Note:
        For illustrative purposes a tcpport of 1502 is used in the examples, however, the default tcpport is 1500.

        It is assumed that the dsm.sys file is controlled by the system administrator. The Tivoli Storage Manager server administrator should supply the name and IP address of the Tivoli Storage Manager server, as well as the node name and password.

    3. Edit the dsm.opt file specified by the DSMI_CONFIG environment variable to specify the server name of the dsm.sys stanza edited in the previous step. For example:
         servername tsmsrver
      

Install and Configure the Storage Agent

Note:
The Storage Agent should not be installed on the same machine as the TSM server.

On the same system as the client, install the storage agent. The default installation directory is /usr/tivoli/tsm/StorageAgent/bin.

The instructions in this section are shown using the Software Management and Installation Tool (SMIT). You can also use the Install and Update Software Manager (installm).

Note:
Throughout this procedure, /dev/cd0 is used for CD-ROM. This may be different in your environment. Loading the storage agent files can take several minutes.

Installation using the SMIT procedure:

  1. Record the following information. This information is required throughout the remainder of this procedure.
  2. Log in as the root user.
  3. Load the storage agent CD-ROM into the selected drive.
  4. From your desktop window, access SMIT and make selections according to the level of your AIX operating system.

    Enter:

    +--------------------------------------------------------------------------------+
    |smit install_update &                                                           |
    +--------------------------------------------------------------------------------+

    For AIX 4.3, select:

    +--------------------------------------------------------------------------------+
    |Install and Update Software                                                     |
    |  Install and Update from the LATEST Available Software                         |
    +--------------------------------------------------------------------------------+

    For AIX 5.1, select:

    +--------------------------------------------------------------------------------+
    |Install Software                                                                |
    |  Install Software                                                              |
    +--------------------------------------------------------------------------------+
  5. On the next window, select the device that you are using for the installation. You can enter the drive name in the window or click on List to access the device list.

    If you click on List, select the CD-ROM drive that you are using for the installation (for example, /dev/cd0).

  6. Click on OK.
  7. Locate the line Software to Install.
    1. To install all components listed in the table at step 8, continue at step 10.
    2. To selectively install components, click on List for the latest available software packages and continue at step 8.
  8. Select the components that you require. The following table lists the component fileset file names.


    Table 2. Package and Fileset Names for Installation

    AIX 4.3.3 Platforms
    Package Name Fileset Names Description
    tivoli.tsm.StorageAgent.rte tivoli.tsm.StorageAgent.rte StorageAgent common functions, examples
    tivoli.tsm.devices.aix43.rte tivoli.tsm.devices.aix43.rte SCSI runtime device support
    tivoli.tsm.msg.en_US.devices tivoli.tsm.msg.en_US.devices SMIT screens
    tivoli.tsm.msg.en_US.server tivoli.tsm.msg.en_US.server Message catalog and Online help


    Table 3. Package and Fileset Names for Installation

    AIX 5.1 Platforms
    Package Name Fileset Names Description
    tivoli.tsm.StorageAgent.rte tivoli.tsm.StorageAgent.rte StorageAgent common functions, examples
    tivoli.tsm.devices.aix5.rte64 tivoli.tsm.devices.aix5.rte64 SCSI runtime device support
    tivoli.tsm.msg.en_US.devices tivoli.tsm.msg.en_US.devices SMIT screens
    tivoli.tsm.msg.en_US.server tivoli.tsm.msg.en_US.server Message catalog and Online help
  9. Click OK.
  10. Check the default settings for the options on this window.
  11. Click OK.

    SMIT responds:

    +--------------------------------------------------------------------------------+
    |ARE YOU SURE?...                                                                |
    +--------------------------------------------------------------------------------+
  12. Click OK.

    This installation may take several minutes.

  13. Click Done after the installation is complete, remove the CD, and exit from SMIT.
  14. Ensure that the DEVCONFIG option is specified in the dsmsta.opt file. For example, for a device configuration file named devconfig.out located at /usr/tivoli/tsm/StorageAgent/bin, edit the dsmsta.opt file and enter the following line:
    DEVCONFIG devconfig.out
    
  15. Use the information that you collected in step 1 to issue the DSMSTA SETSTORAGESERVER command. For example:
    dsmsta setstorageserver myname=storagnt mypassword=fun4me
    myhladdress=agent.tucson.ibm.com
    servername=tsmsrver serverpassword=not4u
    hladdress=tsmsrver.tucson.ibm.com lladdress=1502
    

    See Set Installation Data for the Storage Agent: DSMSTA SETSTORAGESERVER for details about the command parameters.

    The command generates the following lines in the device configuration file for the storage agent:

    +--------------------------------------------------------------------------------+
    |set staname storagnt                                                            |
    |SET STAPASSWORD xxxxxxx                                                         |
    |SET STAHLADDRESS agent.tucson.ibm.com                                           |
    |DEFINE SERVER tsmsrver serverpassword=xxxxxxxxxxx                               |
    | HLADDRESS=tsmsrver.tucson.ibm.com LLADDRESS=1502                               |
    |                                                                                |
    +--------------------------------------------------------------------------------+

    The passwords (shown here as xxxxxxxx) are encrypted in the file.

    The command also generates the following line in the dsmsta.opt file:

    +--------------------------------------------------------------------------------+
    |SERVERNAME tsmsrver                                                             |
    +--------------------------------------------------------------------------------+
    See The Storage Agent Options File and The Device Configuration File for the Storage Agent for details on these files.

Step 3. Tivoli Storage Manager Server

The following provides the steps that you need to perform on the TSM server. If further explanation is required, see Administrator's Guide.

  1. For each client that you want to enable SAN data transfer, define the client's storage agent to the TSM server as if the storage agent is a server. You must use the same name and password that you set for the storage agent when you installed it on the client system. The DEFINE SERVER command must be issued from the TSM server (library manager or library client) that will manage the client's data. For example:
    define server storagnt serverpassword=fun4me
    hladdress=agent.tucson.ibm.com lladdress=1500 validateprotocol=all
    
    Note:
    The VALIDATEPROTOCOL parameter in the previous example is optional. This parameter determines whether a cyclic redundancy check should be performed to validate data on all metadata transferred between the storage agent and the TSM server. See the Administrator's Reference for additional information about the DEFINE SERVER command. See the Administrator's Guide for additional information about data validation.
  2. Configure the SAN drives. This involves the following steps:

    Tape Device

    1. Define a shared SCSI or 3494 library
    2. Define paths to the library using the DEFINE PATH command on the server
    3. Define drives that are associated with the library
    4. Define paths to the drives using the DEFINE PATH command on the server
    5. Define the device class
    6. Define the storage pool

    Disk Device

    Configure Enterprise Management and define a device class of DEVTYPE=FILE and SHARED=YES. TSM automatically defines a new FILE library and also defines drives corresponding to the mount limit for the FILE device class. The FILE library name is the same as the device class name. Each drive uses the library name with a numeric suffix. If the mount limit is changed, the number of drives also changes.

    Note:
    As each session gets exclusive access to a file volume, the mount limit should correspond to the number of expected concurrent backups.
  3. Modify policy for the client so the storage agent, acting on behalf of the client, is associated with a storage pool that uses the drives on the SAN. The client must use a management class that has copy groups with a destination storage pool.

    The destination storage pool must be associated with the library. The library must be the one you have defined paths to the drives for the client. For example, do the following:

    1. Create a policy domain for clients that will use the SAN devices for direct data transfer.
    2. Create a policy set in that domain.
    3. In the default management class for that policy set, modify the copy groups. Set the destination storage pool to the storage pool associated with the SAN drives that you configured.
      Note:
      If you decide not to use the default management class for the SAN drives, you will need to create a new management class. Clients that want to use the SAN drives need to use an include statement to bind their files to this new management class. See Backup-Archive Installation and User's Guide for details on the include-exclude list.
    4. Activate the policy set.
    5. Register or update the client nodes so that they are in the new policy domain.

    See Administrator's Guide for details on changing policy for clients that can use SAN drives. For details about the commands, see Administrator's Reference.

The following figure displays the results of completing the previous two steps.

Note:
This figure does not include all the required options. Steps 2 and 3 provide more details.

Figure 5. Communications information. Results of Steps 2 and 3. The passwords are shown as "xxxxxxx" because they are encrypted in the file.

Communications information


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]