Tivoli Header

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 the StorageTek ACSLS and the Gresham EDT documentation for installation instructions. See Figure 4 for an example of a storage agent in an ACSLS-managed library environment. Complete the following steps to configure your storage agent external library environment:

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

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

Step 2. Client System

The procedures in this section describe installation and configuration of TSM client, API, storage agent, and Gresham EDT software.

Note:
Gresham EDT or any other middleware that provides external library enablement is allowed. For installation information, see the Gresham or other middleware products documentation.

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 client 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
      TCPPport 1502
      
    2. Edit the dsm.opt file to specify the servername 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. Load the storage agent CD-ROM into the selected drive.
  4. Enter the following command for a list of packages that you can install:
    +--------------------------------------------------------------------------------+
    |/usr/sbin/pkgadd -d /cdrom/cdrom0                                               |
    +--------------------------------------------------------------------------------+

    In this example the CD-ROM name is /cdrom/cdrom0; yours may be different.

    You can make multiple selections at this step. The packages are:

    TIVsmSsta
    The Tivoli storage agent application is installed.

    TIVsmSdev
    The device driver package for non-IBM devices is installed.

    The PKGADD command loads the selected files.

    Notes:

    1. Loading the storage agent files can take several minutes, and it may take a few minutes for the installation to begin after the server package has been selected.

    2. The installation program automatically installs the storage agent based on the level of Sun Solaris on the installation machine.
  5. Enter "y" when the system issues this message:
    +--------------------------------------------------------------------------------+
    |This package contains scripts which will be executed with super-user (root)     |
    |permission during the process of installing the package.                        |
    |Do you want to continue with the installation of this package?                  |
    +--------------------------------------------------------------------------------+
  6. Enter the following commands from a root user command prompt to eject the CD, after the installation is complete:
    +--------------------------------------------------------------------------------+
    |cd /                                                                            |
    |eject cdrom                                                                     |
    +--------------------------------------------------------------------------------+
  7. 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
     
    
    Note:
    The TSM server, in this example TSMSRVER, must be running when the DSMSTA SETSTORAGESERVER command is issued.
    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.
  8. 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:

    Incorporate the following library definition information:

    Using the editor of your choice, open device configuration file and add the following entry to the bottom of the file:

    +--------------------------------------------------------------------------------+
    |DEFINE LIBRARY stk-lib libtype=external lanfree=yes obeymountretention=yes      |
    |                                                                                |
    +--------------------------------------------------------------------------------+

    The resulting device configuration file would appear as:

    +--------------------------------------------------------------------------------+
    |SET STANAME storagnt                                                            |
    |SET STAPASSWORD xxxxxxx                                                         |
    |SET STAHLADDRESS agent.tucson.ibm.com                                           |
    |DEFINE SERVER tsmsrver serverpassword=xxxxxxxxxxx                               |
    | HLADDRESS=tsmsrver.tucson.ibm.com LLADDRESS=1502                               |
    |DEFINE LIBRARY stk-lib libtype=external lanfree=yes obeymountretention=yes      |
    |                                                                                |
    +--------------------------------------------------------------------------------+

    Save and close the file.

  9. Define a path from the storage agent to the external manager. Gresham EDT-DistribuTape is the external library manager interfacing with the ACSLS library software. The EDT executable is located in its default path /opt/OMIdtelm/bin/elm. For example:
    define path storagnt stk-lib srctype=server desttype=library
     externalmanager=/opt/OMIdtelm/bin/elm
    

    For additional information about the DEFINE PATH command, see the Tivoli Storage Manager Administrator's Reference.

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. On the server, perform 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. 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 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.
  3. Configure the SAN drives. This involves the following steps:

    1. Define a library type of EXTERNAL. For example:
      define library stk-lib libtype=external lanfree=yes obeymountretention=yes
       
      
    2. Define a path from the server to the external manager. Gresham EDT-DistribuTape is the external library manager interfacing with the ACSLS library software, the EDT executable is located in its default path /opt/OMIdtelm/bin/elm. For example:
      define path tsmsrver stk-lib srctype=server desttype=library
       externalmanager=/opt/OMIdtelm/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 PATH command, see theAdministrator's Reference.
    3. Define a path from the storage agent to the external manager. The DEFINE PATH command must be issued from the TSM server. Gresham EDT-DistribuTape is the external library manager interfacing with the ACSLS library software. The EDT executable is located in its default path /opt/OMIdtelm/bin/elm. For example:
      define path storagnt stk-lib srctype=server desttype=library
       externalmanager=/opt/OMIdtelm/bin/elm
      
      For additional information about the DEFINE PATH command, see the Tivoli Storage Manager Administrator's Reference.
    4. Define a device class with a device type of ECARTRIDGE
    5. Define the storage pool
  4. Modify policy for the client so the storage agent, acting on behalf of the client, is associated with a storage pool that users 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 that you have defined paths to its 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 external library, you will need to create a new management class. Clients that want to use the SAN attached library 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 additional command information, 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 7. Communications information. Results of Steps 2 and 3. The passwords are shown as "xxxxxxx" because they are encrypted in the file.

Communications information

Configuring Devices for the Storage Agent to Access

Step 4. Client System

During this step you will start the storage agent and verify the LAN-free configuration.

Start the Storage Agent

Start the storage agent as follows:

Verify the LAN-free 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. Verify that the backup is LAN-free by using a TSM Administrative Command Line client to login to the TSM server and storage agent to verify the proper sessions have been established. When LAN-free data movement is occurring, a QUERY SESSION on the storage agent should show bytes received (displayed as Bytes Recvd) for the node increasing to the total amount of data being backed up. The QUERY SESSION on the TSM server should show a very small amount of bytes received (metadata) for the same node. If the node's session exhibits this behavior, and you receive a message stating 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 ]