Tivoli Header

Administrator's Guide


Configuring IBM 349X Libraries in a LAN

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

Set up the Device on the Server System

You must first set up the 349X library on the server system. This involves the following tasks:

  1. Set the 349X Library Manager Control Point, or LMCP. This procedure is described in the IBM SCSI Tape Drive, Medium Changer, and Library Device Drivers Installation and User's Guide for AIX.
  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 349X library named 3494LIB:
    define library 3494lib libtype=349x
    
  2. Define a path from the server to the library:
    define path server1 3494lib srctype=server desttype=library 
    device=/dev/lmcp0,/dev/lmcp1
    

    The DEVICE parameter specifies the device special files for the LMCP.

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

  3. Define the drives in the library:
    define drive 3494lib drive01
    define drive 3494lib drive02
    

    Both drives belong to the 3494LIB library.

    See Defining Drives.

  4. Define a path from the server to each drive:
    define path server1 drive01 srctype=server desttype=drive 
    library=3494lib device=/dev/rmt0
    define path server1 drive02 srctype=server desttype=drive 
    library=3494lib device=/dev/rmt1
    

    The DEVICE parameter gives the device special file 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 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 the two drives in the 3494LIB library, use the following command to define a device class named 3494_CLASS:
    define devclass 3494_class library=3494lib devtype=3590 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 3494_POOL associated with the device class named 3494_CLASS.
    define stgpool 3494_pool 3494_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.

Categories in an IBM 349X Automated Library

The 349X library manager tracks the category number of each volume in the library. A single category number identifies all volumes used for the same purpose or application. These category numbers are useful when multiple systems share the resources of a single library.

Attention: If other systems or other Tivoli Storage Manager servers connect to the same 349X library, each must use a unique set of category numbers. Otherwise, two or more systems may try to use the same volume, and cause a corruption or loss of data.

Typically, a software application that uses a 349X library device uses volumes in one or more categories that are reserved for that application. To avoid loss of data, each application sharing the library must have unique categories. When you define a 349X library to the server, you can use the PRIVATECATEGORY and SCRATCHCATEGORY parameters to specify the category numbers for private and scratch Tivoli Storage Manager volumes in that library. See Tivoli Storage Manager Volumes for more information on private and scratch volumes.

When a volume is first inserted into the library, either manually or automatically at the convenience I/O station, the volume is assigned to the insert category (X'FF00'). A software application, such as Tivoli Storage Manager, can contact the library manager to change a volume's category number. For Tivoli Storage Manager, you would use the CHECKIN LIBVOLUME command (see Checking New Volumes into a Library).

The number of categories that the server requires depends on whether you have enabled support for 3590 drives. If support is not enabled for 3590 drives, the server reserves two category numbers in each 349X library that it accesses: one for private volumes and one for scratch volumes. If you enable 3590 support, the server reserves three categories in the 349X library: private, scratch for 3490 drives, and scratch for 3590 drives.

The default values for the PRIVATECATEGORY and SCRATCHCATEGORY parameters are the same as when 3590 support is not enabled. However, the server automatically creates the scratch category for 3590 drives, by adding the number 1 to the SCRATCHCATEGORY value you specify. For example, suppose you enter the following command:

define library my3494 libtype=349x privatecategory=400 scratchcategory=401

Tivoli Storage Manager uses the following categories in the library:

To avoid overlapping categories, ensure that the value specifies for the private category is not equal to the scratch category value plus 1.

Attention: The default values for the categories may be acceptable in most cases. However, if you connect other systems or Tivoli Storage Manager servers to a single 349X library, ensure that each uses unique category numbers. Otherwise, two or more systems may try to use the same volume, and cause a corruption or loss of data.

Also, if you share a 349X library with other Tivoli Storage Manager servers or other applications or systems, be careful when enabling 3590 support to prevent loss of data. See Enabling Support for IBM 3590 Drives in Existing 349X Libraries. 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.

Enabling Support for IBM 3590 Drives in Existing 349X Libraries

The new category that the server creates for 3590 scratch volumes can duplicate a category already assigned to another application and cause loss of data. If you are currently sharing a 349X library with other Tivoli Storage Manager servers or other applications or systems and you enable support for 3590 drives, you need to be careful. The server automatically creates a third category for 3590 scratch volumes by adding one to the existing scratch category for any 349X libraries defined to Tivoli Storage Manager.

To prevent loss of data, do one of the following before enabling 3590 support:

For more information about checking in volumes, see Checking New Volumes into a Library.

After taking steps to prevent data loss, enable 3590 support by adding the following line to the server options file (dsmserv.opt):

ENABLE3590LIBRARY  YES

Stop and start the server to make this change effective.

Check in and Label a Library Volume

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.
  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 ]