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

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
       
      

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 /opt/tivoli/tsm/StorageAgent/bin.

  1. Record the following information. This information is required throughout the remainder of this procedure.
  2. Log in as the root user.
  3. Insert the storage agent CD-ROM into a CD-ROM drive. The following discussion assumes that the CD-ROM is mounted on directory /cdrom.
  4. See the README.STA file on the CD-ROM for changes to the installation procedure.
  5. Use the SWINSTALL command in non-interactive or interactive mode.
    1. To install non-interactively: Enter the following command and continue at step 13:
      +--------------------------------------------------------------------------------+
      |swinstall -s /cdrom <filesetname>                                               |
      +--------------------------------------------------------------------------------+

      Where <filesetname> is one or more fileset names listed in Table 2.

      Note:
      To install all storage agent files, specify: TIVsmHsta.

      Table 2. Storage Agent Filesets

      Fileset: Installs:
      TIVsmHsta.storage_agent Storage agent
      TIVsmDD32_HP11_00 HP 32-bit device driver for HP 11.00
      TIVsmDD64_HP11_00 HP 64-bit device driver for HP 11.00
      TIVsmDD32_HP11_11 HP 32-bit device driver for HP 11.11
      TIVsmDD64_HP11_11 HP 64-bit device driver for HP 11.11
    2. To install in interactive mode: Enter the following command and continue at step 6:
      +--------------------------------------------------------------------------------+
      |swinstall -s /cdrom                                                             |
      +--------------------------------------------------------------------------------+
  6. Select Options from the menu. In the Change Options box, review the installation options and change any that are required for your particular installation.
  7. At the Software Selection Screen, select the TSM product or products you require:
  8. From the Actions pull-down menu, select Mark for Install.
  9. From the Actions pull-down menu, select Install.
  10. Select OK.
  11. Select YES to begin installing.
  12. When the message appears indicating that the installation is complete, select Done.
  13. When the installation is finished, remove the CD from the drive.
  14. Select Exit from the File menu to leave the installation program and return to the system prompt.
  15. Ensure that the DEVCONFIG option is specified in the dsmsta.opt file. If not, perform the following for example, for a device configuration file named devconfig.out located /opt/tivoli/tsm/StorageAgent/bin, edit the dsmsta.opt file and enter the following line:
    DEVCONFIG devconfig.out
    
  16. 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 4. 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 ]