tivoli storage manager for aix - ibm supportpublib.boulder.ibm.com/tividd/td/smaixn/gc36-0001... ·...

Tivoli® Storage Managerfor AIXManaged System for SANStorage Agent User’s GuideVersion 4 Release 2 GC36-0001-01

Note!Before using this information and the product it supports, be sure to read the general information under “Notices” on page 41.

Second Edition (September 2001)

This edition applies to Version 4 Release 2.1 of Tivoli Storage Manager (product number 5698-TSM) and to anysubsequent releases until otherwise indicated in new editions or technical newsletters.

Changes since the June 2001 edition are marked with a vertical bar (|) in the left margin. Ensure that you are using thecorrect edition for the level of the product.

Order publications through your sales representative or the branch office that serves your locality.

Your feedback is important in helping to provide the most accurate and high-quality information. If you have anycomments about this book or any other Tivoli Storage Manager documentation, please see “Contacting CustomerSupport” on page 37.

© Copyright International Business Machines Corporation 2000, 2001. All rights reserved.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

||

||

Contents

About This Book. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Summary of Changes for Tivoli Storage Manager. . . . . . . . . . . . . . . . . . . . . . . . viiTechnical Changes for Version 4 Release 2.1—September 2001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Chapter 1. Storage Agent Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1LAN-free Client Data Backup Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Dual-session No-Query Restore for LAN-free Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Chapter 2. Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Types of Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Sharing Tape Storage using TSM Library Manager/Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Sharing Disk Storage using Tivoli SANergy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

External Library — Sharing ACSLS-Managed Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 3. Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Summary of Tasks for Procedure 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Summary of Tasks for Procedure 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Procedure 1–Tape and File Sharing with SCSI and 349X Tape and File Devices. . . . . . . . . . . . . . . . 11

Step 1. Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Establishing communications among client, storage agent, and server . . . . . . . . . . . . . . . . . . . . . . . . 11

Step 2. Client System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Step 3. Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Configuring Devices for the Storage Agent to Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17


Step 5. Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Step 6. Client System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Start the Storage Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Verify the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Procedure 2 —External Library Environment with an ACSLS-Managed Library . . . . . . . . . . . . . . . . 20

Step 1. Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Establishing communications among client, storage agent, and server . . . . . . . . . . . . . . . . . . . . 21

Configuring Devices for the Storage Agent to Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27


Appendix A. Administration and Configuration Reference . . . . . . . . . . . . . . 29Starting and Stopping the Storage Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

iiiTivoli® Storage Manager for AIX Managed System for SAN Storage Agent User’s Guide

||

||

||

||

||

||

||

||

||

||

||

||

||

||

Obtaining Tape Device Information on the Client System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Set Installation Data for the Storage Agent: DSMSTA SETSTORAGESERVER . . . . . . . . . . . . . . . . 30

The Storage Agent Options File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

The Device Configuration File for the Storage Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Appendix B. Legacy ACSLS Data Migration and Coexistence. . . . . . . . . . . 35Data Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Data Coexistence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Appendix C. Where to Look for Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Reporting a Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Tivoli Storage Manager Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Related IBM Hardware Products Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Translations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Appendix D. Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

iv Version 4 Release 2

||

||

||

||

||

||

||

||

||

||

||

||

About This Book

This user’s guide is intended for anyone who will be using the Tivoli Managed System forSAN product, commonly referred to as the storage agent. This document provides anoverview of LAN-free data transfer. It also provides detailed explanations about configuringand using the Tivoli Storage Manager (TSM) client, storage agent, and TSM server. Youshould be familiar with TSM, SAN, and operating system administration. You may requireadditional publications during configuration of the storage agent environment. Refer to thelisting of Tivoli Storage Manager Publications in “Where to Look for Information” onpage 37.

Note: Tivoli Managed System for SAN is only supported in US English. At the time ofpublishing this document no other language support was available.

For information about Tivoli Storage Manager, seehttp://www.tivoli.com/support/storage_mgr/tivolimain.html.

vTivoli® Storage Manager for AIX Managed System for SAN Storage Agent User’s Guide

||||||||

http://www.tivoli.com/support/storage_mgr/tivolimain.html

vi Version 4 Release 2

Summary of Changes for Tivoli Storage Manager

This section summarizes changes made to the Storage Agent product and to this publication.

Technical Changes for Version 4 Release 2.1—September 2001The following changes have been made to the product for this edition:

Device support enhancements

¶ LAN-free external library interface support allows access to LAN-free datatransfer for TSM Servers sharing access to ACSLS-managed libraries (that is, aStorageTek llibrary controlled by Automated Cartridge System Library Software(ACSLS) software or Library Station). This publication provides additionalinformation.

¶ Tivoli Storage Manager servers can now share tape drives in a StorageTeklibrary managed by ACSLS or LibraryStation software. Gresham Extended DataTechnology DistribuTAPE (EDT-DistribuTAPE) is a middleware softwareprogram that takes advantage of Tivoli Storage Manager’s external libraryinterface to allow tape drives in ACSLS libraries to be shared among servers.This support allows a storage agent to access an external library for LAN-freeoperations.

viiTivoli® Storage Manager for AIX Managed System for SAN Storage Agent User’s Guide

|

|

|

|||||

|||||||

viii Version 4 Release 2

Storage Agent Overview

Managed System for SAN is a feature of Tivoli Storage Manager (TSM) that enablesLAN-free TSM client data movement. The TSM client data moves directly to and from astorage device attached to a Storage Area Network (SAN), thereby off-loading the datamovement from the LAN and from the Tivoli Storage Manager server. The storage agent isinstalled on the client machine and shares storage resources with the Tivoli Storage Managerserver. The storage agent can write directly to storage media in a format that is consistentwith that used by the server. The TSM server or servers control the storage devices and keeptrack of the data that the client has stored. TSM continues to use a LAN connection toexchange control information, such as policy information and data about the objects that arebacked up. Using the SAN for client data movement decreases the load on the TSM serverand allows the server to support a greater number of simultaneous client connections. SeeFigure 1.

To use Managed System for SAN you must install a storage agent on the client system. Thestorage agent communicates with the server to obtain and store database information and tocoordinate device and volume access. The server determines if the client is requesting access

TSM ClientStorage Agent installed

Tape Library

File Library

Library ControlClient Metadata

LibraryControl

ClientData

SAN

LAN

TSM Server

Figure 1. SAN Data Movement. Solid lines indicate data movement. Broken lines indicate movement of controlinformation and metadata.

1

1Tivoli® Storage Manager for AIX Managed System for SAN Storage Agent User’s Guide

|

||||

|

||||||||||||

1.S

torag

eA

gen

tO

verview

to storage for which the client has a SAN path defined. If a SAN path is defined, the client(by means of the storage agent) transfers data on that path. If a failure occurs on the SANpath, failover occurs and the client uses its LAN connection to the TSM server and movesthe client data over the LAN.

TSM supports SAN-attached device sharing in one of the following ways:

¶ TSM native library management support consisting of a library manager and libraryclients or just a library manager.

¶ Shared disk storage using a FILE library and the integration of the Tivoli SANergy™

product.

¶ External library support, in that tape libraries managed by StorageTek AutomatedCartridge System Library Software (ACSLS) and middleware that enables TSM to shareACSLS-managed libraries. In this environment the device sharing capability is providedby third-party software, such as Gresham Extended Data Technology DistribuTAPE(EDT-DistribuTAPE) a middleware software program that takes advantage of TSM’sexternal library interface to allow tape drives in ACSLS-managed libraries to be sharedamong TSM servers.

For additional information about these configurations, see “Types of Configurations” onpage 3.

LAN-free Client Data Backup ScenarioThe following outlines a typical backup scenario for a TSM client that uses SAN datamovement. This scenario does not apply to External library environments.

1. The client begins a backup operation. The client and the server exchange policyinformation over the LAN to determine the destination of the backed up data.

For a client using LAN-free data movement, the destination is a storage pool that uses adevice on the SAN. That device must also be mapped for the client.

2. Because the destination is on the SAN, the client contacts the storage agent, which willhandle the data transfer. The storage agent sends a request for a volume mount to theserver.

3. The server contacts the storage device and mounts the appropriate media.

4. The server notifies the client of the location where the mounted media resides.

5. The client, by means of the storage agent, writes the backup data directly to the deviceover the SAN.

6. The storage agent sends file attribute information to the TSM server, and the serverstores the information in its database.

Dual-session No-Query Restore for LAN-free PathWhen performing a No-Query restore the TSM server builds a list of files to restore andsends data to the client while continuing to build the list. This type of restore is moreefficient especially in a LAN-free environment. Two sessions are used for the restore whendata for the restore resides on devices with a LAN-free path and devices with a LAN-onlypath. One session restores data from the server with a LAN-only path. The other sessionuses the storage agent to restore data over the LAN-free path. This works only with clientsat the 4.2 level or above.

2 Version 4 Release 2

|

||

||

|||||||

||

|

Planning

You can set up a Managed System for SAN in a number of configurations. Planning thesystem configuration provides a smooth transition through system setup and into production.As part of your planning, you need to identify the following:

¶ Which configuration to implement

¶ Devices to be used for LAN-free data movement

¶ Clients to use LAN-free data movement

¶ For tape libraries (except, ACSLS-managed StorageTek tape libraries), which servers,library manager or library client, manage which client’s data.

Types of ConfigurationsThere are several common types of configurations that take advantage of what can beaccomplished using a storage agent in a LAN-free environment. Your environment isdependent upon the type of storage device you will be using for LAN-free data storage. Thefollowing sections cover descriptions and planning considerations for several typicalLAN-free environments. These environments are:

1. SCSI and 349X Tape Library sharing using the TSM Library Manager and Client. See“Sharing Tape Storage using TSM Library Manager/Client”.

2. File device sharing using SANergy. See “Sharing Disk Storage using Tivoli SANergy” onpage 4.

3. Sharing a library managed by ACSLS or LibraryStation software. See “External Library— Sharing ACSLS-Managed Libraries” on page 5.

Sharing Tape Storage using TSM Library Manager/ClientWhen TSM servers share a SCSI tape or 349X storage device using a library manager andlibrary clients, one server, the library manager, owns and controls the tape library device.The library manager operations include checking volumes into and out of the library,labeling volumes, mounting and dismounting volumes, auditing volumes, and creating aninventory of library contents, see Figure 2 on page 4. The library manager also manages thestorage hierarchy and performs such server functions as storage pool migrations,reclamation, collocation, and backup and restore of storage pools and the database. All of theother TSM servers sharing this library are considered. library clients. A library clientrequests shared library resources as drives or media from the TSM server acting as thelibrary manager, but uses the resources independently. The library manager coordinates theaccess to these resources. Data moves over the SAN between the storage device and eitherthe library manager or the library client. Either the library manager or any library client canmanage the LAN-free movement of client data as long as the client system includes astorage agent.

2


|

|

|||

|

|

|

||

|

|||||

||

||

||

|

||||||||||||||

2.P

lann

ing

The Library Manager and Library Client configurations are represented in Figure 2 .

Note: An environment can consist of just the Library Manager.

The configurations represented in the previous illustration are the following:

¶ A TSM server library manager manages a client’s data, which is stored on a tapelibrary.

¶ A TSM server library client manages a client’s data, which is stored on a tape library.

Sharing Disk Storage using Tivoli SANergyWhen TSM servers share access to disk storage, the environment contains a FILE library(TSM server File device class) and utilizes the SANergy product. SANergy provides a filesharing accelerator. If you will be using a FILE library, you must determine where the TivoliSANergy client and the Tivoli SANergy Metadata Controller (MDC) will be installed. Youwill also require a Windows® share (CIFS) or a Network File Share (NFS) on a Unix systemto achieve file sharing. See Figure 3 on page 5 and Table 1 on page 5 for the possible TivoliSANergy configurations. See the SANergy publications for additional information aboutconfiguring SANergy.

TSM ServerLibrary Manager

TSM ServerLibrary Client

TSM ClientStorage Agents

Tape Library

LAN

SAN

Figure 2. Library Manager/Client LAN—free Configuration


|

|||

||

|

|

||

|

|

|||||||||

In the following table, the numbers refer to those numbers in Figure 3. For example, onepossible configuration is for the Tivoli SANergy client to be installed on the TSM clientmachine (�1�) and the Tivoli SANergy MDC to be installed on the TSM server (�2�). Theseconfigurations can also consist of multiple platforms. For example, an environment canconsist of a SUN MDC working with a NT and AIX client.

Table 1. Tivoli SANergy ConfigurationsTivoli SANergyComponent

Where Installed

Tivoli SANergy Client �1� �2� �1� and �2�

Tivoli SANergy MDC �2� �1� �3�

External Library — Sharing ACSLS-Managed LibrariesWhen TSM servers share access to ACSLS-managed libraries, the sharing is enabled bymiddleware (such as, Gresham EDT-DistribuTAPE) between the data storage manager(TSM) and a media manager (StorageTek ACSLS). See Figure 4 on page 6. The ACSLSServer (or Library Station) manages the physical aspects of tape cartridge storage andretrieval. The external library manager, in this discussion Gresham EDT, communicates withthe ACSLS Server or LibraryStation to access tape cartridges in an automated StorageTeklibrary. The storage agent installed on a machine containing Gresham EDT and a TSM client(such as, Tivoli Data Protection (TDP) for Exchange or TDP for SQL) provides access toSAN-attached storage devices resulting in LAN-free data movement. The continuedconnection to the LAN provides a meta data (control information) path. If the storage agentis not available, the LAN provides a failover path for data backup and recovery.

TSM ClientStorage Agent

TSM Server

Another Node

LAN

SAN

FILE Library

1

2

3

Figure 3. Tivoli SANergy Configurations


|

||||||||

||

|||

||||

|||||

|

||||||||||||

2.P

lann

ing

For detailed installation, configuration, and system administration of ACSLS, refer to theappropriate StorageTek documentation. For detailed installation, configuration, datamigration, and system administration of Gresham EDT-DistribuTAPE, refer to the GreshamEDT User’s Manual.

Figure 4. External Library Environment


|

||

Data Migration and CoexistenceIf you currently have data associated with the TSM ACSLS library type and want to takeadvantage of LAN-free, you will need to consider coexistence and migration issues, see“Legacy ACSLS Data Migration and Coexistence” on page 35.

System RequirementsTo use the Managed System for SAN feature configure the following components at thelatest available software levels. Seehttp://www.tivoli.com/support/storage_mgr/tivolimain.html

¶ Your SAN configuration must meet the applicable hardware and software requirements(see http://www.tivoli.com/support/storage_mgr/san/overview.html).

¶ TCP/IP is required for communication among the TSM server, the client, and the storageagent.

¶ A Tivoli Storage Manager server with this feature (version 4.2.1 or higher). The TSMservers available for the Windows, AIX®, and Sun Solaris operating systems support theManaged System for SAN feature.

¶ A Tivoli Storage Management client (for example, Tivoli Data Protection applicationclient). Client software must be installed on a client system (checkhttp://www.tivoli.com/support/storage_mgr/tivolimain.html for the clients that arecurrently supporting the Managed System for SAN feature).

Note: An API version 4.2 or higher is required.

¶ A Tivoli Storage Manager storage agent. The storage agent must be installed on thesame system as the client software. Also, the storage agent must be at the same level asthe server with which it communicates (including program temporary fix (PTF) level).You can download the latest PTF from the Tivoli Web site athttp://www.tivoli.com/support/storage_mgr/tivolimain.html.

¶ The TSM application program interface (API) software must be at the version 4.2 orhigher level. You can obtain the API by downloading the latest version of thebackup-archive client for AIX from the Web site.

¶ If you are sharing disk storage, Tivoli SANergy Version 2.2 or higher must be installed.

Note: If you are sharing only tape devices, Tivoli SANergy is not required.

¶ If you are using External library support in conjunction with the Gresham product,Gresham EDT DistribuTAPE 6.2.2.0 or higher must be installed. For additionalinformation and product download, seehttp:www.greshamstorage.com/products/download/distributape.html.


||||

2.P

lann

ing


http://www.tivoli.com/support/storage_mgr/san/overview.html



http://www.greshamstorage.com/products/download/distributape.html

Installation and Configuration

The set up procedures are different for disk devices, tape devices and External Library(ACSLS) devices. There are two procedure descriptions in this section. The type ofenvironment you implement determines which procedure you should follow. The types ofenvironments described are:

1. SCSI and 349X Tape Library sharing using the TSM Library Manager and Client.

2. File device sharing using SANergy.

3. External Library support for ACSLS Libraries.

For descriptions of these environments, see “Storage Agent Overview” on page 1 and “Typesof Configurations” on page 3.

The first procedure covers environments that are using either Library Manager/Client orSANergy, see “Procedure 1–Tape and File Sharing with SCSI and 349X Tape and FileDevices” on page 11. The second procedure specifically describes External Library supportfor ACSLS library environment configuration, see “Procedure 2 —External LibraryEnvironment with an ACSLS-Managed Library” on page 20.

Read the summary and continue by performing the tasks in the appropriate procedure usingthe details that follow.

Summary of Tasks for Procedure 1You must complete the following tasks:

1. Network: Ensure that your system meets the prerequisites for the SAN configuration.See “Step 1. Network” on page 11.

Note: If you will be using Tivoli Storage Agent with disk media, you must haveinstalled Tivoli SANergy Version 2.2 on the applicable machines. See Figure 3 onpage 5 for possible Tivoli SANergy configurations. See the Tivoli SANergyAdministrator’s Guide for details.

Establishing communications among client, storage agent, and server

2. Client system:

a. Install the client and the latest level of the TSM API. Specify the LAN-free optionfor the API. See “Install or Upgrade the Client and API Software” on page 12.

b. Install and set up the storage agent. See “Install and Configure the Storage Agent” onpage 14.

3. Server:

3


|

||

3.In

stallation

and

Co

nfig

uratio

n

a. Configure the library and drives on the SAN

b. Define the storage agent as a server

Tape Devices

a. Configure the library and drives on the SAN


Disk Devices

a. Define the FILE device class


See “Step 3. Server” on page 16.

Configuring devices for the storage agent to access

4. Client system: For the tape devices to be used:

a. Obtain device information

See “Step 4. Client System” on page 18.

5. Server:

Set up drive mapping for the storage agents on the server. See “Step 5. Server” onpage 18.

6. Client system:

a. Start the storage agent.

b. Verify the configuration.


Summary of Tasks for Procedure 2You must complete the following tasks:

1. Network: Ensure that your system meets the prerequisites for the SAN configuration.See “Step 1. Network” on page 20.

Note: If you will be using Tivoli Storage Agent with ACSLS-managed libraries, youmust have the ACSLS software and the third-party external library software (suchas, Gresham EDT-DistribuTAPE) installed and configured. See Figure 4 on page 6for an example of a Storage Agent in an ACSLS-managed library environment.See the StorageTek ACSLS and the Gresham EDT documentation for installationinstructions.

Establishing communications among client, storage agent, and server

2. Client system:

a. Install the client and the latest level of the TSM API. Specify the LAN-free optionfor the API. See “Install or Upgrade the Client and API Software” on page 22.

b. Install and set up the storage agent. See “Install and Configure the Storage Agent” onpage 23.


|

|

||

||||||

|

|

||

||

3. Server:

a. Configure the library on the SAN


Tape Devices

a. Configure the library on the SAN


See “Step 3. Server” on page 16.

4. Client system:

a. Start the storage agent.

b. Verify the configuration.


Procedure 1–Tape and File Sharing with SCSI and 349X Tape andFile Devices

The following steps describe configuring a storage agent environment consisting of eithershared libraries or shared disk, or both. If you are configuring an external library, that is, anACSLS-managed library environment, see “Procedure 2 —External Library Environmentwith an ACSLS-Managed Library” on page 20.

Step 1. NetworkThe server system and the client systems must be attached to the SAN along withappropriate storage devices. The server system and the client systems must also beconnected by means of a LAN.

The Managed System for SAN feature requires specific levels and models of hardware andsoftware. Ensure that your system configuration meets the hardware and softwarerequirements for the SAN setup. See the Web site,http://www.tivoli.com/support/storage_mgr/san/overview.html, for details.

Establishing communications among client, storage agent, andserver

Figure 5 on page 12 shows the results of completing “Step 2. Client System” on page 12 and“Step 3. Server” on page 16.

Note: This figure does not include all the required options. Steps 2 and 3 provide moredetails.


|

|

|

|

|

|

|

|

|

|

|

|

|

|

||||

3.In

stallation

and

Co

nfig

uratio

n


Step 2. Client SystemDo the following on the client system:

1. Install or upgrade to the latest level of the client software and the TSM API software.

2. Install the storage agent software.

Install or Upgrade the Client and API Software1. Check that the client system meets the prerequisites for client software. See the

applicable documentation. Install the client software if it is not already installed on thesystem, or upgrade the software to the latest level as necessary. You can ensure this bychecking http://www.tivoli.com/support/storage_mgr/tivolimain.html. If there is a morerecent package, you will want to download and install. See step 3 on page 13 for theinstall instructions.

2. Modify the TSM options file (dsm.sys).

For information about the dsm.opt and dsm.sys files, see Tivoli Storage ManagerInstalling the Clients.

a. Edit the dsm.sys file to specify the communications method between the TSM clientand server. You should see the following:

TSM Client Workstation

Client - MANTIA

Storage Agent - IRIS

TSM Server - GARDEN

dsm.sys file

dsmsta.opt file

servername=

devconfig

garden

devconfig

enablelanfree yes

tcpserveraddress .tucson.tivoli.comgarden

define server serverpassword=jonquil

hladdress=sanclient.tucson.tivoli.com

lladdress=1500

register node crocus domain=sandomain

iris

mantia

devconfig file

set staname iris

set stapassword xxxxxxx

set stahladdress arbor.tucson.tivoli.com

define server serverpassword=xxxxxxxx

hladdress=garden.tucson.tivoli.com

lladdress=1500

garden

Figure 5. Communications information. Results of Steps 2 and 3. The passwords are shown as ″xxxxxxx″ becausethey are encrypted in the file.



commmethod tcpiptcpserveraddress garden.tucson.tivoli.comtcpport 1501

andcommmethod sharedmemshmport 1511

b. If you specified the TCP/IP communication method, edit the dsm.opt file to name theserver specified in the communication method. For example,servername garden

c. Specify that you want the client to use SAN-attached devices during backup, restore,archive, and retrieve processing, if the path to the SAN devices is available. Activatethe following options in the dsm.sys file:enablelanfree yes

LANFREECommethod TCPIPLANFREETCPPort 1501

andLANFREECommethod SharedMemLANFREESHMPORT 1511

3. Update the API software to the latest level by following the procedure described belowor install the latest client.

Note: Ensure that the client is already installed.

a. Create the Tivoli Storage Manager API option files

1) Copy APIINSTALLPATH/dsm.sys.smp to dsm.sys if your system has not been setup to use Tivoli Storage Manager.

2) Edit the dsm.sys file to include the Tivoli Storage Manager server to which youwant to connect. For example:SErvername server_aCOMMmethod TCPipTCPPort 1500TCPServeraddress server_a.domain.company.COM

It is assumed that the dsm.sys file is controlled by the system administrator. TheTivoli Storage Manager server administrator should supply the name and IPaddress of the Tivoli Storage Manager server, as well as the node name andpassword.

b. Set up the environment variables. The BASE API uses unique environment variablesto locate files.

¶ DSMI_CONFIG is the fully qualified name for the client user option file.

¶ DSMI_DIR points to the path containing dsm.sys, dsmtca, and the subdirectoryen_US.

¶ en_US subdirectory must contain dsmclientV3.cat.

¶ DSMI_LOG points to the path for the dsierror.log file

The following are examples on how to set up these environment variables.


3.In

stallation

and

Co

nfig

uratio

n

export DSMI_CONFIG=APIINSTALLPATH/dsm.optexport DSMI_DIR=APIINSTALLPATHexport DSMI_LOG=/home/user_a/logdir

Note: The quickest way to set these is to add these variables to the user’s .profilefile.

c. Using shared memory.

The Tivoli Storage Manager API client user must be logged in as root or have thesame user ID as the process running the Tivoli Storage Manager server.

Install and Configure the Storage Agent

Note: It is recommended that the Storage Agent not be installed on the same machine as theTivoli Storage Manager Server.

On the same system as the client, install the storage agent. The default installation directoryis /usr/tivoli/tsm/StorageAgent/bin.

The instructions in this section are shown using the Software Management and InstallationTool (SMIT). You can also use the Install and Update Software Manager (installm).

Note: Throughout this procedure, /dev/cd0 is used for CD-ROM. This may be different inyour environment. Loading the server files can take several minutes.

Here is the SMIT procedure:

1. Gather the following information:

¶ Storage agent: Name and password for the storage agent. The name and passwordmust be the same as the name and password that is used to define the storage agentas a server to the TSM server. For example:

v Name: IRIS

v Password: jonquil

v TCP/IP address: arbor.tucson.tivoli.com

¶ TSM server: Information about the TSM server with which the storage agent willcommunicate. This is the same TSM server with which the client communicates.For example:

v Name: GARDEN

v Password: botanical

v TCP/IP address: garden.tucson.tivoli.com

v TCP/IP port: 1500

2. Log in as the root user.

3. Load the Storage Agent CD-ROM into the selected drive.

4. From your desktop window, access SMIT and make selections according to the level ofyour AIX operating system.

Enter:

smit install_update &


||

|

For AIX 4.3, select:

Install and Update SoftwareInstall and Update from the LATEST Available Software


Install SoftwareInstall Software

5. On the next window, select the device that you are using for the installation. You canenter the drive name in the window or click on List to access the device list.

If you click on List, select the CD-ROM drive that you are using for the installation(for example, /dev/cd0).

6. Click on OK.

7. Locate the line Software to Install.

a. To install all components listed in the table at step 8, continue at step 10.

b. To selectively install components, click on List for the latest available softwarepackages and continue at step 8.

8. Select the component that you require. The following table lists the component filesetfile names.

Table 2. Package and Fileset Names for Installation. AIX 4.3.3 PlatformsPackage Name Fileset Names Description

tivoli.tsm.StorageAgent.rte tivoli.tsm.StorageAgent.rte StorageAgent common functions,examples

tivoli.tsm.devices.aix43.rte tivoli.tsm.devices.aix43.rte SCSI runtime device support

tivoli.tsm.msg.en_US.devices tivoli.tsm.msg.en_US.devices SMIT screens

tivoli.tsm.msg.en_US.server tivoli.tsm.msg.en_US.server Message catalog and Online help

Table 3. Package and Fileset Names for Installation. AIX 5.1 PlatformsPackage Name Fileset Names Description


tivoli.tsm.devices.aix5.rte64 tivoli.tsm.devices.aix5.rte64 SCSI runtime device support



9. Click OK.

10. Check the default settings for the options on this window.

11. Click OK.

SMIT responds:

ARE YOU SURE?...

12. Click OK.

This installation may take several minutes.

13. Click Done after the installation is complete, remove the CD, and exit from SMIT.


3.In

stallation

and

Co

nfig

uratio

n

14. Ensure that a device configuration file exists and that the matching DEVCONFIGoption is in the dsmsta.opt file. For example, for a device configuration file nameddevconfig located at /usr/tivoli/tsm/StorageAgent/bin, edit the dsmsta.opt file and enterthe following line:DEVCONFIG devconfig

15. Use the information that you collected in step 1 on page 14 to issue the DSMSTASETSTORAGESERVER command. For example:dsmsta setstorageserver myname=iris mypassword=jonquilmyhladdress=arbor.tucson.tivoli.comservername=garden serverpassword=botanicalhladdress=garden.tucson.tivoli.com lladdress=1500

See “Set Installation Data for the Storage Agent: DSMSTA SETSTORAGESERVER”on page 30 for the details on the command parameters.

The command generates the following lines in the device configuration file for thestorage agent:

set staname irisSET STAPASSWORD xxxxxxxSET STAHLADDRESS arbor.tucson.tivoli.comDEFINE SERVER garden serverpassword=xxxxxxxxxxxHLADDRESS=garden.tucson.tivoli.com LLADDRESS=1500

The passwords (shown here as xxxxxxxx) are encrypted in the file.

The command also generates the following line in the dsmsta.opt file:

SERVERNAME garden

See “The Storage Agent Options File” on page 32 and “The Device Configuration Filefor the Storage Agent” on page 32 for details on these files.

Step 3. Server

Note: The TSM server console (Microsoft Management Console, MMC) provides a snapinthat contains a storage agent configuration wizard. This wizard performs all of themanual steps listed here and allows you to skip to step 4. For additional information,see the TSM server console online help.

The following is an overview of the steps that you need to do on the TSM server. Fordetails, see Administrator’s Guide. On the server, do the following:

1. Configure the SAN drives. This involves the following steps:

Tape Device

a. Define a shared SCSI or 3494 library

b. Define drives that are associated with the library

c. Define the device class

d. Define the storage pool

Disk Device


Configure Enterprise Management and define a device class of DEVTYPE=FILE andSHARED=YES. TSM automatically defines a new FILE library and also defines drivescorresponding to the mount limit for the FILE device class. The FILE library name is thesame as the device class name. Each drive uses the library name with a numeric suffix.If the mount limit is changed, the number of drives also changes.

Note: The mount limit should correspond to the number of concurrent backups youexpect, as each session gets exclusive access to a file volume.

2. For each client for which you want to enable SAN data transfer, define the client’sstorage agent as if it was a server. You must use the same name and password that youset for the storage agent when you installed it on the client system. The DEFINESERVER command must be issued from the server (library manager or library client)that will manage the client’s data. For example:define server iris serverpassword=jonquilhladdress=sanclient.tucson.tivoli.com lladdress=1500

3. Modify policy for the client so that the storage agent acting on behalf of the client usesthe drives on the SAN. The client must use a management class that has copy groupswith a destination storage pool. The destination storage pool must be associated with thelibrary on the SAN for which you have mapped drives for the client. See Administrator’sGuide for details on changing policy for clients that can use SAN drives. For example,do the following:

a. Create a policy domain for clients that will use the SAN devices for direct datatransfer.

b. Create a policy set in that domain.

c. In the default management class for that policy set, modify the copy groups. Set thedestination storage pool to the storage pool associated with the SAN drives that youconfigured and mapped for the client.

Note: If you decide not to use the default management class for the SAN drives, youwill need to create a new management class. Clients that want to use the SANdrives need to update the include-exclude list to specify the new managementclass. See Tivoli Storage Manager Installing the Clients for details on theinclude-exclude list.

d. Activate the policy set.

e. Register or update the client nodes so that they are in the new policy domain.

See Administrator’s Reference for details on the commands.

To review the expected results of the steps that you have just completed, see Figure 5 onpage 12.

Configuring Devices for the Storage Agent to AccessFigure 6 on page 18 shows the results of completing “Step 4. Client System” on page 18 and“Step 5. Server” on page 18.


3.In

stallation

and

Co

nfig

uratio

n

Step 4. Client System

Note: If you are configuring a FILE Library, go to Step 5.

Perform the following:

Obtain Tape Device InformationDo the following for tape devices:

Use SMIT and issue the following commands to obtain information about devices.

¶ For IBM® devices:Select Devices -> Tape Drive -> List All Defined Tape Drives

¶ For other devices:Devices -> Tivoli Storage Manager -> Optical R/W Disk Drive or Tape Drive or

Library/Medium Changer -> List All Defined devices

Step 5. ServerThe following provides information to help you define drive mappings on the TSM server.Drive mapping allows a client, by means of a storage agent, access to drives in a library.The requirements are different depending on the device you are using.

Consider the following guidelines before you begin mapping your SAN drives:

¶ Map all drives. Problems can occur if you do not define drive mappings on the serverfor each drive in a library. For example, during backup operations, all drives that havebeen mapped can be used by storage agents backing up data. Backup operations will failif you try to use other drives in a library that have not been mapped.

When drive mappings are defined for each drive in a library, backup operations waituntil the next drive is available for the transfer of data.

Note: Backup operations can fail if no mount points are found to satisfy the request. Ifthis occurs it is likely that all available drives have not been mapped to the client.


SAN

TSM Server - GARDEN

Storage Agent

device name: /dev/rmt/3mt

Tape Library Drive

define drive sanlib1 drivea device=/dev/6mt

define drivemapping iris sanlib1 drivea device=/dev/rmt/3mt

Figure 6. Device information. Results of Steps 4 and 5.


|

¶ Limit the number of drives. Use the MAXNUMMP parameter on the REGISTER NODEor UPDATE NODE command to limit the number of drives that are available for thestorage agent to use on behalf of the client.

¶ Review tape device names. For the same tape device, the device name as known to theserver will probably not match the device name as known to the storage agent.

Tape DevicesMap the drives on the server using the device names as seen by the storage agent on eachclient system. See “Obtain Tape Device Information” on page 18.

Note: The DEFINE DRIVEMAPPING command must be issued from the server (librarymanager or library client) that will manage the client’s data.

For example, you would issue the following:define drivemapping iris sangroup drivea device=/dev/rmt3define drivemapping iris sangroup driveb device=/dev/rmt4

See the Administrator’s Reference for your system platform for additional details on thecommands.

For a review of the results of the steps that you have just completed, see Figure 6 onpage 18.

Disk DevicesMap the drives on the server using the device names as seen by the storage agent on eachclient system. For example, on the server side, the directory, d:\tsmdata\server1, is exportedon the NFS server running on the TSM Server machine. On the storage agent, the directoryis NFS mounted as /tsmdata/server1. Because the two directory names do not match, a drivemapping needs to be created for each file drive in the library. Below is the command toissue to create the mapping for this scenario.define drivemapping sa1 file1 file11 device=file online=yes dir="/tsmdata/server1"

See the Administrator’s Reference for your system platform and additional details on thecommands.

Step 6. Client SystemDo the following:

1. “Start the Storage Agent”

2. “Verify the Configuration” on page 20

Start the Storage AgentStart the storage agent by changing to the storage agent directory and issue the followingcommand:dsmsta

When the storage agent starts, it determines if the TSM server is a library client or librarymanager. If the TSM server is a library client, the storage agent uses information about thelibrary manager from the library client in order to cross define itself to the library manager.


3.In

stallation

and

Co

nfig

uratio

n

Verify the ConfigurationTo verify that you have configured your system correctly for LAN-free data movement,perform the following procedure:

1. Run a backup operation from the client. If you receive a message saying that the backuphas been successful, you have configured your system correctly.

2. Ensure the following if you receive a message saying that the backup has failed.

Note: If you retry the backup operation after the first failure, the client attempts to usethe LAN connection for data movement. The client will continue to use the LANuntil the client is stopped and restarted.

a. The TSM server is running. If the TSM server is not running, the storage agent willnot start.

b. The client, storage agent, and server are communicating with each other as expected.

c. The drive mapping is correctly defined.

d. All drives in a library have been mapped on the server.

Determining Whether the Data Movement was LAN-freeUse the following guidelines to help determine whether the data movement is using theLAN-free environment:

¶ Issue either of the following QUERY ACTLOG commands on the server to which theclient is connected:query actlog search=storage_agent_name msgno=8337

orquery actlog search=storage_agent_name

Note: If the query finds entries in the activity log that relates to the storage agent, theclient is using LAN-free data transfer.

¶ Review the amount of data being transmitted from the client to the server. The amountof data being transferred to the server should be considerably less than the amount ofdata being backed up. This is because the actual backup data is passed over the SAN.From the command, issue:netstat -D

Procedure 2 —External Library Environment with anACSLS-Managed Library

If you will be using a Tivoli Storage Agent with ACSLS-managed libraries, you must havethe ACSLS software and the third-party external library software (such as, GreshamEDT-DistribuTAPE) installed and configured. See Figure 4 on page 6 for an example of aStorage Agent in an ACSLS-managed library environment. See the StorageTek ACSLS andthe Gresham EDT documentation for installation instructions.

Step 1. NetworkThe server system and the client systems must be attached to the SAN along withappropriate storage devices. The server system and the client systems must also beconnected by means of a LAN.


|

|

|||||

|

|||

The Managed System for SAN feature requires specific levels and models of hardware andsoftware. Ensure that your system configuration meets the hardware and softwarerequirements for the SAN setup. See the Web site,http://www.tivoli.com/support/storage_mgr/san/overview.html, for details.

Establishing communications among client, storage agent, and serverFigure 7 shows the results of completing “Step 2. Client System” and “Step 3. Server” onpage 26.

Note: This figure does not include all the required options. Steps 2 and 3 provide moredetails.

Step 2. Client SystemDo the following on the client system:

1. Install or upgrade to the latest level of the client software and the TSM API software(version 4.2 or higher).

2. Install the storage agent software.

3. Install Gresham EDT or any other third-party software that provides external libraryenablement. For installation information, see the Gresham documentation.


Client - MANTIA

Storage Agent - IRIS

TSM Server - GARDEN

dsm.sys file

dsmsta.opt file

servername=

devconfig

garden

devconfig

enablelanfree yes

tcpserveraddress .tucson.tivoli.comgarden

define server serverpassword=jonquil

hladdress=sanclient.tucson.tivoli.com

lladdress=1500

register node crocus domain=sandomain

iris

mantia

devconfig file

set staname iris

set stapassword xxxxxxx

set stahladdress arbor.tucson.tivoli.com

define server serverpassword=xxxxxxxx

hladdress=garden.tucson.tivoli.com

lladdress=1500

garden

Figure 7. Communications information. Results of Steps 2 and 3. The passwords are shown as ″xxxxxxx″ becausethey are encrypted in the file.


|

||||

||||

|

||

|||

|

||

||

|

||

3.In

stallation

and

Co

nfig

uratio

n


Install or Upgrade the Client and API Software

1. Check that the client system meets the prerequisites for client software. See the applicabledocumentation. Install the client software if it is not already installed on the system, orupgrade the software to the latest level as necessary. You can ensure this by checkinghttp://www.tivoli.com/support/storage_mgr/tivolimain.html. If there is a more recent package,you will want to download and install. See 3 for the install instructions.

2. Modify the TSM client options file (dsm.sys).

For information about the dsm.opt and dsm.sys files, see Tivoli Storage Manager Installingthe Clients.

a. Edit the dsm.sys file to specify the communications method between the TSM client andserver. You should see the following:commmethod tcpiptcpserveraddress garden.tucson.tivoli.comtcpport 1501

andcommmethod sharedmemshmport 1511

b. If you specified the TCP/IP communication method, edit the dsm.opt file to name theserver specified in the communication method. For example,servername garden

c. Specify that you want the client to use SAN-attached devices during backup, restore,archive, and retrieve processing, if the path to the SAN devices is available. Activate thefollowing option in the dsm.sys file:enablelanfree yes

LANFREECommethod TCPIPLANFREETCPPORT 1501

andLANFREECommethod SharedMemLANFREESHMPORT 1511

3. Update the API software to the latest level by following the procedure described below orinstall the latest client.

Note: Ensure that the client is already installed.

a. Create the Tivoli Storage Manager API option files

1) Copy APIINSTALLPATH/dsm.sys.smp to dsm.sys if your system has not been set upto use Tivoli Storage Manager.

2) Edit the dsm.sys file to include the Tivoli Storage Manager server to which you wantto connect. For example:SErvername server_aCOMMmethod TCPipTCPPort 1500TCPServeraddress server_a.domain.company.COM

It is assumed that the dsm.sys file is controlled by the system administrator. TheTivoli Storage Manager server administrator should supply the name and IP addressof the Tivoli Storage Manager server, as well as the node name and password.


|

|||||

|

||

||

|||

|

||

||

|

|||

||||

|

||

||

|

|

||

||

||||

|||


b. Set up the environment variables. The BASE API uses unique environment variables tolocate files.

¶ DSMI_CONFIG is the fully qualified name for the client user option file.

¶ DSMI_DIR points to the path containing dsm.sys, dsmtca, and the subdirectoryen_US.

¶ en_US subdirectory must contain dsmclientV3.cat.

¶ DSMI_LOG points to the path for the dsierror.log file

The following are examples on how to set up these environment variables.export DSMI_CONFIG=APIINSTALLPATH/dsm.optexport DSMI_DIR=APIINSTALLPATHexport DSMI_LOG=/home/user_a/logdir

Note: The quickest way to set these is to add these variables to the user’s .profile file.

c. Using shared memory.

The Tivoli Storage Manager API client user must be logged in as root or have the sameuser ID as the process running the Tivoli Storage Manager server.

Install and Configure the Storage Agent

Note: It is recommended that the Storage Agent not be installed on the same machine as theTivoli Storage Manager Server.

On the same system as the client, install the storage agent. The default installation directoryis /usr/tivoli/tsm/StorageAgent/bin.

The instructions in this section are shown using the Software Management and InstallationTool (SMIT). You can also use the Install and Update Software Manager (installm).

Note: Throughout this procedure, /dev/cd0 is used for CD-ROM. This may be different inyour environment. Loading the server files can take several minutes.

Here is the SMIT procedure:

1. Gather the following information:

¶ Storage agent: Name and password for the storage agent. The name and passwordmust be the same as the name and password that is used to define the storage agentas a server to the TSM server. For example:

v Storage Agent Name: IRIS

v Storage Agent Password: jonquil

v Storage Agent TCP/IP address: arbor.tucson.tivoli.com

¶ TSM server: Information about the TSM server with which the storage agent willcommunicate. This is the same TSM server with which the client communicates.For example:

v TSM Server Name: GARDEN

v TSM Password: botanical

v TSM TCP/IP address: garden.tucson.tivoli.com


||

|

||

|

|

|

|||

|

|

||

|

||

||

||

||

|

|

|||

|

|

|

|||

|

|

|

3.In

stallation

and

Co

nfig

uratio

n

v TSM TCP/IP port: 1500

v Tape Library Name: stk-lib

2. Log in as the root user.

3. Load the Storage Agent CD-ROM into the selected drive.

4. From your desktop window, access SMIT and make selections according to the level ofyour AIX operating system.

Enter:

smit install_update &


Install and Update SoftwareInstall and Update from the LATEST Available Software


Install SoftwareInstall Software

5. On the next window, select the device that you are using for the installation. You canenter the drive name in the window or click on List to access the device list.

If you click on List, select the CD-ROM drive that you are using for the installation(for example, /dev/cd0).

6. Click on OK.

7. Locate the line Software to Install.

a. To install all components listed in the table at step 8, continue at step 10 on page 25.

b. To selectively install components, click on List for the latest available softwarepackages and continue at step 8.

8. Select the component that you require. The following table lists the component filesetfile names.

Table 4. Package and Fileset Names for Installation. AIX 4.3.3 PlatformsPackage Name Fileset Names Description


tivoli.tsm.devices.aix43.rte tivoli.tsm.devices.aix43.rte SCSI runtime device support



Table 5. Package and Fileset Names for Installation. AIX 5.1 PlatformsPackage Name Fileset Names Description


tivoli.tsm.devices.aix5.rte64 tivoli.tsm.devices.aix5.rte64 SCSI runtime device support




|

|

|

|

||

|

|||

|

||||

|

||||

||

||

|

|

|

||

||

|||||||||||||||||||

|||||||||||||||||||

9. Click OK.

10. Check the default settings for the options on this window.

11. Click OK.

SMIT responds:

ARE YOU SURE?...

12. Click OK.

This installation may take several minutes.

13. Click Done after the installation is complete, remove the CD, and exit from SMIT.

14. Use the information that you collected in step 1 on page 23 to issue the DSMSTASETSTORAGESERVER command. For example:dsmsta setstorageserver myname=iris mypassword=jonquilmyhladdress=arbor.tucson.tivoli.comservername=garden serverpassword=botanicalhladdress=garden.tucson.tivoli.com lladdress=1500

See “Set Installation Data for the Storage Agent: DSMSTA SETSTORAGESERVER”on page 30 for the details on the command parameters.

The command generates the following lines in the device configuration file for thestorage agent:

SET STANAME irisSET STAPASSWORD xxxxxxxSET STAHLADDRESS arbor.tucson.tivoli.comDEFINE SERVER garden serverpassword=botanicalHLADDRESS=garden.tucson.tivoli.com LLADDRESS=1500


The command also generates the following line in the dsmsta.opt file:

SERVERNAME garden

See “The Storage Agent Options File” on page 32 and “The Device Configuration Filefor the Storage Agent” on page 32 for details on these files.

15. Start this step only after the dsmsta command issued in the previous step has completedsuccessfully. Use the library information that you collected in step 1 on page 23 and addlibrary definition information to the device configuration file. For example:

Using the editor of your choice open the device configuration file and add the librarynamed stk-lib, set the libtype to external with lanfree and obeymountretention equallingyes. Gresham EDT-DistribuTape is the external library manager interfacing with theACSLS library software, the EDT executable is located in its default path/usr/lpp/dtelm/bin/elm. With the device configuration file open you would add thefollowing entry to the bottom of the file:

DEFINE LIBRARY stk-lib libtype=external lanfree=yes obeymountretention=yesEXTERNALMANAGER=/usr/lpp/dtelm/bin/elm

The resulting device configuration file would appear as:


|

|

|

|

|||

|

|

|

||

||||

||

||

|||||||

|

|

|||

||

|||

||||||

||||

|

3.In

stallation

and

Co

nfig

uratio

n

SET STANAME irisSET STAPASSWORD xxxxxxxSET STAHLADDRESS arbor.tucson.tivoli.comDEFINE SERVER garden serverpassword=xxxxxxxxxxxHLADDRESS=garden.tucson.tivoli.com LLADDRESS=1500DEFINE LIBRARY eagle-lib libtype=external lanfree=yes obeymountretention=yesEXTERNALMANAGER=/usr/lpp/dtelm/bin/elm

Save and close the file.

Step 3. ServerThe following is an overview of the steps that you need to do on the TSM server. Fordetails, see Administrator’s Guide. On the server, do the following:

1. Install Gresham EDT or any other third-party software that provides external libraryenablement. For installation information, see the Gresham documentation.

2. Configure the SAN drives. This involves the following steps:

Tape Device

a. Define a library type of EXTERNAL. For example:define library stk-lib libtype=external lanfree=yes obeymountretention=yesexternalmanager=/usr/lpp/dtelm/bin/elm

In the previous example the path provided for the external manager is dependentupon the operating system where the TSM server resides. For example, an AIX TSMserver external manager path is /usr/lpp/dtelm/bin/elm in contrast to a TSM Sunserver external manager path of /opt/OMIdtelm/bin/elm or a TSM Windows serverexternal manager path of c:\program files\GES\EDT\bin\elm.exe. For additionalinformation about the DEFINE LIBRARY command, see the Tivoli Storage ManagerAdministrator’s Reference.

b. Define a device class with a device type of ECARTRIDGE

c. Define the storage pool

3. For each client for which you want to enable SAN data transfer, define the client’sstorage agent as if it was a server. You must use the same name and password that youset for the storage agent when you installed it on the client system. The DEFINESERVER command must be issued from the server (library manager or library client)that will manage the client’s data. For example:define server iris serverpassword=jonquilhladdress=sanclient.tucson.tivoli.com lladdress=1500

4. Modify policy for the client so that the storage agent acting on behalf of the client usesthe drives on the SAN. The client must use a management class that has copy groupswith a destination storage pool. The destination storage pool must be associated with thelibrary on the SAN for which you have mapped drives for the client. See Administrator’sGuide for details on changing policy for clients that can use SAN drives. For example,do the following:

a. Create a policy domain for clients that will use the SAN devices for direct datatransfer.

b. Create a policy set in that domain.


|||||||||

|

|||

||

|

|

|

||

|||||||

|

|

|||||

||

||||||

||

|

c. In the default management class for that policy set, modify the copy groups. Set thedestination storage pool to the storage pool associated with the SAN drives that youconfigured and mapped for the client.

Note: If you decide not to use the default management class for the External Library,you will need to create a new management class. Clients that want to use theSAN attached library need to update the include-exclude list to specify thenew management class. See Tivoli Storage Manager Installing the Clients fordetails on the include-exclude list.

d. Activate the policy set.

e. Register or update the client nodes so that they are in the new policy domain.

See Administrator’s Reference for details on the commands.

To review the expected results of the steps that you have just completed, see Figure 5 onpage 12.

Configuring Devices for the Storage Agent to AccessIn step 4 you will enable and start the device driver in order to support the tape device. Incontrast to other configurations documented in this publication External library support doesnot require TSM drive mapping. Instead the Gresham middleware product provides the drivemapping.

Step 4. Client SystemDo the following:

1. “Start the Storage Agent” on page 19

2. “Verify the Configuration” on page 20

Start the Storage AgentStart the storage agent by changing to the storage agent directory and issue the followingcommand:dsmsta

Verify the ConfigurationTo verify that you have configured your system correctly for LAN-free data movement,perform the following procedure:

1. Run a backup operation from the client. If you receive a message saying that the backuphas been successful, you have configured your system correctly.

2. Ensure the following if you receive a message saying that the backup has failed.

Note: If you retry the backup operation after the first failure, the client attempts to usethe LAN connection for data movement. The client will continue to use the LANuntil the client is stopped and restarted.

a. The TSM server is running. If the TSM server is not running, the storage agent willnot start.

b. The client, storage agent, and server are communicating with each other as expected.

c. The mount and message is displayed on the storage agent console.


|||

|||||

|

|

|

||

|

||||

|

|

|

|

|||

|

|||

||

|

|||

||

|

|

3.In

stallation

and

Co

nfig

uratio

n

Determining Whether the Data Movement was LAN-freeUse the following guidelines to help determine whether the data movement is using theLAN-free environment:

¶ Issue either of the following QUERY ACTLOG commands on the server to which theclient is connected:query actlog search=storage_agent_name msgno=8337

orquery actlog search=storage_agent_name

Note: If the query finds entries in the activity log that relates to the storage agent, theclient is using LAN-free data transfer.

¶ Review the amount of data being transmitted from the client to the server. The amountof data being transferred to the server should be considerably less than the amount ofdata being backed up. This is because the actual backup data is passed over the SAN.From the command, issue:netstat -D


|||

||

|

|

|

||

||||

|

|

Administration and ConfigurationReference

The information in this section provides information about administering, monitoring, tuning,and connecting the storage agent.

Starting and Stopping the Storage AgentStart the storage agent by accessing the storage agent directory and issue the followingcommand:dsmsta

Stop the storage agent by typing the following command at the command line prompt:halt

Obtaining Tape Device Information on the Client SystemTo complete the setup of the storage agent, you must obtain the device names from theclient system. You can get this information by using SMITTY and issuing the followingcommands:

¶ For IBM devices:Select Devices ->

Tape Drive -> List All Defined Tape Drives

¶ For other devices:Devices -> Tivoli Storage Manager -> Optical R/W Disk Drive or Tape Drive or

Library/Medium Changer -> List All Defined devices

A


||

A.

Ad

min

istration

and

Co

nfig

uratio

nR

eference

Set Installation Data for the Storage Agent: DSMSTASETSTORAGESERVER

PurposeUse this utility on the client system where the storage agent has been installed. The utilityadds communication information to the device configuration file and the dsmsta.opt file forthe storage agent. See “Install and Configure the Storage Agent” on page 14 for moreinformation on when to use this command.

This utility does not remove any previous entries in the files. It appends information to theexisting files. The option devconfig, to set a name for the device configuration file, mustexist in the dsmsta.opt file for the command to work. See the example for details on theinformation that the command adds.

Format@@ DSMSTA SETSTORAGESERVER MYName = storage_agent_name @

@ MYPAssword = storage_agent_password @

@ MYHLAddress = storage_agent_hladdress SERVERName = server_name @

@ SERVERPAssword = server_password HLAddress = server_tcpip_address @

@ LLAddress = server_tcpip_port @A

ParametersAll parameters are required.

MYNameSpecifies the name of the storage agent. This name appears in the SET STANAMEcommand that is inserted into the device configuration file.

Note: You must use the same name when you define the storage agent as a server to theTSM server.

MYPAsswordSpecifies the password of the storage agent. This value is encrypted and used in the SETSTAPASSWORD command that is inserted into the device configuration file.

Note: You must use the same password when you define the storage agent as a server tothe TSM server.

MYHLAddressSpecifies the TCP/IP address of the storage agent. This value is used internally in theSET STAHLAddress command which is inserted into the device configuration file.


SERVERNameSpecifies the name of the TSM server. This name appears in the DEFINE SERVERcommand that is inserted into the device configuration file.

SERVERPAsswordSpecifies the password of the server. This value is encrypted and appears in theSERVERPASSWORD field of the DEFINE SERVER command that is inserted into thedevice configuration file.

HLAddressSpecifies the TCP/IP address of the server. This value is used in the HLADDRESS fieldof the DEFINE SERVER command.

LLAddressSpecifies the TCP/IP port on which to access the server. This value is used in theLLADDRESS field of the DEFINE SERVER command.

ExamplesIssue the DSMSTA SETSTORAGESERVER command with the following information:

¶ Storage agent

Name: IRIS

Password: jonquil

TCP/IP address: garden.tucson.tivoli.com

¶ TSM server

Name: GARDEN

Password: botanical

TCP/IP address: arbor.tucson.ibm.com

TCP/IP port: 1500

The command is:dsmsta setstorageserver myname=iris mypassword=jonquilmyhladdress=arbor.tucson.tivoli.comservername=garden serverpassword=botanicalhladdress=garden.tucson.tivoli.com lladdress=1500

The command generates the following lines in the device configuration file for the storageagent:

SET STANAME irisSET STAPASSWORD xxxxxxxSET STAHLADDRESS arbor.tucson.tivoli.comDEFINE SERVER garden serverpassword=xxxxxxxxHLADDRESS=garden.tucson.tivoli.com LLADDRESS=1500


The command also generates the following line in the dsmsta.opt file for the storage agent:

SERVERNAME garden


A.

Ad

min

istration

and

Co

nfig

uratio

nR

eference

The Storage Agent Options FileThe options file for the storage agent is named dsmsta.opt. The dsmsta.opt file for thestorage agent contains the name of the server with which the storage agent communicates,along with other options. The dsmsta.opt file is located where the storage agent program wasinstalled, the default path is: /usr/tivoli/tsm/StorageAgent/bin

Normally you do not need to make any changes to the options file. If your TSM serverchanges, you may need to make changes to this file.

The required options are:

SERVERName server_nameThe name of the TSM server with which the storage agent communicates. TheDSMSTA SETSTORAGESERVER command inserts this option.

DEVCONFig file_nameThe name of the device configuration file for the storage agent. A typical name forthe file is devconfig.

The following options are also available, but not required:

RESOURCETimeout minutesSpecifies the maximum number of minutes that a storage agent waits for a resourceon the server. The default value is 10 minutes. The minimum value is 1 minute. Thisparameter is optional.

STAMaxpooledsessions numberThe number of sessions that the storage agent keeps open to the TSM server. Thedefault value is 25. Possible values are 0 to 150. If the storage agent needs moresessions than specified, additional sessions are considered temporary and close whenthe transaction is complete.

Note: Allowed abbreviations for the options are shown in uppercase letters above.

The Device Configuration File for the Storage AgentThe device configuration file for the storage agent includes information on the storage agentitself and information about the TSM server with which the storage agent communicates.The file is typically named devconfig and is located with the storage agent program asfollows: For AIX, the location is /usr/tivoli/tsm/StorageAgent/bin. The DSMSTASETSTORAGESERVER command normally generates the contents of the file. If you havechanges to the TSM server or if a service representative directs you, you may need to makechanges to the information. You can use the DSMSTA SETSTORAGESERVER command toadd information to the file.

Typical contents of the device configuration file are as follows:

Note: If you are utilizing an ACSLS-managed library environment, see the second deviceconfiguration file example.

SET STANAME irisSET STAPASSWORD xxxxxxxSET STAHLADDRESS arbor.tucson.tivoli.comDEFINE SERVER garden serverpassword=botanicalHLADDRESS=garden.tucson.tivoli.com LLADDRESS=1500


||||

|

||||||||

|

||

|||||||

In this example, IRIS is the name of the storage agent and GARDEN is the name of theTSM server.

Typical contents of the device configuration file for an ACSLS-managed library environmentare as follows:

SET STANAME irisSET STAPASSWORD xxxxxxxSET STAHLADDRESS arbor.tucson.tivoli.comDEFINE SERVER garden serverpassword=botanicalHLADDRESS=garden.tucson.tivoli.com LLADDRESS=1500DEFINE LIBRARY stk-lib libtype=external lanfree=yes obeymountretention=yesEXTERNALMANAGER=/usr/lpp/dtelm/bin/elm

In this example, IRIS is the name of the storage agent, GARDEN is the name of the TSMserver, and STK-LIB is the name of the ACSLS-managed library.

The following describes the contents of the file:

SET STANAMESets the name of the storage agent. The name must be the same as the name thatwas used to define the storage agent as a server to the TSM server.

SET STAPASSWORDSets the password of the storage agent. The password must be the same as thepassword that was used when defining the storage agent as a server to the TSMserver. The password is encrypted.

SET STAHLADDRESSSets the TCP/IP address of the storage agent.

DEFINE SERVERThe definition of the TSM server with which the storage agent communicates.

DEFINE LIBRARYThe definition of an ACSLS-managed library to the TSM server. TheEXTERNALMANAGER parameter must specify the path where the external librarymanager executable is located on the same machine as the storage agent.


||

||

|||||||||

||

|

|||

||||

||

||

||||

A.

Ad

min

istration

and

Co

nfig

uratio

nR

eference

Legacy ACSLS Data Migration andCoexistence

Note: For the latest information concerning migration and coexistence, see the TivoliStorage Manager readme.

If your environment consists of TSM storage pools associated with an ACSLS library typeand a device class containing the GENERICTAPE device type, you need to considermigration and coexistence issues for existing data. To take advantage of LAN-free datatransfer, the data must be migrated to a storage pool associated with an EXTERNAL librarytype and a device class containing the ECARTRIDGE device type. Data migration isrecommended over coexistence.

Data MigrationData migration of ACSLS to EXTERNAL is recommended. Migrate the existing data fromexisting (old) storage pools to new storage pools associated with the appropriate policy,device class, and library definitions. Migration of data also allows the entire environment tobe LAN-free, providing better performance and better utilization of tape drives and media.

Figure 8 displays the normal migration path from an old storage pool containing the dataassociated with the ACSLS library type to a new storage pool associated with anEXTERNAL library type and an ECARTRIDGE device class.

Two methods to migrate data are:

Figure 8. Legacy ACSLS Data Migration

B


|

|||

|

|

|

||

||||||

|

||||

||||

|

B.

Leg

acyA

CS

LS

Data

Mig

ration

and

Co

existence

¶ Use the Tivoli Storage Manager server MOVE DATA command. This method allows thelegacy ACSLS data to move to a new storage pool without moving any expired files inthe aggregates. For more information, see the Managing Storage Pools and Volumessection of the Administrator’s Guide.

¶ Use the Tivoli Storage Manager server storage pool reclamation function. This methodworks by reclaiming the active files from the legacy ACSLS storage pools. Reclamationprocessing, however, is very resource intensive and should be performed during periodsof low resource utilization. For more information, see Reclaiming Space in SequentialAccess Storage Pools section of the Administrator’s Guide.

Data CoexistenceStorage pool volumes created using the ACSLS library type cannot be accessed using theEXTERNAL library type, but the two library types can coexist on the same STK library.Even though ACSLS and EXTERNAL data coexistence is not recommended, coexistencemight provide a temporary solution during the migration for certain environments, such as,large amounts of legacy ACSLS data and very small migration time-windows. AllowingACSLS and EXTERNAL library types to coexist requires that tape drives within the librarybe partitioned. The ACSLS library type requires at least one dedicated tape drive. If youchoose to have data coexist, either temporarily or long-term, be sure to implement thefollowing in your environment set-up:

¶ Leave at least one dedicated drive with its original configuration (that is, leave drivemapping intact) using the same device driver as when the data using the ACSLS librarytype was originally written.

¶ Start the SSI daemon in the following order:

1. Issue the rc_acs.ssi script from the TSM ACSLS support.

2. Issue the rc.edt script from the Gresham EDT support.


||||

|||||

|

|||||||||

|||

|

|

|

Where to Look for Information

This appendix describes the service that IBM provides for Tivoli Managed System for SANStorage Agent and tells you where to look for more information about Tivoli StorageManager products.

Contacting Customer SupportFor support for this or any Tivoli product, you can contact Tivoli Customer Support in oneof the following ways:

¶ Visit the Tivoli Storage Manager technical support Web site athttp://www.tivoli.com/support/storage_mgr/tivolimain.html.

¶ Submit a problem management record (PMR) electronically at IBMSERV/IBMLINK.You can access IBMLINK at http://www2.ibmlink.ibm.com.

¶ Submit a problem management record (PMR) electronically athttp://www.tivoli.com/support. See “Reporting a Problem” on page 38 for details.

¶ Send e-mail to [email protected].

Customers in the United States can also call 1-800-TIVOLI8 (1-800-848-6548). For productnumbers 5697-TS9, 5697-DRS or 5697-DPM call 1-800-237-5511.

International customers should consult the Web site for customer support telephone numbers.

You can also review the Customer Support Handbook, which is available on our Web site athttp://www.tivoli.com/support/handbook/.

When you contact Tivoli Customer Support, be prepared to provide identificationinformation for your company so that support personnel can readily assist you. Companyidentification information may also be needed to access various online services available onthe Web site.

The support Web site offers extensive information, including a guide to support services (theCustomer Support Handbook); frequently asked questions (FAQs); and documentation for allTivoli products, including Release Notes, Redbooks, and Whitepapers. The documentationfor some product releases is available in both PDF and HTML formats. Translateddocuments are also available for some product releases.

You can order documentation by e-mail at [email protected]. Please provide the publicationnumber, part number, or order number of the desired document. Alternatively, you canprovide the document title, version number, and date of publication.

C


|

|

|||

|

||

||

||

||

|

||

|

||

||||

|||||

|||

C.

Wh

ereto

Lo

ok

for

Info

rmatio

n


http://www2.ibmlink.ibm.com

http://www.tivoli.com/support

http://www.tivoli.com/support/handbook/

We are very interested in hearing about your experience with Tivoli products anddocumentation. We also welcome your suggestions for improvements. If you have commentsor suggestions about our documentation, please contact us in one of the following ways:

¶ Send e-mail to [email protected].

¶ Complete our customer feedback survey at http://www.tivoli.com/support/feedback/.

Reporting a ProblemPlease have the following information ready when you report a problem:

¶ The Tivoli Storage Manager server version, release, modification, and service levelnumber. You can get this information by entering the QUERY STATUS command at theTSM command line.

¶ The Tivoli Storage Manager client version, release, modification, and service levelnumber. You can get this information by entering dsmc at the command line.

¶ The communication protocol (for example, TCP/IP), version, and release number you areusing.

¶ The activity you were doing when the problem occurred, listing the steps you followedbefore the problem occurred.

¶ The exact text of any error messages.

InternetYou can get additional information through an anonymous FTP server,ftp://ftp.software.ibm.com. Tivoli Storage Manager information is in the/storage/tivoli-storage-management directory.

A newsgroup, [email protected], is implemented by a third party. IBM supports thisnewsgroup on a best-effort basis only.

Tivoli Storage Manager PublicationsThe following table lists TSM server publications.

Publication Title Order Number

Tivoli Storage Manager Messages GC35-0405

Tivoli Storage Management Products License Information GH09-4572

Tivoli Storage Manager for AIX Quick Start GC35-0402

Tivoli Storage Manager for AIX Administrator’s Guide GC35-0403

Tivoli Storage Manager for AIX Administrator’s Reference GC35-0404

Tivoli Storage Manager for AIX Managed System for SAN Storage AgentUser’s Guide

GC36-0001

Tivoli Storage Manager for Sun Solaris Managed System for SAN StorageAgent User’s Guide

GC36-0002

Tivoli Storage Manager for Windows Managed System for SAN StorageAgent User’s Guide

GC35-0434


|||

|

|

|

|

|||

||

||

||

|

|

|||

||

|

|

|||

||

||

||

||

||

|||

|||

|||

|

http://www.tivoli.com/support/feedback/

ftp://ftp.software.ibm.com

The following table lists the TSM client publications.


Tivoli Space Manager for UNIX Using the Hierarchical StorageManagement Clients

SH26-4115

Tivoli Storage Manager for Macintosh Using the Backup-Archive Client SH26-4120

Tivoli Storage Manager for UNIX Using the Backup-Archive Clients SH26-4122

Tivoli Storage Manager for NetWare Using the Backup-Archive Client SH26-4116

Tivoli Storage Manager for Windows Using the Backup-Archive Clients SH26-4117

Tivoli Storage Manager Installing the Clients SH26-4119

Tivoli Storage Manager Quick Reference for the Backup-Archive Clients SH26-4118

Tivoli Storage Manager Trace Facility Guide SH26-4121

Tivoli Storage Manager Using the Application Programming Interface SH26-4123

The following table lists Tivoli Data Protection publications.


Tivoli Data Protection for Informix Installation and User’s Guide SH26-4095

Tivoli Data Protection for Lotus Domino, S/390 Edition Licensed ProgramSpecifications

GC26-7305

Tivoli Data Protection for Lotus Domino for UNIX Installation and User’s Guide SH26-4088

Tivoli Data Protection for Lotus Domino for Windows NT Installation GC26-7320

Tivoli Data Protection for Lotus Notes on AIX Installation and User’s Guide SH26-4067

Tivoli Data Protection for Lotus Notes on Windows NT Installation and User’sGuide

SH26-4065

Tivoli Data Protection for Microsoft Exchange Server Installation and User’s Guide SH26-4110

Tivoli Data Protection for Microsoft SQL Server Installation and User’s Guide SH26-4111

Tivoli Data Protection for Oracle for UNIX Installation and User’s Guide SH26-4112

Tivoli Data Protection for Oracle for Windows NT Installation and User’s Guide SH26-4113

Tivoli Data Protection for R/3 Installation and User’s Guide SC33-6389

Tivoli Data Protection for Workgroups for Windows NT User’s Guide GC35-0359

Tivoli Data Protection for Workgroups for NetWare User’s Guide GC32-0444

Related IBM Hardware Products PublicationsThe following table lists related IBM hardware products publications.

Title Order Number

IBM 3490 Magnetic Tape Subsystem Enhanced Capability Models E01 andE11 User’s Guide

GA32-0298

IBM SCSI Tape Drive, Medium Changer, and Library Device Drivers:Installation and User’s Guide

GC35-0154

Magstar 3494 Tape Library Operator Guide GA32-0280

Magstar 3494 Tape Library Introduction and Planning Guide GA32-0279

IBM Magstar 3590 Tape Subsystem Operator’s Guide GA32-0330


|

|||

|||

||

||

||

||

||

||

||

|||

|

|||

||

|||

||

||

||

|||

||

||

||

||

||

||

|||

|

|

|||

|||

|||

||

||

||

C.

Wh

ereto

Lo

ok

for

Info

rmatio

n

Title Order Number

IBM 3570 Magstar MP Tape Subsystem Operator’s Guide GA32-0345

IBM RedbooksThe International Technical Support Center (ITSC) publishes redbooks, which are books onspecialized topics, such as, Using TSM to Back Up Databases. You can order publicationsthrough your IBM representative or the IBM branch office serving your locality. You canalso search for and order books of interest to you by visiting the IBM Redbooks home pageon the World Wide Web at this address: http://www.redbooks.ibm.com.

TranslationsTivoli Storage Agent is supported in only US English. Other language support is notavailable at this time.


||

|||

|

|||||

|

||

http://www.redbooks.ibm.com

Notices

This information was developed for products and services offered in the U.S.A. IBM maynot offer the products, services, or features discussed in this document in other countries.Consult your local IBM representative for information on the products and services currentlyavailable in your area. Any reference to an IBM product, program, or service is not intendedto state or imply that only that IBM product, program, or service may be used. Anyfunctionally equivalent product, program, or service that does not infringe any IBMintellectual property right may be used instead. However, it is the user’s responsibility toevaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described inthis document. The furnishing of this document does not give you any license to thesepatents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM IntellectualProperty Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other countrywhere such provisions are inconsistent with local law: INTERNATIONAL BUSINESSMACHINES CORPORATION PROVIDES THIS PUBLICATION “AS IS” WITHOUTWARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUTNOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do notallow disclaimer of express or implied warranties in certain transactions, therefore, thisstatement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes areperiodically made to the information herein; these changes will be incorporated in neweditions of the publication. IBM may make improvements and/or changes in the product(s)and/or the program(s) described in this publication at any time without notice.

D


D.

No

tices

Any references in this information to non-IBM Web sites are provided for convenience onlyand do not in any manner serve as an endorsement of those Web sites. The materials atthose Web sites are not part of the materials for this IBM product, and use of those Websites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believesappropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose ofenabling: (i) the exchange of information between independently created programs and otherprograms (including this one) and (ii) the mutual use of the information which has beenexchanged, should contact:

IBM CorporationInformation Enabling RequestsDept. M135600 Cottle RoadSan Jose CA 95193-0001U.S.A.

Such information may be available, subject to appropriate terms and conditions, including insome cases, payment of a fee.

The licensed program described in this information and all licensed material available for itare provided by IBM under terms of the IBM Customer Agreement, IBM InternationalProgram License Agreement, or any equivalent agreement between us.

Information concerning non-IBM products was obtained from the suppliers of thoseproducts, their published announcements or other publicly available sources. IBM has nottested those products and cannot confirm the accuracy of performance, compatibility or anyother claims related to non-IBM products. Questions on the capabilities of non-IBM productsshould be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. Toillustrate them as completely as possible, the examples include the names of individuals,companies, brands, and products. All of these names are fictitious and any similarity to thenames and addresses used by an actual business enterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and color illustrations may notappear.

TrademarksThe following terms are trademarks of the International Business Machines Corporation inthe United States, other countries, or both:

AIXIBMIBMLink

Tivoli is a trademark of Tivoli Systems Inc. in the United States, other countries, or both.


Microsoft®, Windows, Windows NT®, and the Windows logo are trademarks of MicrosoftCorporation in the United States, other countries, or both.

StorageTek is a trademark of Storage Technology Corporation in the United States, othercountries, or both.

ACSLS is a trademark of Storage Technology Corporation in the United States, othercountries, or both.

EDT-DistribuTAPE is a trademark of Gresham in the United States, other countries, or both.

UNIX® is a registered trademark of The Open Group in the United States and othercountries.

Other company, product, and service names may be trademarks or service marks of others.


D.

No

tices

Glossary

A

ACSLSAutomated Cartridge System Library Software

APIApplication program interface.

application clientOne of the Tivoli Data Protection for application programs installed on a system. The Tivoli Storage Managerserver provides backup services to these clients.

application program interface (API)A set of functions that applications running on a client platform can call to store, query, and retrieve objects fromTSM storage.

archiveA function that allows users to copy one or more files to a storage pool for long-term storage. Archive copiesmay be accompanied by descriptive information and may be retrieved by archive date, by file name, or bydescription. Contrast with retrieve.

automated cartridge system library software (ACSLS)StorageTek ACSLS software is a library-enablement application. ACSLS functions as the central service providerfor library operations.

B

backupThe process of copying information for safekeeping. TSM has processes for backing up user files, the TSMdatabase, and storage pools. For example, users can back up one or more files to a storage pool to ensure againstloss of data. Contrast with restore.

backup-archive clientA program that runs on a workstation or file server and provides a means for users to back up, archive, restore,and retrieve files.

C

clientA program running on a PC, workstation, file server, LAN server, or mainframe that requests services of anotherprogram, called the server. The following types of clients can obtain services from a TSM server: administrativeclient, application client, API client, backup-archive client, HSM client (also known as space manager client), andhost server.

The terms in this glossary are defined as they pertain to the Tivoli Storage Manager library. If you do not find the term you need,refer to the IBM Software Glossary on the Web at this URL: www.ibm.com/ibm/terminology/. You can also refer to IBM Dictionaryof Computing, New York: McGraw-Hill, 1994. For a complete Tivoli Storage Manager glossary, see Administrator’s Guide.

This glossary may include terms and definitions from:

¶ The American National Standard Dictionary for Information Systems, ANSI X3.172-1990, copyright (ANSI). Copies may bepurchased from the American National Standards Institute, 11 West 42nd Street, New York 10036.

¶ The Information Technology Vocabulary, developed by Subcommittee 1, Joint Technical Committee 1, of the InternationalOrganization for Standardization and the International Electrotechnical Commission (ISO/IEC JTC2/SC1).


||

|||

Glo

ssary

http://www.ibm.com/ibm/terminology

client nodeA file server or workstation on which the backup-archive client program has been installed, which has beenregistered to the server.

client options fileA file that a client can change, containing a set of processing options that identify the server, communicationmethod, and options for backup, archive, hierarchical storage management, and scheduling. Also called thedsm.opt file.

D

device classA named group of storage devices with common characteristics. Each device class has a unique name andrepresents a device type of disk, file, optical disk, or tape.

device configuration file(1) On a TSM storage agent, a file that contains the name and password of the storage agent and the DEFINESERVER command for the TSM server that is managing the SAN-attached libraries and drives (2) On a TSMserver, a file that contains information about defined device classes, and, on some TSM servers, defined librariesand drives.

device driverA collection of subroutines that control the interface between I/O device adapters and the processor.

device typeA category of storage device. Each device class is categorized with one of the supported device types, forexample, DISK or CARTRIDGE.

driveA device used to read and write data on a medium such as a magnetic disk, optical disk, or tape.

drive mappingThe correlation of drive names between a TSM server and a TSM storage agent.

dsm.opt fileSee client options file and client user options file.

dsmserv.optSee server options file.

dsmsta.optSee storage agent options file.

E

External libraryA type of enablement provided by TSM to allow LAN-free data movement for ACSLS managed STK libraries.To activate this support the TSM library type must be EXTERNAL.

F

FILE device typeA device type that specifies sequential access files on disk storage.

L

LANLocal area network.

LAN-free data transferThe movement of client data directly from a client to a storage device over a SAN, rather than over the LAN.


|||

library(1) A repository for demountable recorded media, such as magnetic tapes. (2) For TSM, a collection of one ormore drives, and possibly robotic devices (depending on the library type), which can be used to access storagevolumes.

library managerA TSM server that controls device operations when multiple TSM servers share a storage device. Theseoperations include mount, dismount, volume ownership, and library inventory.

local area network (LAN)A network in which a set of devices are connected to one another for communication and that can be connectedto a larger network.

M

management classA policy object that users can bind to each file to specify how the server manages the file. The management classcan contain a backup copy group, an archive copy group, and space management attributes. The copy groupsdetermine how the TSM server manages backup versions or archive copies of files. The space managementattributes determine whether files are eligible for migration from space manager client nodes to TSM storage, andunder what conditions. See also copy group.

mount requestA server request to mount a sequential access media volume so that data can be read from or written to thesequential access media.

N

nodeA unique name used to identify a workstation to the server. See also client node.

P

policy domainA policy object that contains policy sets, management classes, and copy groups that are used by a group of clientnodes. See policy set and management class.

policy setA policy object that contains a group of management class definitions that exist for a policy domain. At any onetime there can be many policy sets within a policy domain but only one policy set can be active. See policydomain and management class.

R

reclamationA process of consolidating the remaining data from many sequential access volumes onto fewer new sequentialaccess volumes.

restoreThe process of returning a backup copy to an active storage location for use. TSM has processes for restoring itsdatabase, storage pools, storage pool volumes, and users’ backed-up files. For example, users can copy a backupversion of a file from the storage pool to the workstation. The backup version in the storage pool is not affected.Contrast with backup.

S

SANStorage area network.


Glo

ssary

SCSISmall computer system interface.

serverThe program that provides backup, archive, space management, and administrative services to clients. The serverprogram must be at the necessary level to provide all of these services.

server options fileA file that specifies processing options for communication methods, tape handling, pool sizes, language, and date,time, and number formats.

server storageThe storage pools used by the server to store users’ files: backup versions, archive copies, and files migratedfrom Tivoli Space Manager client nodes (space-managed files). See storage pool.

shared libraryA library device that is shared among multiple Tivoli Storage Manager servers.

storage agentA program that enables Tivoli Storage Manager to back up and restore client data directly to and fromSAN-attached storage.

storage agent options fileA file that specifies options for the storage agent. This includes the name of the TSM server with which thestorage agent communicates, the number of sessions that can be kept open to the server, and the name of thedevice configuration file.

storage area network (SAN)A high-speed communications network optimized for storage.

storage poolA named set of storage volumes that TSM uses to store client data. A storage pool is either a primary storagepool or a copy storage pool.

T

tape library(1) A term used to refer to a collection of tape cartridges. (2) An automated device that performs tape cartridgemounts and demounts without operator intervention.

TCP/IPTransmission Control Protocol/Internet Protocol.

Tivoli Storage Manager (TSM)A client/server program that provides storage management to customers in a multivendor computer environment.

Transmission Control Protocol/Internet Protocol (TCP/IP)A set of communication protocols that support peer-to-peer connectivity functions for both local and wide areanetworks.

TSMTivoli Storage Manager.

TSM application program interface (API)A set of functions that applications running on a client platform can call to store, query, and retrieve objects fromTSM storage.


Index

AACSLS support 5, 20, 35

Ddata movement, SAN

prerequisites 7tasks 9

device configuration file 32disk device

mapping drives 19SANergy 2.2 9server install 17

drive mappingcommand example 19disk devices 19general considerations 18tape devices 19

dsm.opt file 13, 22dsmsta.opt 16, 25, 32DSMSTA SETSTORAGESERVER 16, 25

Eenablelanfree option 13, 22external library support 5, 20, 35

FFILE library

configuration considerations 4disk devices 17

Hhow to determine LAN-free data movement 20, 28

LLAN-free data movement

enabling, dsm.opt 13, 22guidelines for determining 20, 28

library client 3

library manager 3limit the SAN drives 19

MManaged System for SAN

description 1FILE library 4planning configurations 3policy considerations 17, 26SANergy Metadata Controller 4

Nnetwork requirements 11, 20no-query restore 2

Oobtaining tape device information 18option, enablelanfree 13, 22options file

client 13, 22storage agent 16, 25, 32

Ppolicy for Managed System for SAN 17, 26

SSAN data movement

prerequisites 7tasks 9

storage agentcomponent configuration 7configuring device access 17device configuration file 32installing 14, 23options file 32starting 19, 27usage requirements 7verify configuration 20, 27


Ind

ex

Ttape device information, obtaining 18TSM API

install 13, 22upgrade 13, 22


Program Number: 5698-TSM

Printed in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.

GC36-0001-01

tivoli storage manager for aix - ibm supportpublib.boulder.ibm.com/tividd/td/smaixn/gc36-0001... ·...

Documents