Tivoli Header

Administrator's Guide


Configuring SCSI Libraries in a SAN

Using a SAN with Tivoli Storage Manager allows the following functions:

The following tasks are required for Tivoli Storage Manager servers to share library devices over a SAN:

  1. Set up server-to-server communications.
  2. Set up the library on the library manager server. In the example used for this section, the library manager server is named ASTRO.
  3. Set up the library on the library client server. In the example used for this section, the library client server is named JUDY.

Setting up Server Communications

Before Tivoli Storage Manager 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. For a discussion regarding the interaction between library clients and the library manager in processing Tivoli Storage Manager operations, see Performing Operations with Shared Libraries.

Set up the Device on the Server System

You must first set up the device on the server system. This involves the following tasks:

  1. Set the appropriate SCSI ID for each drive and for the library or medium-changer.
  2. Physically attach the devices to the server hardware.
  3. Install and configure the appropriate device drivers for the devices.
  4. Determine the device names that are needed to define the devices to Tivoli Storage Manager.
For details, see Attaching an Automated Library Device and Installing and Configuring Device Drivers.

Setting up the Library Manager Server

Use the following procedure as an example of how to set up a Tivoli Storage Manager server as a library manager. The server is named ASTRO:

  1. Define a shared SCSI library named SANGROUP:
    define library sangroup libtype=scsi shared=yes
    
  2. Define a path from the server to the library:
    define path astro sangroup srctype=server desttype=library 
     device=/dev/lb3
    

    For more information about paths, see Defining Paths.

  3. Define the drives in the library:
    define drive sangroup drivea element=16
    define drive sangroup driveb element=17
    
  4. Define a path from the server to each drive:
    define path astro drivea srctype=server desttype=drive 
     library=sangroup device=/dev/rmt4
    define path astro driveb srctype=server desttype=drive 
     library=sangroup device=/dev/rmt5
    

    For more information about paths, see Defining Paths.

  5. Define at least one device class that is associated with the shared library. Set the mount wait times to different values for each server.
    define devclass tape library=sangroup devtype=3570 mountretention=2 mountwait=15
    
  6. Check in the library inventory. The following shows two examples. In both cases, the server uses the name on the barcode label as the volume name.
  7. Set up a storage pool for the shared library with a maximum of 50 scratch volumes.
    define stgpool backtape tape maxscratch=50
    

Setting up the Library Client Servers

Use the following sample procedure for each Tivoli Storage Manager server that will be a library client server.

  1. Define the server that is the library manager:
    define server astro serverpassword=secret hladdress=9.115.3.45 lladdress=1580
     crossdefine=yes
    
  2. Define the shared library named SANGROUP, and identify the library manager server's name as the primary library manager. Ensure that the library name agrees with the library name on the library manager:
    define library sangroup libtype=shared primarylibmanager=astro
    
  3. Define the drives in 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
    define drive sangroup driveb 
    
    Note:
    We recommend that you define all the drives in the shared library to the library client and library manager servers.
  4. Define a path from the library client server to each drive:
    define path judy drivea srctype=server desttype=drive 
     library=sangroup device=/dev/rmt4
    define path judy driveb srctype=server desttype=drive 
     library=sangroup device=/dev/rmt5
    

    For more information about paths, see Defining Paths.

  5. Define at least one device class that is associated with the shared library. Set the mount wait times to different values for each server.
    define devclass tape library=sangroup devtype=3570 mountretention=2 mountwait=10
     
    
  6. Define the storage pool, BACKTAPE, that will use the shared library.
    define stgpool backtape tape maxscratch=50
    

Using the Devices to Store Client Data

After you have attached and defined your devices, you can store client data in two ways:


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