Tivoli Storage Manager for Windows: Administrator's Guide


Configuring TSM Clients to Directly Access SAN-Attached Devices

This section describes the tasks involved in configuring the TSM client and server so that the client can, via a storage agent, move its data to storage on a SAN. As part of the configuration, a storage agent is installed on the client system. TSM supports both tape libraries and FILE libraries. The configuration steps are somewhat different. Only the tape library setup is shown in this publication. See TSM Managed System for SAN Storage Agent User's Guide for detailed information about configuring the TSM client, storage agent, and server for both tape and FILE libraries. This function is provided by the Managed System for SAN feature.

Note:
TCP/IP is the only protocol currently supported for communications between the storage agent and the TSM server.

TSM Client Setup

Setting up the client to directly access a storage device over a SAN consists of installing and configuring the storage agent on the TSM client machine and enabling the option for the API to allow the data movement. You also need to set up the TSM device driver. Thereafter, the client communicates with the storage agent, which in turn communicates with the TSM server. For details on these steps, see TSM Managed System for SAN Storage Agent User's Guide.

TSM Server Setup

  1. Verify that the TSM server is running, and start it if it is not:
    1. From the TSM Console, expand the tree for the server instance you are configuring.
    2. Expand Reports
    3. Click Service Information IconService Information in the TSM Console tree in the left panel. The Service Information window appears in the right panel.
    4. Check to see if the TSM library client server is running. If it is stopped, right click on the server name. A pop-up menu appears.
    5. Click Start in the pop-up menu.
  2. Verify that the TSM device driver is running, and start it if it is not:
    1. From the TSM Console, expand the tree for the machine you are configuring.
    2. Expand Reports.
    3. Click Service Information IconService Information in the TSM Console tree in the left panel. The Service Information window appears in the right panel.
    4. Check to see if the TSM device driver is running. If it is stopped, right click TSM Device Driver. A pop-up menu appears.
    5. Click Start in the pop-up menu.
  3. Obtain the library and drive information for the shared library device:
    1. From the TSM Console, expand the tree for the machine you are configuring.
    2. Expand TSM Device Driver and Reports.
    3. Click Device Information. The Device Information window appears in the right pane.
  4. Define a library named SANGROUP, using the SHARED=YES parameter.
    define library sangroup libtype=scsi device=lb0.0.0.2 shared=yes
    
  5. Define the drives in the library.
    define drive sangroup drivea device=mt0.0.0.2 element=1030
    define drive sangroup driveb device=mt0.2.0.2 element=1031
    
  6. Define a device class for the drives.
    define devclass santape devtype=3570 mountretention=1 mountwait=10
     library=sangroup
    
    Note:
    Do not use a device type of GENERICTAPE for drives to be shared on a SAN with clients.
  7. Define a storage pool, SANPOOL.
    define stgpool sanpool santape description='SAN storage pool'
     maxscratch=50
    

    For each client for which you want to enable SAN data transfer, do the following:

  8. On the server, define the client's storage agent as if it were a server. The name must match the name specified during storage agent configuration. For example, if the storage agent's name is IRIS, issue the following command:
    define server iris serverpassword=jonquil
     hladdress=sanclient.tucson.ibm.com lladdress=1500
    
  9. On the client system, do the following:
    1. Start the TSM device driver.
    2. Determine the device name by which the storage agent knows the device.
    For details on these steps, see TSM Managed System for SAN Storage Agent User's Guide.
  10. On the server, define drive mapping for every drive that the storage agent will access, by using the DEFINE DRIVEMAPPING command.
    Note:
    Before issuing the following commands to map your drives, review the guidelines listed in Guidelines for Mapping Drives.

    For the device name, specify the device name by which the storage agent knows the device.

    define drivemapping iris sangroup drivea device=mt5.0.0.1
    define drivemapping iris sangroup driveb device=mt5.2.0.1
    
  11. Set up the policy so that the clients use the new storage pool as the destination for their backup operations. See Configuring Policy for Managed System for SAN for details.
  12. On the client system, do the following:
    1. Start the storage agent.
    2. Start a backup operation to verify that the setup is complete. To verify whether your configuration was successful, review the information described in Determining Whether the Data Movement was LAN-Free .
    For details on these steps, see TSM Managed System for SAN Storage Agent User's Guide.

Guidelines for Mapping Drives

Consider the following guidelines before you begin mapping your SAN drives:

Determining Whether the Data Movement was LAN-Free

You can use the following guidelines to help you determine whether the data movement was LAN-free:


On this Operating System Do this:
Windows 2000 Click Settings> Network and Dial-up Connections > Local Area Connection Status.
Windows NT Go to an MS-DOS command line and enter:
netstat -e
Note:
The output from the netstat -e command matches the Bytes Sent and Received output displayed on Windows 2000.


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