Tivoli Header

Administrator's Guide


Configuring SCSI Libraries in a LAN

In the following example, an automated SCSI library containing two drives is attached to the server system.

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.

Define the Device to Tivoli Storage Manager

  1. Define a SCSI library named AUTO8MM. The library type is SCSI because the library is a SCSI-controlled automated library. Enter the following command:
    define library auto8mmlib libtype=scsi
    
  2. Define a path from the server to the library:
    define path server1 auto8mmlib srctype=server1 desttype=library 
    device=/dev/lb3
    

    The DEVICE parameter specifies the device driver's name for the library, which is the special file name.

    See Defining Libraries and SCSI Libraries. For more information about paths, see Defining Paths.

  3. Define the drives in the library:
    define drive auto8mmlib drive01 element=82
    define drive auto8mmlib drive02 element=83
    

    Both drives belong to the AUTO8MMLIB library.

    Element address: The element address is a number that indicates the physical location of a drive within an automated library. The server needs the element address to connect the physical location of the drive to the drive's SCSI address. When you define a drive, the element address is required if more than one drive is in an automated library. The element numbers are taken from the device worksheet filled out in step 7. See http://www.tivoli.com/support/storage_mgr/tivolimain.html to determine the element numbers.

    See Defining Drives. For more information about paths, see Defining Paths.

  4. Define a path from the server to each drive:
    define path server1 drive01 srctype=server desttype=drive 
    library=auto8mmlib device=/dev/mt4
    define path server1 drive02 srctype=server desttype=drive 
    library=auto8mmlib device=/dev/mt4
    

    The DEVICE parameter specifies the device driver's name for the drive. In this example, each drive is given a device special file name by Tivoli Storage Manager that is unique to the device special file. For more about device special file names, see Determining Device Special File Names. For more information about paths, see Defining Paths.

  5. Classify drives according to type by defining Tivoli Storage Manager device classes. We recommend that you use FORMAT=DRIVE as the recording format only if all the drives associated with the device class are identical. For example, to classify two drives in the AUTO8MMLIB library, use the following command to define a device class named AUTO8MM_CLASS:
    define devclass auto8mm_class library=auto8mmlib devtype=8mm format=drive
    

    See Defining and Updating Device Classes for Tape Devices.

  6. Verify your definitions by issuing the following commands:
    query library
    query drive
    query path
    query devclass
     
    

    See Requesting Information About Libraries, Requesting Information about Drives, Requesting Information about a Device Class, and Requesting Information About Paths.

  7. Define a storage pool named AUTO8MM_POOL associated with the device class named AUTO8MM_CLASS.
    define stgpool auto8mm_pool auto8mm_class maxscratch=20
    

    Key choices:

    1. Scratch volumes are empty volumes that are labeled and available for use. If you allow scratch volumes for the storage pool by specifying a value for the maximum number of scratch volumes, the server can choose from the scratch volumes available in the library, without further action on your part. If you do not allow scratch volumes, you must perform the extra step of explicitly defining each volume to be used in the storage pool.

    2. Collocation is turned off by default. Collocation is a process by which the server attempts to keep all files belonging to a client node or client file space on a minimal number of volumes. Once clients begin storing data in a storage pool with collocation off, you cannot easily change the data in the storage pool so that it is collocated. To understand the advantages and disadvantages of collocation, see Keeping a Client's Files Together: Collocation and How Collocation Affects Reclamation.

    For more information, see Defining or Updating Primary Storage Pools.

Check in and Label Library Volumes

Ensure that enough volumes are available to the server in the library. Keep enough labeled volumes on hand so that you do not run out during an operation such as client backup.

  1. 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.
  2. Depending on whether you use scratch volumes or private volumes, do one of the following:

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 ]