Configuring libraries for use by a server

To use a library or libraries for storage for an IBM Storage Protect server, you must first set up the devices on the server system.

1. Define the library and the path from the server to the library. Follow the instructions in Defining libraries.
2. Define the drives in the library. Follow the instructions in Defining drives.

   For SCSI libraries, you can use the PERFORM LIBACTION command to define drives and paths for a library in one step, instead of completing both steps 2 and 3. To use the PERFORM LIBACTION command to define drives and paths for a library, the SANDISCOVERY option must be supported and enabled.

3. Define a path from the server to each drive by using the DEFINE PATH command.
4. Define a device class. Follow the instructions in Defining tape device classes.

   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 that are associated with the device class can read and write to all of the media.

   For example, you have a mix of Ultrium Generation 3 and Ultrium Generation 4 drives, but you have only 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.
5. Define a storage pool by using the DEFINE STGPOOL command.
   Consider the following key choices for defining storage pools:

   • Scratch volumes are empty volumes that are available for use. If you specify a value for the maximum number of scratch volumes in the storage pool, the server can choose from the scratch volumes available in the library.

     If you do not allow scratch volumes, you must complete the extra step of explicitly defining each volume to be used in the storage pool. Also, specify the MAXSCRATCH=0 parameter 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. The server uses collocation 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.
6. Check in and label library volumes. Follow the instructions in Checking volumes into an automated library and Labeling tape 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 extra scratch volumes for any potential recovery operations that you might have later.

   The procedures for checking in and labeling volumes 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.

   Libraries with multiple device types: If your library has drives of multiple device types, and you defined two libraries to the IBM Storage Protect server, the two defined libraries represent one physical library. You must check in tape volumes separately to each defined library. Ensure that you check in volumes to the correct IBM Storage Protect library.