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


|Procedure 2 --External Library Environment with an ACSLS-Managed Library

| |

|If you will be using a Tivoli Storage Agent with ACSLS-managed libraries, |you must have the ACSLS software and the third-party external library software |(such as, Gresham EDT-DistribuTAPE) installed and configured. See Figure 4 for an example of a Storage Agent in an ACSLS-managed |library environment. See the StorageTek ACSLS and the Gresham EDT |documentation for installation instructions.

|Step 1. Network

|

|The server system and the client systems must be attached to the SAN along |with appropriate storage devices. The server system and the client |systems must also be connected by means of a LAN.

|The Managed System for SAN feature requires specific levels and models of |hardware and software. Ensure that your system configuration meets the |hardware and software requirements for the SAN setup. See the Web site, |http://www.tivoli.com/support/storage_mgr/san/overview.html, |for details.

|Establishing communications among client, storage agent, and server

|Figure 7 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 7. 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 (version 4.2 or higher).
  2. |Install the storage agent software.
  3. |Install Gresham EDT or any other third-party software that provides |external library enablement. For installation information, see the |Gresham documentation. |

|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 3 for the install instructions.
  2. |Modify the TSM client options file (dsm.sys).

    |For information about the dsm.opt and dsm.sys files, see |Tivoli Storage Manager Installing the Clients. |

    1. |Edit the dsm.sys file to specify the communications method between |the TSM client and server. You should see the following:
      |commmethod tcpip
      |tcpserveraddress garden.tucson.tivoli.com
      |tcpport 1501

      |and

      |commmethod sharedmem
      |shmport 1511
    2. |If you specified the TCP/IP communication method, edit the dsm.opt |file to name the server specified in the communication method. For |example,
      |servername garden
    3. | | | | |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 option in the dsm.sys |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. |Create the Tivoli Storage Manager API option files |
      1. |Copy APIINSTALLPATH/dsm.sys.smp to dsm.sys if your |system has not been set up to use Tivoli Storage Manager.
      2. |Edit the dsm.sys file to include the Tivoli Storage Manager server |to which you want to connect. For example:
        |SErvername         server_a  
        |COMMmethod         TCPip
        |TCPPort            1500 
        |TCPServeraddress   server_a.domain.company.COM

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

    2. |Set up the environment variables. The BASE 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=APIINSTALLPATH/dsm.opt
      |export DSMI_DIR=APIINSTALLPATH
      |export DSMI_LOG=/home/user_a/logdir 
      |Note:
      The quickest way to set these is to add these variables to the user's |.profile file. |
    3. |Using shared memory.

      |The Tivoli Storage Manager API client user must be logged in as root or |have the same user ID as the process running the Tivoli Storage Manager |server. |

    |

|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. 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 |server files can take several minutes. |

|Here is the SMIT procedure: |

  1. |Gather the following information: |
  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 component that you require. The following |table lists the component fileset file names.


    |

    |Table 4. 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 5. 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. |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=botanical                                   |
    ||	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.
  15. |Start this step only after the dsmsta command issued in the previous step |has completed successfully. Use the library information that you |collected in step 1 and add library definition information to the device |configuration file. For example:

    |Using the editor of your choice open the device configuration file and add |the library named stk-lib, set the libtype to external with lanfree and |obeymountretention equalling yes. Gresham EDT-DistribuTape is the |external library manager interfacing with the ACSLS library software, the EDT |executable is located in its default path /usr/lpp/dtelm/bin/elm. With |the device configuration file open you would add the following entry to the |bottom of the file:

    |+--------------------------------------------------------------------------------+
    ||DEFINE LIBRARY stk-lib libtype=external lanfree=yes obeymountretention=yes      |
    ||	EXTERNALMANAGER=/usr/lpp/dtelm/bin/elm                                         |
    ||                                                                                |
    |+--------------------------------------------------------------------------------+

    |The resulting device configuration file would appear as:

    |+--------------------------------------------------------------------------------+
    ||SET STANAME iris                                                                |
    ||SET STAPASSWORD xxxxxxx                                                         |
    ||SET STAHLADDRESS arbor.tucson.tivoli.com                                        |
    ||DEFINE SERVER garden serverpassword=xxxxxxxxxxx                                 |
    || HLADDRESS=garden.tucson.tivoli.com LLADDRESS=1500                              |
    ||DEFINE LIBRARY eagle-lib libtype=external lanfree=yes obeymountretention=yes    |
    ||	EXTERNALMANAGER=/usr/lpp/dtelm/bin/elm                                         |
    ||                                                                                |
    |+--------------------------------------------------------------------------------+

    |Save and close the file. |

|Step 3. Server

|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. |Install Gresham EDT or any other third-party software that provides |external library enablement. For installation information, see the |Gresham documentation.
  2. |Configure the SAN drives. This involves the following steps:

    |Tape Device |

    1. |Define a library type of EXTERNAL. For example:
      |define library stk-lib libtype=external lanfree=yes obeymountretention=yes
      | externalmanager=/usr/lpp/dtelm/bin/elm
      In the previous example the path provided for the external manager is |dependent upon the operating system where the TSM server resides. For |example, an AIX TSM server external manager path is /usr/lpp/dtelm/bin/elm in |contrast to a TSM Sun server external manager path of /opt/OMIdtelm/bin/elm or |a TSM Windows server external manager path of c:\program |files\GES\EDT\bin\elm.exe. For additional information about the |DEFINE LIBRARY command, see the Tivoli Storage Manager Administrator's |Reference.
    2. |Define a device class with a device type of ECARTRIDGE
    3. |Define the storage pool |
  3. |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
  4. |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 External |Library, you will need to create a new management class. Clients that |want to use the SAN attached library 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. |

|Configuring Devices for the Storage Agent to Access

|In step 4 you will enable and start the device driver in order to support |the tape device. In contrast to other configurations documented in this |publication External library support does not require TSM drive |mapping. Instead the Gresham middleware product provides the drive |mapping.

|Step 4. Client System

|Do the following: |

  1. |Start the Storage Agent
  2. |Verify the Configuration |

|Start the Storage Agent

|

|Start the storage agent by changing to the storage agent directory and |issue the following command:

|dsmsta

|Verify the Configuration

|

|To verify that you have configured your system correctly for LAN-free data |movement, perform the following procedure: |

  1. |Run a backup operation from the client. If you receive a message |saying that the backup has been successful, you have configured your system |correctly.
  2. |Ensure the following if you receive a message saying that the backup has |failed.
    |Note:
    If you retry the backup operation after the first failure, the client |attempts to use the LAN connection for data movement. The client will |continue to use the LAN until the client is stopped and restarted. |
    |
    1. |The TSM server is running. If the TSM server is not running, the |storage agent will not start.
    2. |The client, storage agent, and server are communicating with each other as |expected.
    3. |The mount and message is displayed on the storage agent console. |
    |

|Determining Whether the Data Movement was LAN-free
| |

|Use the following guidelines to help determine whether the data movement is |using the LAN-free environment: |


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