Example: Configure a SCSI or virtual tape library with multiple drive device types

You can configure a library with multiple drive device types, for example, a StorageTek L40 library that contains one DLT drive and one LTO Ultrium drive.

About this task

This procedure is an example of configuring an automated SCSI library that contains two drives to the server system. The library is not shared with other IBM Spectrum® Protect servers or with storage agents and is typically attached to the server system by SCSI cables.

In this configuration, the drives are different device types. Define a device class for each drive device type. Drives with different device types are supported in a single library if you define a device class for each type of drive. If you are configuring this way, you must include the specific format for the drive's device type by using the FORMAT parameter with a value other than DRIVE.

The procedure is the same for both SCSI libraries and VTLs, except for the step to define the library. For SCSI libraries, define the library with libtype=scsi. For VTL libraries, define the library with libtype=vtl.

Procedure

  1. Define a SCSI library named MIXEDLIB.
    define library mixedlib libtype=scsi
  2. Define a path from the server to the library.
    AIX operating systems
    define path server1 mixedlib srctype=server desttype=library 
    device=/dev/lb3
    Linux operating systems
    define path server1 mixedlib srctype=server desttype=library 
    device=/dev/tsmscsi/lb3
    Windows operating systems
    define path server1 mixedlib srctype=server desttype=library 
    device=lb0.0.0.3
  3. Define the drives in the library. Both drives belong to the MIXEDLIB library.
    define drive mixedlib dlt1
    define drive mixedlib lto1
  4. Define a path from the server to each drive.
    The DEVICE parameter specifies the device driver's name for the drive, which is the device special file name.
    AIX operating systems
    define path server1 dlt1 srctype=server desttype=drive 
    library=mixedlib device=/dev/mt4
    define path server1 lto1 srctype=server desttype=drive 
    library=mixedlib device=/dev/mt5
    Linux operating systems
    define path server1 dlt1 srctype=server desttype=drive 
    library=mixedlib device=/dev/tsmscsi/mt4
    define path server1 lto1 srctype=server desttype=drive 
    library=mixedlib device=/dev/tsmscsi/mt5
    Windows operating systems
    define path server1 drive01 srctype=server desttype=drive 
    library=autoltolib device=mt0.0.0.4
    define path server1 drive02 srctype=server desttype=drive 
    library=autoltolib device=mt0.0.0.5

    If you did not include the element address when you defined the drive, the server now queries the library to obtain the element address for the drive.

  5. Define device classes.
    Important: Do not use the DRIVE format, which is the default. Because the drives are different types, the server uses the format specification to select a drive. The results of using the DRIVE format in a mixed media library are unpredictable.
    define devclass dlt_class library=mixedlib devtype=dlt format=dlt40
    define devclass lto_class library=mixedlib devtype=lto format=ultriumc
  6. Define storage pools that are associated with the device classes.
    define stgpool lto_pool lto_class maxscratch=20
    define stgpool dlt_pool dlt_class maxscratch=20
  7. Label and check in library volumes.
    label libvolume mixedlib search=yes labelsource=barcode checkin=scratch
  8. Verify your definitions by issuing the following commands:
    query library
    query drive
    query path
    query devclass
    query stgpool
    query libvolume