IBM Tivoli Storage Manager Version 5.3 Technical Workshop Presentation Guide

Chapter 2. Server enhancements 11

2.1 ACSLS support

Figure 2-2 ACSLS enhancements

IBM Tivoli Storage Manager supports tape libraries that are controlled by StorageTek’s

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

the /usr/tivoli/tsm/devices/bin/rc.acs_ssi path for the client daemon invocation. For detailed

installation, configuration, and system administration of ACSLS, refer to the appropriate

StorageTek documentation.

The following commands have changed:

򐂰 DEFINE LIBRARY

򐂰 UPDATE LIBRARY

ibm.com/redbooks

International Technical Support Organization

8

© 2005 IBM Corporation

IBM ITSO – International Technical Support Organization

Server enhancements

•ACSLS library support

–Provide the basic support to share ACSLS libraries across Tivoli

Storage Manager servers in the same way that SCSI libraries

are shared

–Support a LAN-free data movement using libraries that are

controlled by the StorageTek’s ACSLS interface, which has also

been provided

–As a result, the use of a third-party product is no longer required.

12 IBM Tivoli Storage Manager Version 5.3 Technical Workshop Presentation Guide

Figure 2-3 ACSLS implementation example

This slide helps to give you a better understanding of how a shared Tivoli Storage Manager

and ACSLS environment might look. Refer to the following explanation of the abbreviations

that are used in this slide:

򐂰 Client System Component (CSC)

򐂰 Client System Interface (CSI)

򐂰 Automated Cartridge System Library Software (ACSLS)

򐂰 Tivoli Storage Manager Subsystem Interface (TSM SSI)

Beginning with version 5.3, Tivoli Storage Manager supports ACSLS library sharing among

multiple Tivoli Storage Manager servers using native Tivoli Storage Manager library sharing.

When configured to use library sharing, one Tivoli Storage Manager server acts as the library

manager, and the rest act as library clients.

Such Tivoli Storage Manager library operations as checkin, checkout, label, mount and

dismount are controlled by the library manager. When library clients need tape resources,

they contact the Tivoli Storage Manager library manager via TCP/IP to make the request.

With ACSLS, the Tivoli Storage Manager library manager contacts ACSLS via TCP/IP which

ultimately fulfills the request.

The following example demonstrates how to set up Tivoli Storage Manager library sharing

with ACSLS. The ACSLS software is installed on a separate server running Solaris™, and the

ACSID is set to 0.

ibm.com/redbooks

International Technical Support Organization

9

© 2005 IBM Corporation

IBM ITSO – International Technical Support Organization

Server enhancements

•ACSLS library support

Chapter 2. Server enhancements 13

Set up the library manager, library client, and shared library. In the following sequence, the

first line indicates the action to perform and the command that follows is what you enter at the

command line.

# set password for the library manager (san_server1)

set serverpassword password1

# set password for the library client (san_server2)

set serverpassword password2

# define the lib client to the lib manager

define server san_server2 serverpassword=password2 hla=9.11.232.143 lla=1501

# define the lib manager to the lib client

define server san_server1 serverpassword=password1 hla=9.11.232.143 lla=1500

# define the lib manager library on the lib master

define library 9710lib libtype=acsls acsid=0 shared=yes

# define the paths to the drives for the lib manager on the lib manager

define path san_server1 drive1 srctype=server desttype=drive library=9710lib

device=mt1.4.0.7

define path san_server1 drive2 srctype=server desttype=drive library=9710lib

device=mt1.5.0.7

# define the lib client library on the lib client

define library 9710lib libtype=shared primarylibmanager=sannt5_server1

# define the paths to the drives for the lib client on the lib manager

define path san_server2 drive1 srctype=server desttype=drive library=9710lib

device=mt1.4.0.7

define path san_server2 drive2 srctype=server desttype=drive library=9710lib

device=mt1.5.0.7

# define the device class and storage pool on the library master

define devclass 9840class library=9710lib devtype=ecartridge

define stg 9710pool_master 9840class maxscratch=100

# define the device class and storage pool on the library client

define devclass 9840class library=9710lib devtype=ecartridge

define stg 9710pool_client 9840class maxscratch=50

The library sharing is now set up. You can use the defined device class and defined storage

pools to start the backups.