Tivoli Storage Manager for Windows: Managed System for SAN Storage Agent User's Guide


Establishing communications among client, storage agent, and server

Figure 5 shows the results of completing Step 2. Client System and Step 3. Server.

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

Step 2. Client System

Do the following on the client system:

  1. Install or upgrade to the latest level of the client software and the TSM API software.
  2. Install the 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 applicable documentation. Install the client software if it is not already installed on the system, or upgrade the software to the latest level as necessary. You can ensure this by checking http://www.tivoli.com/support/storage_mgr/tivolimain.html. If there is a more recent package, you will want to download and install. See step 3 for the install instructions.
  2. Modify the TSM options file (dsm.opt).

    For information about the dsm.opt file, see Tivoli Storage Manager Installing the Clients.

    1. Specify that you want the client to use SAN-attached devices during backup, restore, archive, and retrieve processing, if the path to the SAN devices is available. Activate the following options in the dsm.opt file:
      enablelanfree yes
       
      LANFREECommethod TCPIP
      LANFREETCPPort 1501
      
      and
      LANFREECommethod SharedMem
      LANFREESHMPORT 1511
      
  3. Update the API software to the latest level by following the procedure described below or install the latest client.
    Note:
    Ensure that the client is already installed.
    1. Download the TSM Version 4.2 for the Windows backup-archive client and the associated BAT file from http://www.tivoli.com/support/storage_mgr/tivolimain.html.
    2. Run the BAT file to unzip the files, and follow the directions to begin the installation procedure.
    3. From the Setup Type window, click Custom.
    4. From the Select Components window, select Client Files and click Change.
    5. Select API Client Runtime Files and deselect the other components.
    6. |Ensure that the installation directory you specify, is the same |directory where the existing API resides.

Install and Configure the Storage Agent

|

|Note:
It is recommended that the Storage Agent not be installed on the same machine |as the Tivoli Storage Manager Server. |

On the same system as the client, install the storage agent and perform the following steps:

  1. Gather the following information:
  2. Insert the Managed System for SAN CD-ROM in the drive of the client system. Follow instructions on the screen to install the storage agent. The results of the installation are:
  3. Ensure that a device configuration file exists and that the matching DEVCONFIG option is in the dsmsta.opt file. For example, for a device configuration file named devconfig located c:\program files\tivoli\tsm\storageagent, edit the dsmsta.opt file and enter the following line:
    DEVCONFIG devconfig
    
  4. Use the information that you collected in step 1 to issue the DSMSTA SETSTORAGESERVER command. For example:
    dsmsta setstorageserver myname=iris mypassword=jonquil
    myhladdress=arbor.tucson.tivoli.com
    servername=garden serverpassword=botanical
    hladdress=garden.tucson.tivoli.com lladdress=1500
    

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

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

    +--------------------------------------------------------------------------------+
    |SET STANAME iris                                                                |
    |SET STAPASSWORD xxxxxxx                                                         |
    |SET STAHLADDRESS arbor.tucson.tivoli.com                                        |
    |DEFINE SERVER garden serverpassword=xxxxxxxxxxx                                 |
    | HLADDRESS=garden.tucson.tivoli.com LLADDRESS=1500                              |
    |                                                                                |
    +--------------------------------------------------------------------------------+

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

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

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

Step 3. Server

Note:
The TSM server console (Microsoft Management Console, MMC) provides a snapin that contains a storage agent configuration wizard. This wizard performs all of the manual steps listed here and allows you to skip to step 4. For additional information, see the TSM server console online help.

The following is an overview of the steps that you need to do on the TSM server. For details, see Administrator's Guide. On the server, do the following:

  1. Configure the SAN drives. This involves the following steps:

    Tape Device

    1. Define a shared SCSI or 3494 library
    2. Define drives that are associated with the library
    3. Define the device class
    4. 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:
    The mount limit should correspond to the number of concurrent backups you expect, as each session gets exclusive access to a file volume.
  2. For each client for which you want to enable SAN data transfer, define the client's storage agent as if it was 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 server (library manager or library client) that will manage the client's data. For example:
    define server iris serverpassword=jonquil
    hladdress=sanclient.tucson.tivoli.com lladdress=1500
    
  3. Modify policy for the client so that the storage agent acting on behalf of the client 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 on the SAN for which you have mapped drives for the client. See Administrator's Guide for details on changing policy for clients that can use SAN drives. 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 and mapped for the client.
      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 update the include-exclude list to specify the new management class. See Tivoli Storage Manager Installing the Clients 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 Reference for details on the commands.

    To review the expected results of the steps that you have just completed, see Figure 5.


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