Tivoli Storage Manager for Windows: Administrator's Guide


Configuring TSM Servers to Share SAN-Connected Devices

The following tasks are required to share tape library devices over a SAN:

Task Required Privilege Class
Setting up Server Communications System or unrestricted storage
Setting up the Library Manager Server System or unrestricted storage
Setting up the Library Client Servers System or unrestricted storage

Setting up Server Communications

Before TSM servers can share a storage device over a SAN, you must set up server communications. This requires configuring each server for Enterprise Administration and defining the servers to each other, using the cross-define function. See Setting Up Communications Among Servers for details.

Note:
Set up each server with a unique name.

Setting up the Library Manager Server

Use the following procedure as an example of how to set up a TSM server as a library manager:

  1. Verify that the TSM library manager 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 manager 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 whose library type is SCSI. For example:
    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.1.0.2 element=1030
    define drive sangroup driveb device=mt0.2.0.2 element=1031
    
  6. Define at least one device class. Use a low mount retention time (1-2 minutes) and mount wait time for shared library devices. Set the mount wait times to different values for each server.
    define devclass tape devtype=dlt mountretention=1 mountwait=10
     library=sangroup
    
  7. Check in the library inventory. The following example checks all volumes into the library inventory as scratch volumes. The server uses the name on the barcode label as the volume name.
    checkin libvolume sangroup search=yes status=scratch
     checklabel=barcode 
    
  8. Set up a storage pool for the shared library with a maximum of 50 scratch volumes.
    define stgpool backtape tape
     description='storage pool for shared sangroup' maxscratch=50
    

Setting up the Library Client Servers

Use the following procedure as an example of how to set up a TSM server as a library client. You must define the library manager server before setting up the library client server.

  1. Verify that the TSM library client 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 the shared library, SANGROUP.
    Note:
    Ensure that the library name agrees with the library name on the library manager.
    define library sangroup libtype=shared primarylibmanager=libmaster
    
  5. Define the drives to the library by using the same names as the drives on the library manager. Element addresses are not required for shared libraries when defining drives on the library client.
    define drive sangroup drivea device=mt0.1.0.3
    define drive sangroup driveb device=mt0.2.0.3
    
    Note:
    You do not have to specify all of the drives in the shared library device.
  6. Define at least one device class. Use a low mount retention time (1-2 minutes) and mount wait time for shared library devices. Set the mount wait times to different values for each server.
    define devclass tape devtype=dlt mountretention=1 mountwait=10
     library=sangroup
    
  7. Define the storage pool, BACKTAPE, that will use the shared library.
    define stgpool backtape tape
     description='storage pool for shared sangroup' maxscratch=50
    
  8. Repeat this procedure to define additional servers as library clients.

Server Operations

When the library manager server starts and the storage device initializes, or after a library manager server is defined to a library client server, the library client server contacts the library manager server. The library client server confirms that the contacted server is the library manager for the named library device. The library client server also compares drive definitions with the library manager server for consistency. The library client server contacts the library manager server for each of the following operations:

Volume Mount
A library client server sends a request to the library manager server for access to a particular volume in the shared library device. For a scratch volume, the library client server does not specify a volume name. If the library manager server cannot access the requested volume, or if scratch volumes are not available, the library manager server denies the mount request. If the mount is successful, the library manager server returns the name of the drive where the volume is mounted.

Volume Release (free to scratch)
When a library client server no longer needs to access a volume, it notifies the library manager server that the volume should be returned to scratch. The library manager server database is updated with the volume's new owner. The volume is deleted from the volume inventory of the library client server.

Table 4 shows the interaction between library client servers and the library manager server in executing TSM commands.

Table 4. How SAN-enabled Servers Execute Common TSM Commands

Server command Library Manager Server Library Client Server
QUERY LIBVOLUME Displays the volumes that are checked into the library. For private volumes, the owner server is also displayed. Not applicable.
CHECKIN LIBVOLUME
CHECKOUT LIBVOLUME
Performs the commands to the library device. Not applicable.

When a check-in operation must be performed because of a client restore, a request is sent to the library manager server.

MOVE MEDIA
MOVE DRMEDIA
Only valid for volumes used by the library manager server. Requests that the library manager server perform the operations. Generates a checkout process on the library manager server.
AUDIT LIBRARY Performs the inventory synchronization with the library device. Performs the inventory synchronization with the library manager server.
LABEL LIBVOLUME Performs the labeling and check-in of media. Not applicable.
DISMOUNT VOLUME Sends the request to the library device. Requests that the library manager server perform the operation.
QUERY VOLUME Checks whether the volume is owned by the requesting library client server and checks whether the volume is in the library device. Requests that the library manager server perform the operation.


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