Configuring libraries for use by one server

To use a library or libraries for storage from one Tivoli® Storage Manager server, you must first set up the device on the server system.

1. For 3494 libraries, set the library ID or name.
   • Set the 3494 Library Manager Control Point (LMCP).
   • Set the symbolic name for the library in the configuration file for the library device driver (/etc/ibmatl.conf).
   These procedures are described in the IBM Tape Device Drivers Installation and User’s Guide at http://www.ibm.com/support/docview.wss?uid=ssg1S7002972.
2. Physically attach devices to the server hardware.
3. Install and configure the appropriate device drivers for the devices on the server that will use the library and drives.
4. Determine the device names that are needed to define the library to Tivoli Storage Manager.
5. Configure the library:
   1. Define the library.
   2. Define a path from the server to the library.
   3. Define the drives in the library.
      Note:

      For SCSI and VTL libraries, you can use the PERFORM LIBACTION to define drives and paths for a library instead of completing Steps c and d separately.

      For ACSLS and 3494 libraries: Drives with different device types or different generations of drives are supported in a single physical library if you define one library to Tivoli Storage Manager for each type of drive or generation of drive. For example, if you have two device types, or two generations of drives of the same device type, define two libraries. Then define the drives and device classes for each library.

   4. Define a path from the server to each drive.
   5. Define a Tivoli Storage Manager device class.

      Device classes specify the recording formats for drives and classify them according to type. Use the default value, FORMAT=DRIVE as the recording format only if all the drives associated with the device class can read and write to all of the media. For example, if you have a mix of Ultrium Generation 3 and Ultrium Generation 4 drives, but only have Ultrium Generation 3 media, you can specify FORMAT=DRIVE because both the Generation 4 and Generation 3 drives can read from and write to Generation 3 media.

   6. Define a storage pool.
      Consider the following key choices for defining storage pools:

      • Scratch volumes are empty volumes that are 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. Also, specify MAXSCR=0 when you define the storage pool so that scratch volumes are not used.

      • The default setting for primary storage pools is collocation by group. The default for copy storage pools and active-data pools is disablement of collocation. Collocation is a process by which the server attempts to keep all files that belong to a group of client nodes, a single client node, a client file space, or a group of client file spaces on a minimal number of volumes. If collocation is disabled for a storage pool and clients begin storing data, you cannot easily change the data in the pool so that it is collocated. To understand the advantages and disadvantages of collocation, see Keeping client files together using collocation and How collocation affects reclamation.
   7. Check in and label library volumes.

      Ensure that enough volumes in the library are available to the server. Keep enough labeled volumes on hand so that you do not run out during an operation such as client backup. Label and set aside extra scratch volumes for any potential recovery operations that you might have later.

      The procedures for volume check-in and labeling are the same whether the library contains drives of a single device type, or drives of multiple device types. You can use the CHECKIN LIBVOLUME command to check in volumes that are already labeled. Or, if you want to label and check in volumes with one step, issue the LABEL LIBVOLUME command.

      Note: If your library has drives of multiple device types, and you defined two libraries to the Tivoli Storage Manager server, the two libraries represent one physical library. You must check in media separately to each defined library. Ensure that you check in volumes to the correct Tivoli Storage Manager library.
6. Verify your device definitions to ensure that everything is configured correctly. Use the QUERY command to review information about each storage object.

   When you issue QUERY DRIVE, verify that the device type for the drive is what you are expecting. If a path is not defined, the drive device type is listed as UNKNOWN and if the wrong path is used, GENERIC_TAPE or another device type is shown. This step is especially important when you are using mixed media.