ACSLS-Managed libraries

Tivoli Storage Manager supports tape libraries controlled by StorageTek Automated Cartridge System Library Software (ACSLS). The ACSLS library server manages the physical aspects of tape cartridge storage and retrieval. The ACSLS client application communicates with the ACSLS library server to access tape cartridges in an automated library. Tivoli Storage Manager is one of the applications that gains access to tape cartridges by interacting with ACSLS through its client, which is known as the control path. The Tivoli Storage Manager server reads and writes data on tape cartridges by interacting directly with tape drives through the data path. The control path and the data path are two different paths. The ACSLS client daemon must be initialized before starting the server. See /usr/tivoli/tsm/devices/bin/rc.acs_ssi for the client daemon invocation. For detailed installation, configuration, and system administration of ACSLS, refer to the appropriate StorageTek documentation. The ACSLS client daemon must be initialized before starting the server. See the script rc.acs_ssi in the server's installation directory for the client daemon invocation. For detailed installation, configuration, and system administration of ACSLS, refer to the appropriate StorageTek documentation. The ACSLS client daemon must be initialized before starting the server. See /opt/tivoli/tsm/devices/bin/rc.acs_ssi for the client daemon invocation. For detailed installation, configuration, and system administration of ACSLS, refer to the appropriate StorageTek documentation.

Configuring an ACSLS-managed library The library ACSLS is attached to the ACSLS server, and the drives are attached to the Tivoli Storage Manager server. The ACSLS server and theTivoli Storage Manager server must be on different systems. Refer to the ACSLS installation documentation for details about how to set up the library. Configuring an ACSLS library with a single drive device type The parameter ACSID specifies the number that the Automatic Cartridge System System Administrator (ACSSA) assigned to the library. Issue the QUERY ACS command to your ACSLS system to determine the number for your library ID. Configuring an ACSLS library with multiple drive device types The following example shows how to set up and ACSLS library with a mix of two 9840 drives and two 9940 drives. Setting up an ACSLS library manager server You can configure an ACSLS library so that it contains all drives of the same device type. In addition, you can configure an ACSLS library so that it contains drives of different device types or different generations of drives. Setting up an ACSLS library client server You must set up the server that is the library manager server before you set up the servers that are the library clients. Checking in and labeling ACSLS library volumes Ensure that enough volumes are available to the server in the library. You must label volumes that do not already have a standard label. Keep enough labeled volumes on hand so that you do not run out during an operation such as client backup.

Configuring an ACSLS-managed library

The library ACSLS is attached to the ACSLS server, and the drives are attached to the Tivoli Storage Manager server. The ACSLS server and the Tivoli Storage Manager server must be on different systems. Refer to the ACSLS installation documentation for details about how to set up the library. There are two configurations described in this section:

In the first configuration, both drives in the ACSLS library are the same device type. See Configuring an ACSLS library with a single drive device type

In the second configuration, the drives are different device types. Drives with different device types (or different generations of drives) are supported in a single physical library if you define one library toTivoli Storage Manager for each type of drive (or generation of drive). If you have two device types, such as 9840 and 9940 (or two generations of drives of the same device type), define two libraries. Then define drives and device classes for each library. In each device class definition, you can use the FORMAT parameter with a value of DRIVE, if you choose.

Configuring an ACSLS library with a single drive device type

The parameter ACSID specifies the number that the Automatic Cartridge System System Administrator (ACSSA) assigned to the library. Issue the QUERY ACS command to your ACSLS system to determine the number for your library ID. 1. Define an ACSLS library named ACSLIB: define library acslib libtype=acsls acsid=1 2. 3. Define the drives in the library: define drive acslib drive01 acsdrvid=1,2,3,4 define drive acslib drive02 acsdrvid=1,2,3,5 The ACSDRVID parameter specifies the ID of the drive that is being accessed. The drive ID is a set of numbers that indicate the physical location of a drive within an ACSLS library. This drive ID must be specified as a, l, p, d, where a is the ACSID, l is the LSM (library storage module), p is the panel number, and d is the drive ID. The server needs the drive ID to connect the physical location of the drive to the drive's SCSI address. See the StorageTek documentation for details. See 4. 5. 6. 7. 8. Define a path from the server to each drive: define path server1 drive01 srctype=server desttype=drive library=acslib device=/dev/mt0 define path server1 drive02 srctype=server desttype=drive library=acslib device=/dev/mt1 define path server1 drive01 srctype=server desttype=drive library=acslib device=/dev/rmt/tsmmt0 define path server1 drive02 srctype=server desttype=drive library=acslib device=/dev/rmt/tsmmt1 define path server1 drive01 srctype=server desttype=drive library=acslib device=/dev/tsmscsi/mt0 define path server1 drive02 srctype=server desttype=drive library=acslib device=/dev/tsmscsi/mt1 define path server1 drive01 srctype=server desttype=drive library=acslib device=/dev/rmt/0mt define path server1 drive02 srctype=server desttype=drive library=acslib device=/dev/rmt/1mt The DEVICE parameter gives the device special file name for the drive. For more about device names, seeDevice special file names. For more information about paths, see Defining paths. 9. Classify drives according to type by defining Tivoli Storage Manager device classes. For example, to classify the two drives in the ACSLIB library, issue the following command to define a device class named ACS_CLASS: Defining drives .

define devclass acs_class library=acslib devtype=ecartridge format=drive This example uses FORMAT=DRIVE as the recording format because both drives associated with the device class use the same recording format; for example, both are 9940 drives. If instead one drive is a 9840 and one is a 9940, you must use specific recording formats when defining the device classes. See Configuring an ACSLS library with multiple drive device types. See Defining tape and optical device classes. 10. To check what you have defined, issue the following commands: 11. query library 12. query drive 13. query path query devclass See the following topics: o Obtaining information about device classes o Requesting information about libraries o Requesting information about paths o Requesting information about drives 14. Create the storage pool to use the devices in the device class you just defined. For example, define a storage pool named ACS_POOL associated with the device class ACS_CLASS: define stgpool acs_pool acs_class maxscratch=20 Key choices: a. Scratch volumes are labeled, 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. b. 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 belonging to a group of client nodes, a single client node, or a client file space 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.

Configuring an ACSLS library with multiple drive device types

The following example shows how to set up and ACSLS library with a mix of two 9840 drives and two 9940 drives. 1. Define two ACSLS libraries that use the same ACSID. For example to define 9840LIB and 9940LIB, enter the following commands: define library 9840lib libtype=acsls acsid=1 define library 9940lib libtype=acsls acsid=1 The ACSID parameter specifies the number that the Automatic Cartridge System System Administrator (ACSSA) assigned to the libraries. Issue the QUERY ACS command to your ACSLS system to determine the number for your library ID. 3. Define the drives, ensuring that they are associated with the appropriate libraries. Note: Tivoli Storage Manager does not prevent you from associating a drive with the wrong library.

2.

o o o

Define the 9840 drives to 9840LIB. define drive 9840lib 9840_drive1 acsdrvid=1,2,3,1 define drive 9840lib 9840_drive2 acsdrvid=1,2,3,2 Define the 9940 drives to 9940LIB.

define drive 9940lib 9940_drive3 acsdrvid=1,2,3,3 define drive 9940lib 9940_drive4 acsdrvid=1,2,3,4

The ACSDRVID parameter specifies the ID of the drive that is being accessed. The drive ID is a set of numbers that indicate the physical location of a drive within an ACSLS library. This drive ID must be specified as a, l, p, d, where a is the ACSID, l is the LSM (library storage module), p is the panel number, and d is the drive ID. The server needs the drive ID to connect the physical location of the drive to the drive's SCSI address. See the StorageTek documentation for details. See 4. Defining drives.

Define a path from the server to each drive. Ensure that you specify the correct library.

o o o o o

For the 9840 drives: define path server1 9840_drive1 srctype=server desttype=drive library=9840lib device=/dev/mt0 define path server1 9840_drive2 srctype=server desttype=drive library=9840lib device=/dev/mt1 define path server1 9840_drive1 srctype=server desttype=drive library=9840lib device=/dev/rmt/tsmmt0 define path server1 9840_drive2 srctype=server desttype=drive library=9840lib device=/dev/rmt/tsmmt1 define path server1 9840_drive1 srctype=server desttype=drive library=9840lib device=/dev/tsmscsi/mt0 define path server1 9840_drive2 srctype=server desttype=drive library=9840lib device=/dev/tsmscsi/mt1 define path server1 9840_drive1 srctype=server desttype=drive library=9840lib device=/dev/rmt/0mt define path server1 9840_drive2 srctype=server desttype=drive library=9840lib device=/dev/rmt/1mt For the 9940 drives: define path server1 9940_drive3 srctype=server desttype=drive library=9940lib device=/dev/mt2 define path server1 9940_drive4 srctype=server desttype=drive library=9940lib device=/dev/mt3 define path server1 9940_drive3 srctype=server desttype=drive library=9940lib device=/dev/rmt/tsmmt2 define path server1 9940_drive4 srctype=server desttype=drive library=9940lib device=/dev/rmt/tsmmt3 define path server1 9940_drive3 srctype=server desttype=drive library=9940lib device=/dev/tsmscsi/mt2 define path server1 9940_drive4 srctype=server desttype=drive library=9940lib device=/dev/tsmscsi/mt3 define path server1 9940_drive3 srctype=server desttype=drive library=9940lib device=/dev/rmt/2mt

o o o o o

5.

define path server1 9940_drive4 srctype=server desttype=drive library=9940lib device=/dev/rmt/3mt The DEVICE parameter gives the device special file name for the drive. For more about device names, seeDevice special file names. For more information about paths, see Defining paths. Classify the drives according to type by defining Tivoli Storage Manager device classes, which specify the recording formats of the drives. Because there are separate libraries, you can enter a specific recording format, for example 9840, or you can enter DRIVE. For example, to classify the drives in the two libraries, use the following commands to define one device class for each type of drive: define devclass 9840_class library=9840lib devtype=ecartridge format=9840 define devclass 9940_class library=9940lib devtype=ecartridge format=9940 See Defining tape and optical device classes.

6.

7. 8.

9.

To check what you have defined, enter the following commands:

10. query library 11. query drive 12. query path query devclass See the following topics: o Requesting information about libraries o Obtaining information about device classes o Requesting information about paths o Requesting information about drives 13. Create the storage pools to use the devices in the device classes that you just defined. For example, define storage pools named 9840_POOL associated with the device class 9840_CLASS and 9940_POOL associated with the device class 9940_CLASS: 14. define stgpool 9840_pool 9840_class maxscratch=20 15. define stgpool 9940_pool 9940_class maxscratch=20 Key choices: a. Scratch volumes are labeled, 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. b. 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 belonging to a group of client nodes, a single client node, or a client file space 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.

Setting up an ACSLS library manager server

You can configure an ACSLS library so that it contains all drives of the same device type. In addition, you can configure an ACSLS library so that it contains drives of different device types or different generations of drives. You can modify the procedure described for configuring a library for use by one server (Configuration with multiple drive device types) and use it for configuring a shared library. You must set up the server that is the library manager before you set up servers that are the library clients. When upgrading multiple servers participating in library sharing to Version 5.3, upgrade all the servers at once, or upgrade the library manager servers and then the library client servers. A Version 5.3 library manager server is compatible with downlevel library clients. However, 5.3 library clients are not compatible with a library manager server that is at a level earlier than 5.3. Note: An exception to this rule is when a fix or product enhancement requires concurrent code changes to the server, storage agent, and library client.

The following example procedure describes how to set up a server named GLENCOE as a library manager. Perform the following steps on the server GLENCOE: 1. Define a server as a library client server named WALLACE: define server wallace HLA=x.x.x.x LLA=y 2. Define a shared ACSLS library named MACGREGOR: define library macgregor libtype=acsls shared=yes acsid=1 This example used an ACSLS managed library configured as acs 1. 3. Define all the device classes that are associated with the shared library MACGREGOR: define devclass tape library=macgregor devtype=9840 4. 5. Define the drives in the library MACGREGOR: define drive macgregor drivea acsdrvid=1,0,1,0 define drive macgregor driveb acsdrvid=1,0,1,1 This example uses the acsdrvid value, which specifies the ID of the drive that is being accessed in an ACSLS library. The drive ID is a set of numbers that indicates the physical location of a drive within an ACSLS library. This drive ID must be specified as a,l,p,d, where a is the ACSID, l is the LSM (library storage module), p is the panel number, and d is the drive ID. The server needs the drive ID to connect the physical location of the drive to the drive's SCSI address. See the StorageTek documentation for details. 6. 7. 8. 9. Define a path from the server GLENCOE to each drive in the library MACGREGOR: define path glencoe drivea srctype=server desttype=drive library=macgregor device=/dev/rmt4 define path glencoe driveb srctype=server desttype=drive library=macgregor device=/dev/rmt5 define path glencoe drivea srctype=server desttype=drive library=macgregor device=/dev/rmt/tsmmt4 define path glencoe driveb srctype=server desttype=drive library=sangroup device=/dev/rmt/tsmmt5 define path glencoe drivea srctype=server desttype=drive library=macgregor device=/dev/IBMtape4 define path glencoe driveb srctype=server desttype=drive library=macgregor device=/dev/IBMtape5 define path glencoe drivea srctype=server desttype=drive library=macgregor device=/dev/rmt/4mt define path glencoe driveb srctype=server desttype=drive library=macgregor device=/dev/rmt/5mt

Setting up an ACSLS library client server

You must set up the server that is the library manager server before you set up the servers that are the library clients. Use the following sample procedure for each Tivoli Storage Manager server that will be a library client. The library client server is named WALLACE. With the exception of one step, perform the procedure from the library client server. 1. 2. Define the server that is the library manager: define server glencoe serverpassword=secret hladdress=9.115.3.45 lladdress=1580 crossdefine=yes

3.

Define the shared library named MACGREGOR, and identify the library manager server's name as the primary library manager. Ensure that the library name is the same as the library name on the library manager: define library macgregor libtype=shared primarylibmanager=glencoe

4.

Perform this step from the library manager. Define a path from the library client server to each drive that the library client server will be allowed to access. The device name should reflect the way the library client system sees the device. There must be a path defined from the library manager to each drive in order for the library client to use the drive. The following is an example of how to define a path: define path wallace drivea srctype=server desttype=drive library=macgregor device=/dev/rmt6 define path wallace driveb srctype=server desttype=drive library=macgregor device=/dev/rmt7 define path wallace drivea srctype=server desttype=drive library=macgregor device=/dev/rmt/6m define path wallace driveb srctype=server desttype=drive library=macgregor device=/dev/rmt/7m define path wallace drivea srctype=server desttype=drive library=macgregor device=/dev/IBMtape6 define path wallace driveb srctype=server desttype=drive library=macgregor device=/dev/IBMtape7 define path wallace drivea srctype=server desttype=drive library=macgregor device=/dev/rmt/6mt define path wallace driveb srctype=server desttype=drive library=macgregor device=/dev/rmt/7mt For more information about paths, see Defining paths. Defining paths

5. 6. 7.

8.

Return to the library client for the remaining steps. Define all the device classes that are associated with the shared library: define devclass tape library=macgregor devtype=9840 define devclass tape library=macgregor devtype=lto Set the parameters for the device class the same on the library client as on the library manager. Making the device class names the same on both servers is also a good practice, but is not required. The device class parameters specified on the library manager server override those specified for the library client. This is true whether or not the device class names are the same on both servers. If the device class names are different, the library manager uses the parameters specified in a device class that matches the device type specified for the library client. Note: If a library client requires a setting that is different from what is specified in the library manager's device class (for example, a different mount limit), do the following: a. b. Create an additional device class on the library manager server. Specify the parameter settings you want the library client to use. Create a device class on the library client with the same name and device type as the new device class you created on the library server.

9.

Define the storage pool, LOCHNESS, that will use the shared library: define stgpool lochness tape maxscratch=50

10. Repeat this procedure to define additional servers as library clients.

Checking in and labeling ACSLS library volumes

Ensure that enough volumes are available to the server in the library. You must label volumes that do not already have a standard label. Keep enough labeled volumes on hand so that you do not run out during an operation such as client backup. Each volume used by a server for any purpose must have a unique name. This requirement applies to all volumes, whether the volumes are used for storage pools, or used for operations such as database backup or export. The requirement also applies to volumes that reside in different libraries. Tip: If your library has drives of multiple device types, you defined two libraries to the Tivoli Storage Manager server in the procedure inConfiguring an ACSLS library with multiple drive device types. The two Tivoli Storage Manager libraries represent the one physical library. The check-in process finds all available volumes that are not already checked in. You must check in media separately to each defined library. Ensure that you check in volumes to the correct Tivoli Storage Manager library. 1. Check in the library inventory. The following shows examples for libraries with a single drive device type and with multiple drive device types.

o o
2.

Check in volumes that are already labeled: checkin libvolume acslib search=yes status=scratch checklabel=no Label and check in volumes: label libvolume acslib search=yes overwrite=no checkin=scratch

Depending on whether you use scratch volumes or private volumes, do one of the following:

If you use only scratch volumes, ensure that enough scratch volumes are available. For example, you may need to label more volumes. As volumes are used, you may also need to increase the number of scratch volumes allowed in the storage pool that you defined for this library. o If you want to use private volumes in addition to or instead of scratch volumes in the library, define volumes to the storage pool you defined. The volumes you define must have been already labeled and checked in. See Defining storage pool volumes. For more information about checking in volumes, see Checking new volumes into a library

Configuring an ACSLS library with multiple drive device types

The following example shows how to set up and ACSLS library with a mix of two 9840 drives and two 9940 drives. 1. Define two ACSLS libraries that use the same ACSID. For example to define 9840LIB and 9940LIB, enter the following commands: define library 9840lib libtype=acsls acsid=1 define library 9940lib libtype=acsls acsid=1 The ACSID parameter specifies the number that the Automatic Cartridge System System Administrator (ACSSA) assigned to the libraries. Issue the QUERY ACS command to your ACSLS system to determine the number for your library ID. 3. Define the drives, ensuring that they are associated with the appropriate libraries. Note: Tivoli Storage Manager does not prevent you from associating a drive with the wrong library.

2.

o o o o

Define the 9840 drives to 9840LIB. define drive 9840lib 9840_drive1 define drive 9840lib 9840_drive2 Define the 9940 drives to 9940LIB. define drive 9940lib 9940_drive3 define drive 9940lib 9940_drive4

acsdrvid=1,2,3,1 acsdrvid=1,2,3,2 acsdrvid=1,2,3,3 acsdrvid=1,2,3,4

The ACSDRVID parameter specifies the ID of the drive that is being accessed. The drive ID is a set of numbers that indicate the physical location of a drive within an ACSLS library. This drive ID must be specified as a, l, p, d, where a is the ACSID, l is the LSM (library storage module), p is the panel number, and d is the drive ID. The server needs the drive ID to connect the physical location of the drive to the drive's SCSI address. See the StorageTek documentation for details.

See 4.

Defining drives.

Define a path from the server to each drive. Ensure that you specify the correct library.

o o o o o

For the 9840 drives: define path server1 9840_drive1 srctype=server desttype=drive library=9840lib device=/dev/mt0 define path server1 9840_drive2 srctype=server desttype=drive library=9840lib device=/dev/mt1 define path server1 9840_drive1 srctype=server desttype=drive library=9840lib device=/dev/rmt/tsmmt0 define path server1 9840_drive2 srctype=server desttype=drive library=9840lib device=/dev/rmt/tsmmt1 define path server1 9840_drive1 srctype=server desttype=drive library=9840lib device=/dev/tsmscsi/mt0 define path server1 9840_drive2 srctype=server desttype=drive library=9840lib device=/dev/tsmscsi/mt1 define path server1 9840_drive1 srctype=server desttype=drive library=9840lib device=/dev/rmt/0mt define path server1 9840_drive2 srctype=server desttype=drive library=9840lib device=/dev/rmt/1mt For the 9940 drives: define path server1 9940_drive3 srctype=server desttype=drive library=9940lib device=/dev/mt2 define path server1 9940_drive4 srctype=server desttype=drive library=9940lib device=/dev/mt3 define path server1 9940_drive3 srctype=server desttype=drive library=9940lib device=/dev/rmt/tsmmt2 define path server1 9940_drive4 srctype=server desttype=drive library=9940lib device=/dev/rmt/tsmmt3 define path server1 9940_drive3 srctype=server desttype=drive library=9940lib device=/dev/tsmscsi/mt2 define path server1 9940_drive4 srctype=server desttype=drive library=9940lib device=/dev/tsmscsi/mt3 define path server1 9940_drive3 srctype=server desttype=drive library=9940lib device=/dev/rmt/2mt

o o o o o

5.

define path server1 9940_drive4 srctype=server desttype=drive library=9940lib device=/dev/rmt/3mt The DEVICE parameter gives the device special file name for the drive. For more about device names, seeDevice special file names. For more information about paths, see Defining paths. Classify the drives according to type by defining Tivoli Storage Manager device classes, which specify the recording formats of the drives. Because there are separate libraries, you can enter a specific recording format, for example 9840,

6.

or you can enter DRIVE. For example, to classify the drives in the two libraries, use the following commands to define one device class for each type of drive: 7. 8. define devclass 9840_class library=9840lib devtype=ecartridge format=9840 define devclass 9940_class library=9940lib devtype=ecartridge format=9940 See Defining tape and optical device classes. 9. To check what you have defined, enter the following commands:

10. query library 11. query drive 12. query path query devclass See the following topics: o Requesting information about libraries o Obtaining information about device classes o Requesting information about paths o Requesting information about drives 13. Create the storage pools to use the devices in the device classes that you just defined. For example, define storage pools named 9840_POOL associated with the device class 9840_CLASS and 9940_POOL associated with the device class 9940_CLASS: 14. define stgpool 9840_pool 9840_class maxscratch=20 15. define stgpool 9940_pool 9940_class maxscratch=20 Key choices: a. Scratch volumes are labeled, 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. b. 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 belonging to a group of client nodes, a single client node, or a client file space 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.