![]() |
![]() |
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 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 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 initalized 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 library 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.
define library acslib libtype=acsls acsid=1
The parameter ACSID specifies the number that Automatic Cartridge System System Administrator (ACSSA) assigned to the library. Issue QUERY ACS in your system to determine the number for your library ID.
define path server1 acslib srctype=server desttype=library acsid=1
For more information about paths, see Defining Paths.
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 numbesr 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 ofthe drive to the drive's SCSI address. See the Storage Tek documentation for details.
See Defining Drives.
define path server1 drive01 srctype=server desttype=drive library=acslib device=/dv/mt0 define path server1 drive02 srctype=server desttype=drive library=acslib device=/dv/mt1
The DEVICE parameter specifies the device special file for the drive. In this example, each drive is given a Tivoli Storage Manager name 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.
define devclass acs_class library=acslib devtype=ecartridge format=drive
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.
define stgpool acs_pool acs_class maxscratch=20
Key choices:
For more information, see Defining or Updating Primary Storage Pools.
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.
checkin libvolume acslib search=yes status=scratch checklabel=no
label libvolume acslib search=yes overwrite=no checkin=scratch
After you have attached and defined your devices, you can store client data in two ways: