tivoli storage manager storage agent

62
Tivoli Storage Manager for AIX Managed System for SAN Storage Agent User’s Guide Version 5 Release 1 GC32-0771-00

Upload: micka-luboya

Post on 12-Mar-2015

184 views

Category:

Documents


10 download

TRANSCRIPT

Page 1: Tivoli Storage Manager Storage Agent

Tivoli Storage Managerfor AIX

Managed System for SANStorage Agent User’s GuideVersion 5 Release 1

GC32-0771-00

Page 2: Tivoli Storage Manager Storage Agent
Page 3: Tivoli Storage Manager Storage Agent

Tivoli Storage Managerfor AIX

Managed System for SANStorage Agent User’s GuideVersion 5 Release 1

GC32-0771-00

Page 4: Tivoli Storage Manager Storage Agent

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

First Edition (March 2002)

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

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 v.

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

Page 5: Tivoli Storage Manager Storage Agent

Contents

About This Book . . . . . . . . . . . vWhere to Look for Information . . . . . . . . v

Contacting Customer Support . . . . . . . vInternet . . . . . . . . . . . . . . . viTivoli Storage Manager Publications . . . . . viRelated IBM Hardware Products Publications viiiIBM Redbooks . . . . . . . . . . . . viiiTranslations . . . . . . . . . . . . . viii

Summary of Changes for Tivoli StorageManager . . . . . . . . . . . . . . ixTechnical Changes for Version 5 Release 1—March2002 . . . . . . . . . . . . . . . . . ix

Chapter 1. Storage Agent Overview . . . 1LAN-free Client Data Backup Scenario. . . . . . 2Dual-session No-Query Restore for LAN-free Path. . 2

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

Sharing Tape Storage using TSM LibraryManager/Client . . . . . . . . . . . . 3Sharing Disk Storage using Tivoli SANergy . . . 4External Library — Sharing ACSLS-ManagedLibraries . . . . . . . . . . . . . . . 5

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

Chapter 3. Installation and Configuration 9Summary of Tasks for Procedure 1 . . . . . . . 9Summary of Tasks for Procedure 2 . . . . . . 10Procedure 1— Tape and File Sharing with SCSI and349X Tape and File Devices . . . . . . . . . 10Step 1. Network . . . . . . . . . . . . . 10Establishing Communications among Client, StorageAgent, and Server . . . . . . . . . . . . 11

Step 2. Client System . . . . . . . . . . 11Step 3. Tivoli Storage Manager Server . . . . 15

Configuring Devices for the Storage Agent to Access 17Step 4. Client System . . . . . . . . . . 17Step 5. Server. . . . . . . . . . . . . 18

Step 6. Client System . . . . . . . . . . . 19Start the Storage Agent . . . . . . . . . 19Verify the LAN-free Configuration. . . . . . 20

Procedure 2 — External Library Environment withan ACSLS–Managed Library. . . . . . . . . 21

Step 1. Network . . . . . . . . . . . . 21Establishing Communications among Client,Storage Agent, and Server . . . . . . . . 21Configuring Devices for the Storage Agent toAccess . . . . . . . . . . . . . . . 28Step 4. Client System . . . . . . . . . . 28

Appendix A. Administration andConfiguration Reference . . . . . . . 31Starting and Stopping the Storage Agent . . . . 31Obtaining Tape Device Information on the ClientSystem . . . . . . . . . . . . . . . . 31Set Installation Data for the Storage Agent: DSMSTASETSTORAGESERVER. . . . . . . . . . . 32The Storage Agent Options File. . . . . . . . 34The Device Configuration File for the Storage Agent 34

Appendix B. Legacy ACSLS DataMigration and Coexistence . . . . . . 37Data Migration . . . . . . . . . . . . . 37Data Coexistence . . . . . . . . . . . . 38

Appendix C. Notices . . . . . . . . . 39Trademarks . . . . . . . . . . . . . . 40

Glossary . . . . . . . . . . . . . . 43

Index . . . . . . . . . . . . . . . 47

© Copyright IBM Corp. 2000, 2002 iii

Page 6: Tivoli Storage Manager Storage Agent

iv Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 7: Tivoli Storage Manager Storage Agent

About This Book

This user’s guide is intended for anyone who will be using the Tivoli® ManagedSystem for SAN product, commonly referred to as the storage agent. Thisdocument provides an overview of LAN-free data transfer. It also providesdetailed explanations about configuring and using the Tivoli Storage Manager(TSM) client, storage agent, and TSM server. You should be familiar with TSM,SAN, and operating system administration. You may require additionalpublications during configuration of the storage agent environment. Refer to thelisting of Tivoli Storage Manager Publications in “Where to Look for Information”.

Note: Tivoli Managed System for SAN is only supported in US English. At thetime of publishing this document no other language support was available.

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

Where to Look for InformationThe following describes the service that IBM® provides for Tivoli Managed Systemfor SAN Storage Agent and tells you where to look for more information aboutTivoli Storage Manager products.

Contacting Customer SupportFor support for this or any Tivoli product, you can contact Tivoli CustomerSupport in one of the following ways:v Visit the Tivoli Storage Manager technical support Web site at

http://www.tivoli.com/support/storage_mgr/tivolimain.html.v Submit a problem management record (PMR) electronically at

IBMSERV/IBMLINK. You can access IBMLINK athttp://www2.ibmlink.ibm.com.

v Submit a problem management record (PMR) electronically athttp://www.tivoli.com/support. See “Reporting a Problem” on page vi fordetails.

v Send e-mail to [email protected].

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

International customers should consult the Web site for customer supporttelephone numbers.

You can also review the Customer Support Handbook, which is available on our Website at http://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.Company identification information may also be needed to access various onlineservices available on the Web site.

© Copyright IBM Corp. 2000, 2002 v

Page 8: Tivoli Storage Manager Storage Agent

The support Web site offers extensive information, including a guide to supportservices (the Customer Support Handbook); frequently asked questions (FAQs);and documentation for all Tivoli products, including Release Notes, Redbooks™,and Whitepapers. The documentation for some product releases is available inboth PDF and HTML formats. Translated documents are also available for someproduct releases.

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

We are very interested in hearing about your experience with Tivoli products anddocumentation. We also welcome your suggestions for improvements. If you havecomments or suggestions about our documentation, please contact us in one of thefollowing ways:v 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:v The Tivoli Storage Manager server version, release, modification, and service

level number. You can get this information by entering the QUERY STATUScommand at the TSM command line.

v The Tivoli Storage Manager client version, release, modification, and servicelevel number. You can get this information by entering dsmc at the commandline.

v The communication protocol (for example, TCP/IP), version, and release numberyou are using.

v The activity you were doing when the problem occurred, listing the steps youfollowed before the problem occurred.

v The exact text of any error messages.

InternetYou can access 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 supportsthis newsgroup on a best-effort basis only.

Tivoli Storage Manager PublicationsThe following table lists Tivoli Storage Manager server publications.

Publication Title Order Number

Tivoli Storage Management Products License Information GH09-4572

Tivoli Storage Manager Messages GC32-0767

Tivoli Storage Manager for AIX Administrator’s Guide GC32-0768

Tivoli Storage Manager for AIX Administrator’s Reference GC32-0769

Tivoli Storage Manager for AIX Quick Start GC32-0770

vi Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 9: Tivoli Storage Manager Storage Agent

The following table lists Tivoli Storage Manager storage agent publications.

Publication Title Order Number

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

GC32-0771

Tivoli Storage Manager for HP-UX Managed System for SAN StorageAgent User’s Guide

GC32-0727

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

GC32-0781

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

GC32-0785

The following table lists the Tivoli Storage Manager client publications.

Publication Title Order Number

Tivoli Space Manager for UNIX: Using the Hierarchical StorageManagement Clients

GC32-0794

Tivoli Storage Manager for Macintosh: Backup-Archive Installation andUser’s Guide

GC32-0787

Tivoli Storage Manager for NetWare: Backup-Archive Installation andUser’s Guide

GC32-0786

Tivoli Storage Manager for UNIX: Backup-Archive Installation and User’sGuide

GC32-0789

Tivoli Storage Manager for Windows: Backup-Archive Installation andUser’s Guide

GC32-0788

Tivoli Storage Manager Trace Facility Guide GC32-0792

Tivoli Storage Manager Using the Application Program Interface GC32-0793

The following table lists Tivoli Data Protection publications.

Publication TitleOrderNumber

Tivoli Data Protection for EMC Symmetrix for R/3 Installation and User’s Guide SC33-6386

Tivoli Data Protection for IBM ESS for Oracle Databases DB2 UDB Installationand User’s Guide

SH26-4125

Tivoli Data Protection for IBM ESS for R/3 Installation and User’s Guide SC33-6387

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

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

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

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

GC26-7305

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 Installation and User’s Guide SH26-4113

About This Book vii

Page 10: Tivoli Storage Manager Storage Agent

Publication TitleOrderNumber

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

Tivoli Data Protection for R/3 Installation and User’s Guide for DB2 UDB SC33-6341

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

Tivoli Data Protection for WebSphere Application Server Installation and User’sGuide

SC33-6399

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 Magstar 3494 Tape Library Introduction and Planning Guide GA32-0279

IBM 3490E Model E01 and E11 User’s Guide GA32-0298

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

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

GC35-0154

IBM TotalStorage Enterprise Tape System 3590 Operator Guide GA32-0330

IBM Magstar 3494 Tape Library Dataserver Operator Guide GA32-0280

IBM RedbooksThe International Technical Support Center (ITSC) publishes redbooks, which arebooks on specialized topics, such as, Using TSM to Back Up Databases. You canorder publications through your IBM representative or the IBM branch officeserving your locality. You can also search for and order books of interest to you byvisiting the IBM Redbooks home page on the World Wide Web at this address:http://www.redbooks.ibm.com.

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

viii Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 11: Tivoli Storage Manager Storage Agent

Summary of Changes for Tivoli Storage Manager

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

Technical Changes for Version 5 Release 1—March 2002The following changes have been made to the product for this edition:

Changes in Defining Drives and Libraries

v Device names are now specified in the DEFINE PATH and UPDATEPATH commands, rather than in the DEFINE DRIVE, UPDATE DRIVE,DEFINE LIBRARY, and UPDATE LIBRARY commands.

v Path names for external libraries are now specified in the DEFINE PATHcommand.

v Drive mapping is no longer supported and has been replaced by theDEFINE PATH command.

Data Validation with Cyclic Redundancy CheckingTivoli Storage Manager provides the option of specifying whether a cyclicredundancy check (CRC) is performed during a client session with theserver, storage agent, or for storage pools. The server or storage agentvalidates the data by using a cyclic redundancy check which can helpidentify data corruption. Data validation can be enabled for one or all ofthe following:v Tivoli Storage Manager storage agents at Version 5.1v Tivoli Storage Manager client nodes at Version 5.1v Storage Pools

See the DEFINE SERVER, UPDATE SERVER, DEFINE STGPOOL, UPDATESTGPOOL, DEFINE NODE and UPDATE NODE commands in the TSMAdministrator’s Reference.

© Copyright IBM Corp. 2000, 2002 ix

Page 12: Tivoli Storage Manager Storage Agent

x Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 13: Tivoli Storage Manager Storage Agent

Chapter 1. Storage Agent Overview

Managed System for SAN is a feature of Tivoli Storage Manager (TSM) thatenables LAN-free TSM client data movement. The TSM client data moves directlyto and from a storage device attached to a Storage Area Network (SAN), therebyoff-loading the data movement from the LAN and from the Tivoli Storage Managerserver. The storage agent is installed on the client machine and shares storageresources with the Tivoli Storage Manager server. The storage agent can writedirectly to storage media in a format that is consistent with that used by the server.The TSM server or servers control the storage devices and keep track of the datathat the client has stored. TSM continues to use a LAN connection to exchangecontrol information, such as policy information and data about the objects that arebacked up. Using the SAN for client data movement decreases the load on theTSM server and allows the server to support a greater number of simultaneousclient connections. See Figure 1.

To use Managed System for SAN you must install a storage agent on the clientsystem. The storage agent communicates with the server to obtain and storedatabase information and to coordinate device and volume access. The serverdetermines if the client is requesting access to storage for which the client has aSAN path defined. If a SAN path is defined, the client (by means of the storage

ClientStorage Agent installed

Tape Library

File Library

Library ControlClient Metadata

LibraryControl

ClientData

SAN

LAN

Storage Manager Server

Figure 1. SAN Data Movement. Solid lines indicate data movement. Broken lines indicatemovement of control information and metadata.

© Copyright IBM Corp. 2000, 2002 1

Page 14: Tivoli Storage Manager Storage Agent

agent) transfers data on that path. If a failure occurs on the SAN path, failoveroccurs and the client uses its LAN connection to the TSM server and moves theclient data over the LAN.

TSM supports SAN-attached device sharing in one of the following ways:v TSM native library management support consisting of a library manager and

library clients or just a library manager.v Shared disk storage using a FILE library and the integration of the Tivoli

SANergy™ product.v External library support, in tape libraries managed by StorageTek Automated

Cartridge System Library Software (ACSLS) and middleware that enables TSMto share ACSLS-managed libraries. In this environment the device sharingcapability is provided by third-party software, such as Gresham Extended DataTechnology DistribuTAPE (EDT-DistribuTAPE) a middleware software programthat takes advantage of TSM’s external library interface to allow tape drives inACSLS-managed libraries to be shared among TSM servers.

For additional information about these configurations, see “Types ofConfigurations” on page 3.

LAN-free Client Data Backup ScenarioThe following outlines a typical backup scenario for a TSM client that uses SANdata movement. This scenario does not apply to External library environments.1. The client begins a backup operation. The client and the server exchange policy

information 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 poolthat uses a device on the SAN. That device must also have a defined pathbetween the device and the storage agent.

2. Because the destination is on the SAN, the client contacts the storage agent,which will handle the data transfer. The storage agent sends a request for avolume mount to the server.

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

device over the SAN.6. The storage agent sends file attribute information to the TSM server, and the

server stores 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 restoreand sends data to the client while continuing to build the list. This type of restoreis more efficient especially in a LAN-free environment, and allows the restore to berestarted if interrupted. Two sessions are used for the restore when data for therestore 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 othersession uses the storage agent to restore data over the LAN-free path. This worksonly with clients at the 4.2 level or above.

2 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 15: Tivoli Storage Manager Storage Agent

Chapter 2. Planning

You can set up a Managed System for SAN in a number of configurations.Planning the system configuration provides a smooth transition through systemsetup and into production. As part of your planning, you need to identify thefollowing:v Which configuration to implementv Devices to be used for LAN-free data movementv Clients to use LAN-free data movementv 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 different types of configurations that take advantage of what can beaccomplished using a storage agent in a LAN-free environment. Your environmentis dependent upon the type of storage device you will be using for LAN-free datastorage. The following sections cover descriptions and planning considerations forseveral typical LAN-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” on page 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 librarymanager and library clients, one server, the library manager, owns and controls thetape library device. The library manager operations include checking volumes intoand out of the library, labeling volumes, mounting and dismounting volumes,auditing volumes, and creating an inventory of library contents, see Figure 2 onpage 4. The library manager also manages the storage hierarchy and performs suchserver functions as storage pool migrations, reclamation, collocation, and backupand restore of storage pools and the database. All of the other TSM servers sharingthis library are considered library clients. A library client requests shared libraryresources such as, drives or media from the TSM server acting as the librarymanager, but uses the resources independently. The library manager coordinatesthe access to these resources. Data moves over the SAN between the storage deviceand either the library manager or the library client. Either the library manager orany library client can manage the LAN-free movement of client data as long as theclient system includes a storage agent.

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

© Copyright IBM Corp. 2000, 2002 3

Page 16: Tivoli Storage Manager Storage Agent

Note: An environment can have a Library Manager without a Library Client.

The configurations represented in the previous illustration are the following:v A TSM server library manager manages a client’s data, which is stored on a tape

library.v 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 FILElibrary (TSM server File device class) and utilizes the SANergy product. SANergyprovides a file sharing accelerator. If you will be using a FILE library, you mustdetermine where the Tivoli SANergy client and the Tivoli SANergy MetadataController (MDC) will be installed. You will also require a Windows® share (CIFS)or a Network File Share (NFS) on a Unix system to achieve file sharing. SeeFigure 3 on page 5 and Table 1 on page 5 for the possible Tivoli SANergyconfigurations. See the SANergy publications for additional information aboutconfiguring SANergy.

Figure 2. Library Manager/Client LAN—free Configuration

4 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 17: Tivoli Storage Manager Storage Agent

In the following table, the numbers refer to those numbers in Figure 3. Forexample, one possible configuration is for the Tivoli SANergy client to be installedon the TSM client machine (�1�) and the Tivoli SANergy MDC to be installed onthe TSM server (�2�). These configurations can also consist of multiple platforms.For example, an environment can consist of a SUN MDC working with a Windowsand AIX client.

Table 1. Tivoli SANergy Configurations

Tivoli SANergyComponent

Where Installed

Tivoli SANergyClient

�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 isenabled by middleware (such as, Gresham EDT-DistribuTAPE) between the datastorage manager (TSM) and a media manager (StorageTek ACSLS). See Figure 4 onpage 6. The ACSLS Server (or Library Station) manages the physical aspects of tapecartridge storage and retrieval. The external library manager, in this discussionGresham EDT, communicates with the ACSLS Server or LibraryStation to accesstape cartridges in an automated StorageTek library. The storage agent installed ona machine containing Gresham EDT and a TSM or Tivoli Data Protection (TDP)client provides access to SAN-attached storage devices resulting in LAN-free datamovement. The continued connection to the LAN provides a meta data (control

TSM ClientStorage Agent

TSM Server

Another Node

LAN

SAN

FILE Library

1

2

3

Figure 3. Tivoli SANergy Configurations

Chapter 2. Planning 5

Page 18: Tivoli Storage Manager Storage Agent

information) path. If the storage agent is not available, the LAN provides a failoverpath for data backup and recovery.

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

Data Migration and CoexistenceIf you currently have data associated with the TSM ACSLS library type and wantto take advantage of LAN-free, you will need to consider coexistence andmigration issues, see “Appendix B. Legacy ACSLS Data Migration andCoexistence” on page 37.

LAN

SAN

1234

LAN-freeData

Movement

1 2 3 4

Tivoli StorageManagerServer

GreshamEDT

Data Owner

Tivoli StorageManager

Client

GreshamEDT

StorageAgent

STK Tape Library

ChangerControl

ChangerControl

3270ChangerControl

Tape Drives

TCP/IP CommunicationFibre Channel3270 Communications-Library Control Commands

Library Manageron

z/OS

ACSLSServer

or

Figure 4. External Library Environment

6 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 19: Tivoli Storage Manager Storage Agent

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

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

v TCP/IP is required for communication among the TSM server, the client, and thestorage agent.

v A Tivoli Storage Manager server with this feature (version 5.1.0 or higher). Theserver and the storage agent must be at the same version, release, andmaintenance level. The TSM servers for the AIX®, HP-UX, Sun Solaris, andWindows operating systems support the Managed System for SAN feature.

v A Tivoli Storage Management client or a Tivoli Data Protection client). Clientsoftware 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).

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

v The TSM application program interface (API) software must be at the version 4.2or higher. You can obtain the API by downloading the latest version of thebackup-archive client for AIX from the Web site athttp://www.tivoli.com/support/storage_mgr/tivolimain.html.

v If you are sharing disk storage, Tivoli SANergy Version 2.2 or higher must beinstalled.

Note: If you are sharing only tape devices, Tivoli SANergy is not required.v 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. Foradditional information and product download, seehttp:www.greshamstorage.com/products/download/distributape.html.

Note: External library support only applies to Tivoli Storage Managerenvironments sharing Storage Technology (STK) tape devices.

Chapter 2. Planning 7

Page 20: Tivoli Storage Manager Storage Agent

8 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 21: Tivoli Storage Manager Storage Agent

Chapter 3. Installation and Configuration

The following information describes the installation and configuration of thestorage agent LAN-free environment. There are two procedures, which procedureyou choose to follow depends upon the type of environment you areimplementing.

The first procedure covers environments that are using one or more of thefollowing:v SCSI and 349X Tape Library sharing using the TSM Library Manager and Clientv File device sharing using SANergy

For installation and configuration steps, see “Procedure 1— Tape and File Sharingwith SCSI and 349X Tape and File Devices” on page 10 .

The second procedure specifically describes external library support for ACSLSlibrary environment configuration, see “Procedure 2 — External LibraryEnvironment with an ACSLS–Managed Library” on page 21.

For high-level descriptions of these environments, see “Chapter 1. Storage AgentOverview” on page 1 and “Types of Configurations” on page 3.

To begin the installation and configuration process, read the summary of theprocedure, review the complete procedure, and then perform the steps described inthe procedure. The summary itself briefly describes the overall configuration. It is agood idea to understand the overall process before beginning the procedure, sincethe process takes place on multiple machines at differing times. Following thesummary is the complete procedure containing the step-by-step installation andconfiguration instructions.

Summary of Tasks for Procedure 1The following summarizes the installation and configuration tasks provided in theprocedure:v Verifying network configuration

Network: Ensure that your system meets the prerequisites for the SANconfiguration.

v Establishing communications among client, storage agent, and TSM server

Client System:

– Install the TSM client or TDP client, and the TSM API. Specify the LAN-freeoption

– Install and set up the storage agent

TSM Server:

– If your environment is using tape devices, configure the library and drives onthe SAN

– If your environment is using disk devices, configure Enterprise Managementand define the FILE device class

v Configuring devices for the storage agent to access

© Copyright IBM Corp. 2000, 2002 9

Page 22: Tivoli Storage Manager Storage Agent

Client System:

– If your environment is using disk devices, skip this step– If your environment is using tape devices, obtain tape device information

Server (Storage Agent):

– Define paths between the storage agents and devices

Client System:

– Start the storage agent– Verify the LAN-free configuration

Summary of Tasks for Procedure 2The following summarizes the installation and configuration tasks provided in theprocedure:v Verifying network configuration

Network: Ensure that your system meets the prerequisites for the SANconfiguration.

v Establishing communications and configuring the client, storage agent, andTSM server

Client System:

– Install the TSM client or TDP client, and the TSM API. Specify the LAN-freeoption

– Install and set up the storage agent

TSM Server:

– Configure the library and drives on the SAN– Define the storage agent as a server

Client System:

– Start the storage agent– Verify the LAN-free configuration

Procedure 1— Tape and File Sharing with SCSI and 349X Tape and FileDevices

The following steps describe configuring a storage agent environment consisting ofeither shared libraries or shared disk, or both. If you are configuring an externallibrary, that is, an ACSLS-managed library environment, see “Procedure 2 —External Library Environment with an ACSLS–Managed Library” on page 21.

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 ofhardware and software. Ensure that your system configuration meets the hardware

10 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 23: Tivoli Storage Manager Storage Agent

and software requirements for the SAN setup. See the Web site,http://www.tivoli.com/support/storage_mgr/san/overview.html, for details.

Note: If you will be using Tivoli storage agent with disk media, you must haveinstalled Tivoli SANergy Version 2.2 on the applicable machines. SeeFigure 3 on page 5 for possible Tivoli SANergy configurations. See the TivoliSANergy Administrator’s Guide for details.

Establishing Communications among Client, Storage Agent, andServer

For a pictorial representation of what you will accomplish during the next twosteps, see Figure 5 on page 17 .

Step 2. Client SystemThe sections in this step describe installation of TSM client, API, and storage agentsoftware.

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

User’s Guide for the client. Install the client software and API if it is notalready installed on the system, or upgrade the software to the latest level asnecessary. The latest levels can be downloaded from the Tivoli Storage ManagerWeb site at http://www.tivoli.com/support/storage_mgr/tivolimain.html.

2. Modify the TSM options file (dsm.sys).For information about the dsm.opt and dsm.sys files, see Backup-ArchiveInstallation and User’s Guide.a. Edit the dsm.sys file to specify the communications method between the

TSM client and server. For example:COMMmethod TCPipTCPServeraddress tsmsrver.tucson.ibm.comTCPPort 1502

Note: For illustrative purposes a tcpport of 1502 is used in the examples,however, the default tcpport is 1500.

b. Edit the dsm.opt file to specify the server name of the dsm.sys stanza editedin step a. For example:servername tsmsrver

c. Add the following options to the same dsm.sys stanza edited in step a.These options specify that the client will use SAN-attached devices; whenthe path is available, during backup, restore, archive, and retrieveprocessing.enablelanfree yes

LANFREECommmethod TCPIPLANFREETCPPort 1500

orLANFREECommmethod SharedMemLANFREESHMPORT 1510

3. If your are using a TDP client, configure the API by performing the followingprocedure:a. Set up the environment variables. The TSM API uses unique environment

variables to locate files.

Chapter 3. Installation and Configuration 11

Page 24: Tivoli Storage Manager Storage Agent

v DSMI_CONFIG is the fully qualified name for the client user option file.v DSMI_DIR points to the path containing dsm.sys, dsmtca, and the

subdirectory en_US.v en_US subdirectory must contain dsmclientV3.cat.v 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=/usr/tivoli/tsm/client/api/bin/dsm.optexport DSMI_DIR=/usr/tivoli/tsm/client/api/binexport DSMI_LOG=/home/user_a/logdir

Note: The quickest method to set the environment variables is to add thesevariables to the user’s .profile file.

b. Edit the dsm.sys file to specify the communications method between theTSM API and server.1) If a dsm.sys file does not exist in the directory specified by DSMI_DIR,

create a symbolic link to the dsm.sys file in the TSM client installationdirectory. For example:ln -s /usr/tivoli/tsm/client/ba/bin/dsm.sys /usr/tivoli/tsm/client/api/bin/dsm.sys

2) Edit an existing stanza in the dsm.sys file or create a new stanza tospecify the options for connecting to the TSM server. For example:SErvername tsmsrverCOMMmethod TCPipTCPPort 1502TCPServeraddress tsmsrver.tucson.ibm.com

Note: For illustrative purposes a tcpport of 1502 is used in theexamples, however, the default tcpport is 1500.

It is assumed that the dsm.sys file is controlled by the systemadministrator. The Tivoli Storage Manager server administrator shouldsupply the name and IP address of the Tivoli Storage Manager server, aswell as the node name and password.

c. Edit the dsm.opt file specified by the DSMI_CONFIG environment variableto specify the server name of the dsm.sys stanza edited in the previous step.For example:

servername tsmsrver

Install and Configure the Storage Agent

Note: The Storage Agent should not be installed on the same machine as the TSMserver.

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

The instructions in this section are shown using the Software Management andInstallation Tool (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 bedifferent in your environment. Loading the storage agent files can takeseveral minutes.

Installation using the SMIT procedure:

12 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 25: Tivoli Storage Manager Storage Agent

1. Record the following information. This information is required throughout theremainder of this procedure.v Storage agent: Name and password for the storage agent. Decide on a

name and password that will be used to initialize the storage agent and todefine the storage agent as a server to the TSM server. For example:– Name: storagnt– Password: fun4me– TCP/IP address: agent.tucson.ibm.com

v TSM server: Information about the TSM server that the storage agent willneed in order to communicate with the server. This is the same TSM serverwith which the client communicates. For example:– Name: tsmsrver– Password: not4u– TCP/IP address: tsmsrver.tucson.ibm.com– TCP/IP port: 1502

Notes:

a. You can verify the server information by issuing the QUERY STATUScommand from a TSM administrative command-line.

b. The ’Server Password Set’ displayed in the QUERY STATUS outputmust be equal to YES and for this example the password is set to not4u.To set the server password issue the SET SERVERPASSWORD commandfrom a TSM administrative command-line. For example:set serverpassword not4u

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 of your AIX operating system.Enter:

smit install_update &

For AIX 4.3, select:

Install and Update SoftwareInstall and Update from the LATEST Available Software

For AIX 5.1, select:

Install SoftwareInstall Software

5. On the next window, select the device that you are using for the installation.You can enter the drive name in the window or click on List to access thedevice list.If you click on List, select the CD-ROM drive that you are using for theinstallation (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 on page 14, continueat step 10 on page 14.

Chapter 3. Installation and Configuration 13

Page 26: Tivoli Storage Manager Storage Agent

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

8. Select the components that you require. The following table lists thecomponent fileset file names.

Table 2. Package and Fileset Names for Installation. AIX 4.3.3 Platforms

Package Name Fileset Names Description

tivoli.tsm.StorageAgent.rte tivoli.tsm.StorageAgent.rte StorageAgent commonfunctions, 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 Onlinehelp

Table 3. Package and Fileset Names for Installation. AIX 5.1 Platforms

Package Name Fileset Names Description

tivoli.tsm.StorageAgent.rte tivoli.tsm.StorageAgent.rte StorageAgent commonfunctions, examples

tivoli.tsm.devices.aix5.rte64 tivoli.tsm.devices.aix5.rte64 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 Onlinehelp

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 fromSMIT.

14. Ensure that the DEVCONFIG option is specified in the dsmsta.opt file. Forexample, for a device configuration file named devconfig.out located at/usr/tivoli/tsm/StorageAgent/bin, edit the dsmsta.opt file and enter the followingline:DEVCONFIG devconfig.out

15. Use the information that you collected in step 1 on page 13 to issue theDSMSTA SETSTORAGESERVER command. For example:dsmsta setstorageserver myname=storagnt mypassword=fun4memyhladdress=agent.tucson.ibm.comservername=tsmsrver serverpassword=not4uhladdress=tsmsrver.tucson.ibm.com lladdress=1502

See “Set Installation Data for the Storage Agent: DSMSTASETSTORAGESERVER” on page 32 for details about the command parameters.

The command generates the following lines in the device configuration file forthe storage agent:

14 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 27: Tivoli Storage Manager Storage Agent

set staname storagntSET STAPASSWORD xxxxxxxSET STAHLADDRESS agent.tucson.ibm.comDEFINE SERVER tsmsrver serverpassword=xxxxxxxxxxxHLADDRESS=tsmsrver.tucson.ibm.com LLADDRESS=1502

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

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

SERVERNAME tsmsrver

See “The Storage Agent Options File” on page 34 and “The DeviceConfiguration File for the Storage Agent” on page 34 for details on these files.

Step 3. Tivoli Storage Manager ServerThe following provides the steps that you need to perform on the TSM server. Iffurther explanation is required, see Administrator’s Guide.1. For each client that you want to enable SAN data transfer, define the client’s

storage agent to the TSM server as if the storage agent is a server. You mustuse the same name and password that you set for the storage agent when youinstalled it on the client system. The DEFINE SERVER command must beissued from the TSM server (library manager or library client) that will managethe client’s data. For example:define server storagnt serverpassword=fun4mehladdress=agent.tucson.ibm.com lladdress=1500 validateprotocol=all

Note: The VALIDATEPROTOCOL parameter in the previous example isoptional. This parameter determines whether a cyclic redundancy checkshould be performed to validate data on all metadata transferredbetween the storage agent and the TSM server. See the Administrator’sReference for additional information about the DEFINE SERVERcommand. See the Administrator’s Guide for additional information aboutdata validation.

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

a. Define a shared SCSI or 3494 libraryb. Define paths to the library using the DEFINE PATH command on the serverc. Define drives that are associated with the libraryd. Define paths to the drives using the DEFINE PATH command on the servere. Define the device classf. Define the storage pool

Disk Device

Configure Enterprise Management and define a device class of DEVTYPE=FILEand SHARED=YES. TSM automatically defines a new FILE library and alsodefines drives corresponding to the mount limit for the FILE device class. TheFILE library name is the same as the device class name. Each drive uses thelibrary name with a numeric suffix. If the mount limit is changed, the numberof drives also changes.

Chapter 3. Installation and Configuration 15

Page 28: Tivoli Storage Manager Storage Agent

Note: As each session gets exclusive access to a file volume, the mount limitshould correspond to the number of expected concurrent backups.

3. Modify policy for the client so the storage agent, acting on behalf of the client,is associated with a storage pool that uses the drives on the SAN. The clientmust use a management class that has copy groups with a destination storagepool.The destination storage pool must be associated with the library. The librarymust be the one you have defined paths to the drives for the client. Forexample, do the following:a. Create a policy domain for clients that will use the SAN devices for direct

data transfer.b. Create a policy set in that domain.c. In the default management class for that policy set, modify the copy groups.

Set the destination storage pool to the storage pool associated with the SANdrives that you configured.

Note: If you decide not to use the default management class for the SANdrives, you will need to create a new management class. Clients thatwant to use the SAN drives need to use an include statement to bindtheir files to this new management class. See Backup-ArchiveInstallation and User’s Guide for details 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 Guide for details on changing policy for clients that can useSAN drives. For details about the commands, see Administrator’s Reference.

The following figure displays the results of completing the previous two steps.

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

16 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 29: Tivoli Storage Manager Storage Agent

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

Step 4. Client System

Note: If you are configuring a FILE Library, skip this step and proceed to Step 5.

Perform the following:

Obtain Tape Device InformationUse SMIT and issue the following commands to obtain information about tapedevices.v For IBM devices:

Select Devices -> Tape Drive -> List All Defined Tape Drives

TSM Client Workstation

Client - DATAOWNER

Storage Agent - STORAGNT

TSM Server - TSMSRVER

dsm.sys file

dsmsta.opt file

define server serverpassword=fun4me

hladdress=agent.tucson.ibm.com

lladdress=1500

register node bak2work

domain=sandomain

storagnt

dataowner

devconfig.out file

set staname storagnt

set stapassword xxxxxxx

set stahladdress agent.tucson.ibm.com

define server serverpassword=xxxxxxxx

hladdress=tsmsrver.tucson.ibm.com

lladdress=1502

tsmsrver

servername

devconfig

tsmsrver

devconfig.out

enablelanfree yes

lanfreecommmethod tcpip

lanfreetcpport 1500

tcpserveraddress .tucson.ibm.com

tcpport 1502

tsmsrver

Figure 5. Communications information. Results of Steps 2 and 3. The passwords are shownas ″xxxxxxx″ because they are encrypted in the file.

Chapter 3. Installation and Configuration 17

Page 30: Tivoli Storage Manager Storage Agent

v 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 paths from the storageagent to the drives that are available to the TSM server. Paths allow a client, bymeans of a storage agent, access to drives in a library. The requirements aredifferent depending on the device you are using.

Consider the following guidelines before you begin defining paths to your SANdrives:v Define paths to all drives. Problems can occur if you do not define paths from

the server to each drive in a library. For example, during backup operations, alldrives that have paths can be used by storage agents backing up data. Backupoperations will fail if you try to use other drives in a library that do not havedefined paths.When paths are defined for each drive in a library, backup operations wait untilthe next drive is available for the transfer of data.

Note: Backup operations can fail if no mount points are found to satisfy therequest. If this occurs, it is likely that all available drives do not have apath to the client.

v If you want to limit the number of drives available to a node, you can use theMAXNUMMP parameter on the REGISTER NODE or UPDATE NODEcommand. This will limit the number of drives that are available for the storageagent to use on behalf of the client.

v Review tape device names. For the same tape device, the device name as knownto the server will probably not match the device name as known to the storageagent.

Tape DevicesDefine paths on the server using the device names as seen by the storage agent oneach client system. See “Obtain Tape Device Information” on page 17.

Important: Be sure that the device names are what is seen by the storage agent oneach client system.

Note: The DEFINE PATH 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 path storagnt drive1 srctype=server desttype=drive library=sanlib1 device=/dev/mt1

See the Administrator’s Reference for your system platform for additional details onthe DEFINE PATH command.

Depending on the operating system of the TSM server, there may not be a quickway to confirm which device names on the storage agent correspond to devicenames on the TSM server without using a trial and error method. To confirmdevice names, you should work with one online drive at a time, and cycle throughthe storage agent device names until a successful backup can be run. On AIX, theserial number from ’lscfg -v -l rmt#’ is useful in finding the corresponding devicename on the TSM server.

18 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 31: Tivoli Storage Manager Storage Agent

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

Disk DevicesDefine paths on the server using the device names as seen by the storage agent oneach client system. For example, on the server side, the directory,d:\tsmdata\server1, is exported on the NFS server running on the TSM Servermachine.

On the storage agent, the directory is NFS mounted as /tsmdata/server1. Becausethe two directory names do not match, a path needs to be created for each filedrive in the library. The following is the command issued to create the path forthis scenario. In this example, file3 represents the destination file drive in the disklibrary with a name of disklib.define path storagnt file3 srctype=server desttype=drive library=disklib device=filedirectory="/tsmdata/server1"

For command information, see the Administrator’s Reference.

The following figure displays the results of completing steps three, four and five.

Step 6. Client SystemDuring this final step you will start the storage agent and verify the LAN-freeconfiguration.

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

When the storage agent starts, it determines if the TSM server is a library client orlibrary manager. If the TSM server is a library client, the storage agent usesinformation about the library manager from the library client in order to crossdefine itself to the library manager.

TSM Client Workstation

SAN

TSM Server - TSMSRVER

Storage Agent

device name: /dev/mt1

Tape Library Drive

define drive sanlib1 drive1

define path tsmsrver drive1 srctype=server

destype=drive library=sanlib1 device=/dev/mt6

define path storagnt drive1 srctype=server

destype=drive library=sanlib1 device=/dev/mt1

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

Chapter 3. Installation and Configuration 19

Page 32: Tivoli Storage Manager Storage Agent

Verify the LAN-free ConfigurationTo verify that you have configured your system correctly for LAN-free datamovement, perform the following procedure:1. Run a backup operation from the client. Verify that the backup is LAN-free by

using a TSM Administrative Command Line client to login to the TSM serverand storage agent to verify the proper sessions have been established. WhenLAN-free data movement is occurring, a QUERY SESSION on the storage agentshould show bytes received (displayed as Bytes Recvd) for the node increasingto the total amount of data being backed up. The QUERY SESSION on the TSMserver should show a very small amount of bytes received (metadata) for thesame node. If the node’s session exhibits this behavior, and you receive amessage stating that the backup has been successful, you have configured yoursystem correctly.

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

Note: If you retry the backup operation after the first failure, the clientattempts to use the LAN connection for data movement. The client willcontinue to use the LAN until the client is stopped and restarted.

a. The TSM server is running. If the TSM server is not running, the storageagent will not start.

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

c. The paths to the drives are correctly defined.d. All drives in a library have defined paths from the server.

Determining Whether the Data Movement was LAN-freeUse the following guidelines to help determine whether the data movement isusing the LAN-free environment:v Monitor the QUERY SESSION output against the node that is running the

LAN-free backup. Review the Bytes Sent and Bytes Received. You can performthis action by using a TSM administrative command-line client to login to theTSM server and storage agent to verify the proper sessions have beenestablished. When LAN-free data movement is occurring, a QUERY SESSION onthe storage agent should show bytes received (displayed as Bytes Recvd) for thenode increasing to the total amount of data being backed up. The QUERYSESSION on the TSM server should show a very small amount of bytes received(metadata) for the same node. If the node’s session exhibits this behavior, thedata movement is LAN-free.

v Issue either of the following QUERY ACTLOG commands on the server towhich the client 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 storageagent, the client is using LAN-free data transfer.

v Review the amount of data being transmitted from the client to the server. Theamount of data being transferred to the server should be considerably less thanthe amount of data being backed up. This is because the actual backup data ispassed over the SAN. From the operating system command-line, issue:netstat -D

20 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 33: Tivoli Storage Manager Storage Agent

Procedure 2 — External Library Environment with an ACSLS–ManagedLibrary

If you will be using a 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 the StorageTekACSLS and the Gresham EDT documentation for installation instructions. SeeFigure 4 on page 6 for an example of a storage agent in an ACSLS-managed libraryenvironment. Complete the following steps to configure your storage agentexternal library environment:

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 ofhardware and software. Ensure that your system configuration meets the hardwareand software requirements 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 Server

For a pictorial representation of what you will accomplish during the next twosteps, see Figure 7 on page 28.

Step 2. Client SystemThe procedures in this section describe installation and configuration of TSM client,API, storage agent, and Gresham EDT software.

Note: Gresham EDT or any other middleware that provides external libraryenablement is allowed. For installation information, see the Gresham orother middleware products documentation.

Install or Upgrade the Client and API Software:

1. Check that the client system meets the prerequisites for client software. See theUser’s Guide for the client. Install the client software and API if it is notalready installed on the system, or upgrade the software to the latest level asnecessary. The latest levels can be downloaded from the Tivoli Storage ManagerWeb site at http://www.tivoli.com/support/storage_mgr/tivolimain.html.

2. Modify the client options file (dsm.sys).For information about the dsm.opt and dsm.sys files, see Backup-ArchiveInstallation and User’s Guide.a. Edit the dsm.sys file to specify the communications method between the

TSM client and server. For example:COMMmethod TCPipTCPServeraddress tsmsrver.tucson.ibm.comTCPPport 1502

b. Edit the dsm.opt file to specify the servername of the dsm.sys stanza editedin step a. For example,servername tsmsrver

Chapter 3. Installation and Configuration 21

Page 34: Tivoli Storage Manager Storage Agent

c. Add the following options to the same dsm.sys stanza edited in step a.These options specify that the client will use SAN-attached devices; whenthe path is available, during backup, restore, archive, and retrieveprocessing.enablelanfree yes

LANFREECommmethod TCPIPLANFREETCPPORT 1500

orLANFREECommmethod SharedMemLANFREESHMPORT 1510

3. If your are using a TDP client, configure the API by performing the followingprocedure:a. Set up the environment variables. The TSM API uses unique environment

variables to locate files.v DSMI_CONFIG is the fully qualified name for the client user option file.v DSMI_DIR points to the path containing dsm.sys, dsmtca, and the

subdirectory en_US.v en_US subdirectory must contain dsmclientV3.cat.v 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=/usr/tivoli/tsm/client/api/bin/dsm.optexport DSMI_DIR=/usr/tivoli/tsm/client/api/binexport DSMI_LOG=/home/user_a/logdir

Note: The quickest method to set the environment variables is to add thesevariables to the user’s .profile file.

b. Edit the dsm.sys file to specify the communications method between theTSM API and server.1) If a dsm.sys file does not exist in the directory specified by DSMI_DIR,

create a symbolic link to the dsm.sys file in the TSM client installationdirectory. For example:ln -s /usr/tivoli/tsm/client/ba/bin/dsm.sys /usr/tivoli/tsm/client/api/bin/dsm.sys

2) Edit an existing stanza in the dsm.sys file or create a new stanza tospecify the options for connecting to the TSM server. For example:SErvername tsmsrverCOMMmethod TCPipTCPPort 1502TCPServeraddress tsmsrver.tucson.ibm.com

It is assumed that the dsm.sys file is controlled by the systemadministrator. The Tivoli Storage Manager server administrator shouldsupply the name and IP address of the Tivoli Storage Manager server, aswell as the node name and password.

c. Edit the dsm.opt file specified by the DSMI_CONFIG environment variableto specify the server name of the dsm.sys stanza edited in the previous step.For example:

servername tsmsrver

Install and Configure the Storage Agent:

22 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 35: Tivoli Storage Manager Storage Agent

Note: The Storage Agent should not be installed on the same machine as the TSMserver.

On the same system as the client, install the storage agent. The default installationdirectory is /usr/tivoli/tsm/StorageAgent/bin. The instructions in this section areshown using the Software Management and Installation Tool (SMIT). You can alsouse the Install and Update Software Manager (installm).

Note: Throughout this procedure, /dev/cd0 is used for CD-ROM. This may bedifferent in your environment. Loading the storage agent files can takeseveral minutes.

1. Record the following information. This information is required throughout theremainder of this procedure.v Storage agent: Name and password for the storage agent. Decide on a

name and password that will be used to initialize the storage agent and todefine the storage agent as a server to the TSM server. For example:– Storage Agent Name: storagnt– Storage Agent Password: fun4me– Storage Agent TCP/IP address: agent.tucson.ibm.com

v TSM server: Information about the TSM server that the storage agent willneed in order to communicate with the server. This is the same TSM serverwith which the client communicates. For example:– TSM Server Name: tsmsrver– TSM Password: not4u– TSM TCP/IP address: tsmsrver.tucson.ibm.com– TSM TCP/IP port: 1502– Tape Library Name: stk-lib

Notes:

a. You can verify the server information by issuing the QUERY STATUScommand from a TSM administrative command-line.

b. The ’Server Password Set’ displayed in the QUERY STATUS outputmust be equal to YES and for this example the password is set to not4u.To set the server password issue the SET SERVERPASSWORD commandfrom a TSM administrative command-line. For example:set serverpassword not4u

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 of your AIX operating system.Enter:

smit install_update &

For AIX 4.3, select:

Install and Update SoftwareInstall and Update from the LATEST Available Software

For AIX 5.1, select:

Chapter 3. Installation and Configuration 23

Page 36: Tivoli Storage Manager Storage Agent

Install SoftwareInstall Software

5. On the next window, select the device that you are using for the installation.You can enter the drive name in the window or click on List to access thedevice list.If you click on List, select the CD-ROM drive that you are using for theinstallation (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

software packages and continue at step 8.8. Select the components that you require. The following table lists the

component fileset file names.

Table 4. Package and Fileset Names for Installation. AIX 4.3.3 Platforms

Package Name Fileset Names Description

tivoli.tsm.StorageAgent.rte tivoli.tsm.StorageAgent.rte StorageAgent commonfunctions, 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 Onlinehelp

Table 5. Package and Fileset Names for Installation. AIX 5.1 Platforms

Package Name Fileset Names Description

tivoli.tsm.StorageAgent.rte tivoli.tsm.StorageAgent.rte StorageAgent commonfunctions, examples

tivoli.tsm.devices.aix5.rte64 tivoli.tsm.devices.aix5.rte64 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 Onlinehelp

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 fromSMIT.

14. Use the information that you collected in step 1 on page 23 to issue theDSMSTA SETSTORAGESERVER command. For example:dsmsta setstorageserver myname=storagnt mypassword=fun4memyhladdress=agent.tucson.ibm.comservername=tsmsrver serverpassword=not4uhladdress=tsmsrver.tucson.ibm.com lladdress=1502

24 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 37: Tivoli Storage Manager Storage Agent

Note: The TSM server, in this example TSMSRVER, must be running whenthe DSMSTA SETSTORAGESERVER command is issued.

See “Set Installation Data for the Storage Agent: DSMSTASETSTORAGESERVER” on page 32 for details about the command parameters.

The command generates the following lines in the device configuration file forthe storage agent:

SET STANAME storagntSET STAPASSWORD xxxxxxxSET STAHLADDRESS agent.tucson.ibm.comDEFINE SERVER tsmsrver serverpassword=not4uHLADDRESS=tsmsrver.tucson.ibm.com LLADDRESS=1502

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

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

SERVERNAME tsmsrver

See “The Storage Agent Options File” on page 34 and “The DeviceConfiguration File for the Storage Agent” on page 34 for details on these files.

15. Start this step only after the dsmsta command issued in the previous step hascompleted successfully. Use the library information that you collected in step 1on page 23 to add library definition information to the device configuration

file. For example:Incorporate the following library definition information:v Add the library named stk-libv Set the libtype to externalv Set lanfree to YESv Set obeymountretention to YES

Using the editor of your choice, open device configuration file and add thefollowing entry to the bottom of the file:

DEFINE LIBRARY stk-lib libtype=external lanfree=yes obeymountretention=yes

The resulting device configuration file would appear as:

SET STANAME storagntSET STAPASSWORD xxxxxxxSET STAHLADDRESS agent.tucson.ibm.comDEFINE SERVER tsmsrver serverpassword=xxxxxxxxxxxHLADDRESS=tsmsrver.tucson.ibm.com LLADDRESS=1502DEFINE LIBRARY stk-lib libtype=external lanfree=yes obeymountretention=yes

Save and close the file.16. Define a path from the storage agent to the external manager. Gresham

EDT-DistribuTape is the external library manager interfacing with the ACSLSlibrary software. The EDT executable is located in its default path/usr/lpp/dtelm/bin/elm For example:define path storagnt stk-lib srctype=server desttype=libraryexternalmanager=/usr/lpp/dtelm/bin/elm

Chapter 3. Installation and Configuration 25

Page 38: Tivoli Storage Manager Storage Agent

For additional information about the DEFINE PATH command, see the TivoliStorage Manager Administrator’s Reference.

Step 3.Tivoli Storage Manager ServerThe following provides the steps that you need to perform on the TSM server. Iffurther explanation is required, see Administrator’s Guide. On the server, performthe following:1. Install Gresham EDT or any other third-party software that provides external

library enablement. For installation information, see the Greshamdocumentation.

2. For each client that you want to enable SAN data transfer, define the client’sstorage agent to the TSM server as if the storage agent is a server. You mustuse the same name and password that you set for the storage agent when youinstalled it on the client system. The DEFINE SERVER command must beissued from the TSM server that will manage the client’s data. For example:define server storagnt serverpassword=fun4mehladdress=agent.tucson.ibm.com lladdress=1500 validateprotocol=all

Note: The VALIDATEPROTOCOL parameter in the previous example isoptional. This parameter determines whether a cyclic redundancy checkshould be performed to validate data on all metadata transferredbetween the storage agent and the TSM server. See the Administrator’sReference for additional information about the DEFINE SERVERcommand. See the Administrator’s Guide for additional information aboutdata validation.

3. Configure the SAN drives. This involves the following steps:a. Define a library type of EXTERNAL. For example:

define library stk-lib libtype=external lanfree=yes obeymountretention=yes

b. Define a path from the server to the external manager. GreshamEDT-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. For example:define path tsmsrver stk-lib srctype=server desttype=libraryexternalmanager=/usr/lpp/dtelm/bin/elm

In the previous example the path provided for the external manager isdependent upon the operating system where the TSM server resides. Forexample, an AIX TSM server external manager path is/usr/lpp/dtelm/bin/elm in contrast to a TSM Sun server external managerpath of /opt/OMIdtelm/bin/elm or a TSM Windows server externalmanager path of c:\program files\GES\EDT\bin\elm.exe. For additionalinformation about the DEFINE PATH command, see theAdministrator’sReference.

c. Define a path from the storage agent to the external manager. The DEFINEPATH command must be issued from the TSM server. GreshamEDT-DistribuTape is the external library manager interfacing with theACSLS library software. The EDT executable is located in its default path/opt/OMIdtelm/bin/elm. For example:define path storagnt stk-lib srctype=server desttype=libraryexternalmanager=/opt/OMIdtelm/bin/elm

For additional information about the DEFINE PATH command, see theTivoli Storage Manager Administrator’s Reference.

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

26 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 39: Tivoli Storage Manager Storage Agent

e. Define the storage pool4. Modify policy for the client so the storage agent, acting on behalf of the client,

is associated with a storage pool that users the drives on the SAN. The clientmust use a management class that has copy groups with a destination storagepool.The destination storage pool must be associated with the library. The librarymust be the one that you have defined paths to its drives for the client. Forexample, do the following:a. Create a policy domain for clients that will use the SAN devices for direct

data transfer.b. Create a policy set in that domain.c. In the default management class for that policy set, modify the copy groups.

Set the destination storage pool to the storage pool associated with the SANdrives that you configured.

Note: If you decide not to use the default management class for theexternal library, you will need to create a new management class.Clients that want to use the SAN attached library need to use aninclude statement to bind their files to this new management class.See Backup-Archive Installation and User’s Guide 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 Guide for details on changing policy for clients that can useSAN drives. For additional command information, see Administrator’s Reference.

The following figure displays the results of completing the previous two steps.

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

Chapter 3. Installation and Configuration 27

Page 40: Tivoli Storage Manager Storage Agent

Configuring Devices for the Storage Agent to Access

Step 4. Client SystemDuring this step you will start the storage agent and verify the LAN-freeconfiguration.

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

Verify the LAN-free ConfigurationTo verify that you have configured your system correctly for LAN-free datamovement, perform the following procedure:1. Run a backup operation from the client. Verify that the backup is LAN-free by

using a TSM Administrative Command Line client to login to the TSM serverand storage agent to verify the proper sessions have been established. When

TSM Client Workstation

Client - DATAOWNER

Storage Agent - STORAGNT

TSM Server - TSMSRVER

dsm.sys file

dsmsta.opt file

define server serverpassword=fun4me

hladdress=agent.tucson.ibm.com

lladdress=1500

register node bak2work

domain=sandomain

storagnt

dataowner

devconfig.out file

set staname storagnt

set stapassword xxxxxxx

set stahladdress agent.tucson.ibm.com

define server serverpassword=xxxxxxxx

hladdress=tsmsrver.tucson.ibm.com

lladdress=1502

tsmsrver

servername

devconfig

tsmsrver

devconfig.out

enablelanfree yes

lanfreecommmethod tcpip

lanfreetcpport 1500

tcpserveraddress .tucson.ibm.com

tcpport 1502

tsmsrver

Figure 7. Communications information. Results of Steps 2 and 3. The passwords are shownas ″xxxxxxx″ because they are encrypted in the file.

28 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 41: Tivoli Storage Manager Storage Agent

LAN-free data movement is occurring, a QUERY SESSION on the storage agentshould show bytes received (displayed as Bytes Recvd) for the node increasingto the total amount of data being backed up. The QUERY SESSION on the TSMserver should show a very small amount of bytes received (metadata) for thesame node. If the node’s session exhibits this behavior, and you receive amessage stating that the backup has been successful, you have configured yoursystem correctly.

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

Note: If you retry the backup operation after the first failure, the clientattempts to use the LAN connection for data movement. The client willcontinue to use the LAN until the client is stopped and restarted.

a. The TSM server is running. If the TSM server is not running, the storageagent will not start.

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

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

Determining Whether the Data Movement was LAN-free: Use the followingguidelines to help determine whether the data movement is using the LAN-freeenvironment:v Monitor the QUERY SESSION output against the node that is running the

LAN-free backup. Review the Bytes Sent and Bytes Received. You can performthis action by using a TSM administrative command-line client to login to theTSM server and storage agent to verify the proper sessions have beenestablished. When LAN-free data movement is occurring, a QUERY SESSION onthe storage agent should show bytes received (displayed as Bytes Recvd) for thenode increasing to the total amount of data being backed up. The QUERYSESSION on the TSM server should show a very small amount of bytes received(metadata) for the same node. If the node’s session exhibits this behavior, thedata movement is LAN-free.

v Issue either of the following QUERY ACTLOG commands on the server towhich the client 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 storageagent, the client is using LAN-free data transfer.

v Review the amount of data being transmitted from the client to the server. Theamount of data being transferred to the server should be considerably less thanthe amount of data being backed up. This is because the actual backup data ispassed over the SAN. From the command, issue:netstat -D

Chapter 3. Installation and Configuration 29

Page 42: Tivoli Storage Manager Storage Agent

30 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 43: Tivoli Storage Manager Storage Agent

Appendix A. Administration and Configuration Reference

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 thefollowing command:dsmsta

Stop the storage agent by typing the following command at the command lineprompt:halt

Obtaining Tape Device Information on the Client SystemTo complete the setup of the storage agent, you must obtain the device names fromthe client system. You can get this information by using SMITTY and issuing thefollowing commands:v For IBM devices:

Select Devices ->Tape Drive -> List All Defined Tape Drives

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

Library/Medium Changer -> List All Defined devices

© Copyright IBM Corp. 2000, 2002 31

Page 44: Tivoli Storage Manager Storage Agent

Set Installation Data for the Storage Agent: DSMSTASETSTORAGESERVER

PurposeUse this utility on the client system where the storage agent has been installed. Theutility adds communication information to the device configuration file and thedsmsta.opt file for the storage agent. See “Install and Configure the Storage Agent”on page 12 for more information on when to use this command.

This utility does not remove any previous entries in the files. It appendsinformation to the existing files. The option devconfig, which sets a name for thedevice configuration file, must exist in the dsmsta.opt file for the command towork. See the example for details on the information 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 SETSTANAME command that is inserted into the device configuration file.

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

MYPAsswordSpecifies the password of the storage agent. This value is encrypted and usedin the SET STAPASSWORD command that is inserted into the deviceconfiguration file.

Note: You must use the same password when you define the storage agent asa server to the TSM server.

MYHLAddressSpecifies the TCP/IP address of the storage agent. This value is used internallyin the SET STAHLAddress command which is inserted into the deviceconfiguration file.

32 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 45: Tivoli Storage Manager Storage Agent

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

SERVERPAsswordSpecifies the password of the server. This value is encrypted and appears inthe SERVERPASSWORD field of the DEFINE SERVER command that isinserted into the device configuration file.

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

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

ExamplesIssue the DSMSTA SETSTORAGESERVER command with the followinginformation:v Storage agent

Name: storagntPassword: fun4meTCP/IP address: agent.tucson.ibm.com

v TSM serverName: tsmsrverPassword: not4uTCP/IP address: tsmsrver.tucson.ibm.comTCP/IP port: 1502

The command is:dsmsta setstorageserver myname=storagnt mypassword=fun4memyhladdress=agent.tucson.ibm.comservername=tsmsrver serverpassword=not4uhladdress=tsmsrver.tucson.ibm.com lladdress=1502

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

SET STANAME storagntSET STAPASSWORD xxxxxxxSET STAHLADDRESS agent.tucson.ibm.comDEFINE SERVER tsmsrver serverpassword=xxxxxxxxHLADDRESS=tsmsrver.tucson.ibm.com LLADDRESS=1502

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

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

SERVERNAME tsmsrver

Appendix A. Administration and Configuration Reference 33

Page 46: Tivoli Storage Manager Storage Agent

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

Normally you do not need to make any changes to the options file. If your TSMserver changes, you may need to make changes to this file. The required optionsare:

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

DEVCONFig file_nameThe name of the device configuration file for the storage agent. A typicalname for the 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 aresource on the server. The default value is 10 minutes. The minimumvalue is 1 minute. This parameter is optional.

STAMaxpooledsessions numberThe number of sessions that the storage agent keeps open to the TSMserver. The default value is 25. Possible values are 0 to 150. If the storageagent needs more sessions than specified, additional sessions areconsidered temporary and close when the 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 thestorage agent itself and information about the TSM server with which the storageagent communicates. The file is typically named devconfig and is with the storageagent program at this location: /usr/tivoli/tsm/StorageAgent/bin . The DSMSTASETSTORAGESERVER command normally generates the contents of the file. If youhave changes to the TSM server or if a service representative directs you, you mayneed to make changes to the information. You can use the DSMSTASETSTORAGESERVER command to add 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 seconddevice configuration file example.

SET STANAME storagntSET STAPASSWORD fun4meSET STAHLADDRESS agent.tucson.ibm.comDEFINE SERVER tsmsrver serverpassword=not4uHLADDRESS=tsmsrver.tucson.ibm.com LLADDRESS=1502

In this example, STORAGNT is the name of the storage agent and TSMSRVER isthe name of the TSM server.

34 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 47: Tivoli Storage Manager Storage Agent

Typical contents of the device configuration file for an ACSLS-managed libraryenvironment are as follows:

SET STANAME storagntSET STAPASSWORD fun4meSET STAHLADDRESS agent.tucson.ibm.comDEFINE SERVER tsmsrver serverpassword=not4uHLADDRESS=tsmsrver.tucson.ibm.com LLADDRESS=1502DEFINE LIBRARY stk-lib libtype=external lanfree=yes obeymountretention=no

In this example, STORAGNT is the name of the storage agent, TSMSRVER is thename of the TSM server, and STK-LIB is the name of the ACSLS-managed tapelibrary.

The following describes the contents of the file:

SET STANAMESets the name of the storage agent. The name must be the same as thename that was used to define the storage agent as a server to the TSMserver.

SET STAPASSWORDSets the password of the storage agent. The password must be the same asthe password that was used when defining the storage agent as a server tothe TSM server. 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 agentcommunicates.

DEFINE LIBRARYThe definition of an ACSLS-managed library to the TSM server.

Appendix A. Administration and Configuration Reference 35

Page 48: Tivoli Storage Manager Storage Agent

36 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 49: Tivoli Storage Manager Storage Agent

Appendix B. Legacy ACSLS Data Migration and Coexistence

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

If your environment consists of TSM storage pools associated with an ACSLSlibrary type and a device class containing the GENERICTAPE device type, youneed to consider migration and coexistence issues for existing data. To takeadvantage of LAN-free data transfer, the data must be migrated to a storage poolassociated with an EXTERNAL library type and a device class containing theECARTRIDGE device type. Data migration is recommended over coexistence.

Data MigrationData migration of ACSLS to EXTERNAL is recommended. Migrate the existingdata from existing (old) storage pools to new storage pools associated with theappropriate policy, device class, and library definitions. Migration of data alsoallows the entire environment to be LAN-free, providing better performance andbetter utilization of tape drives and media.

Figure 8 displays the normal migration path from an old storage pool containingthe data associated with the ACSLS library type to a new storage pool associatedwith an EXTERNAL library type and an ECARTRIDGE device class.

Figure 8. Legacy ACSLS Data Migration

© Copyright IBM Corp. 2000, 2002 37

Page 50: Tivoli Storage Manager Storage Agent

Two methods to migrate data are:v Use the Tivoli Storage Manager server MOVE DATA command. This method

allows the legacy ACSLS data to move to a new storage pool without movingany expired files in the aggregates. For more information, see the ManagingStorage Pools and Volumes section of the Administrator’s Guide.

v Use the Tivoli Storage Manager server storage pool reclamation function. Thismethod works by reclaiming the active files from the legacy ACSLS storagepools. Reclamation processing, however, is very resource intensive and shouldbe performed during periods of low resource utilization. For more information,see Reclaiming Space in Sequential Access Storage Pools section of theAdministrator’s Guide.

Data CoexistenceStorage pool volumes created using the ACSLS library type cannot be accessedusing the EXTERNAL library type, but the two library types can coexist on thesame STK library. Even though ACSLS and EXTERNAL data coexistence is notrecommended, coexistence might provide a temporary solution during themigration for certain environments, such as, large amounts of legacy ACSLS dataand very small migration time-windows. Allowing ACSLS and EXTERNAL librarytypes to coexist requires that tape drives within the library be partitioned. TheACSLS library type requires at least one dedicated tape drive. If you choose tohave data coexist, either temporarily or long-term, be sure to implement thefollowing in your environment set-up:v Leave at least one dedicated drive with its original configuration (that is, leave

drive mapping intact) using the same device driver as when the data using theACSLS library type was originally written.

v 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.

38 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 51: Tivoli Storage Manager Storage Agent

Appendix C. Notices

This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user’s responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. 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 IBMIntellectual Property 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 othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

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

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

© Copyright IBM Corp. 2000, 2002 39

Page 52: Tivoli Storage Manager Storage Agent

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, 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 in some cases, payment of a fee.

The licensed program described in this information and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.

TrademarksThe following terms are trademarks of the International Business MachinesCorporation in the United States, other countries, or both:

AIXIBMIBMLink

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

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

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

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

40 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 53: Tivoli Storage Manager Storage Agent

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 andother countries.

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

Appendix C. Notices 41

Page 54: Tivoli Storage Manager Storage Agent

42 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 55: Tivoli Storage Manager Storage Agent

Glossary

AACSLS. Automated cartridge system library software.

application client. One of the Tivoli Data Protectionfor application programs installed on a system. TheTivoli Storage Manager server provides backup servicesto these clients.

archive. To copy one or more files to a storage poolfor long-term storage. Archived files can includedescriptive information and can be retrieved by archivedate, by file name, or by description. Contrast withretrieve.

automated cartridge system library software(ACSLS). A library-enablement application fromStorageTek. ACSLS functions as the central serviceprovider for library operations.

Bback up. To copy information to another location toensure against loss of data. In Tivoli Storage Manager,you can back up user files, the Tivoli Storage Managerdatabase, and storage pools. Contrast with restore.

backup-archive client. A program that runs on aworkstation or file server and provides a means forusers to back up, archive, restore, and retrieve files.

Cclient. A program running on a PC, workstation, fileserver, LAN server, or mainframe that requests servicesof another program, called the server. The followingtypes of clients can obtain services from a TivoliStorage Manager server: administrative client,application client, API client, backup-archive client, andHSM client (also known as space manager client).

client node. A file server or workstation on which thebackup-archive client program has been installed, andwhich has been registered to the server.

client options file. A file that a client can change,containing a set of processing options that identify theserver, communication method, and options for backup,archive, hierarchical storage management, andscheduling. Also called the dsm.opt file.

Ddevice class. A named set of characteristics applied toa group of storage devices. Each device class has aunique name and represents a device type of disk, file,optical disk, or tape.

device configuration file. (1) On a Tivoli StorageManager storage agent, a file that contains the nameand password of the storage agent, and the DEFINESERVER command for the Tivoli Storage Managerserver that is managing the SAN-attached libraries anddrives. (2) On a Tivoli Storage Manager server, a filethat contains information about defined device classes,and, on some Tivoli Storage Manager servers, definedlibraries and drives.

device driver. A collection of subroutines that controlthe interface between I/O device adapters and theprocessor.

dsm.opt file. See client options file.

dsmserv.opt. See server options file.

dsmsta.opt. See storage agent options file.

Eexternal library. A type of enablement provided byTivoli Storage Manager to allow LAN-free data

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

This glossary may include terms and definitions from:

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

v The Information Technology Vocabulary, developed by Subcommittee 1, Joint Technical Committee 1, of theInternational Organization for Standardization and the International Electrotechnical Commission (ISO/IECJTC2/SC1).

© Copyright IBM Corp. 2000, 2002 43

Page 56: Tivoli Storage Manager Storage Agent

movement for ACSLS-managed StorageTek libraries. Toactivate this support the Tivoli Storage Manager librarytype must be EXTERNAL.

FFILE device type. A device type that specifies the useof sequential access files on disk storage as volumes.

LLAN. Local area network.

LAN-free data transfer. The movement of client datadirectly between a client and a storage device over aSAN, rather than over the LAN.

library. (1) A repository for demountable recordedmedia, such as magnetic tapes. (2) For Tivoli StorageManager, a collection of one or more drives, andpossibly robotic devices (depending on the librarytype), which can be used to access storage volumes.

library manager. A Tivoli Storage Manager server thatcontrols device operations when multiple Tivoli StorageManager servers share a storage device. The deviceoperations include mount, dismount, volumeownership, and library inventory.

Mmanagement class. A policy object that users can bindto each file to specify how the server manages the file.The management class can contain a backup copygroup, an archive copy group, and space managementattributes. The copy groups determine how the servermanages backup versions or archive copies of the file.The space management attributes determine whetherthe file is eligible to be migrated by the space managerclient to server storage, and under what conditions thefile is migrated.

Nnode. A workstation or file server that is registeredwith a Tivoli Storage Manager server to receive itsservices. See also client node.

Ppolicy domain. A policy object that contains policysets, management classes, and copy groups that areused by a group of client nodes. See policy set andmanagement class.

policy set. A policy object that contains a group ofmanagement classes that exist for a policy domain.Several policy sets can exist within a policy domain but

only one policy set is active at one time. See policydomain and management class.

Rreclamation. A process of consolidating the remainingdata from many sequential access volumes onto fewernew sequential access volumes.

restore. To copy information from its backup locationto the active storage location for use. In Tivoli StorageManager, you can restore the server database, storagepools, storage pool volumes, and users’ backed-up files.The backup version in the storage pool is not affectedby the restore operation. Contrast with backup.

SSAN. Storage area network.

SCSI. Small computer system interface.

server. The program that provides backup, archive,space management, and administrative services toclients. The server program must be at the necessarylevel to provide all of these services.

server options file. A file that contains settings thatcontrol various server operations. These settings, oroptions, affect such things as communications, devices,and performance.

server storage. The primary and copy storage poolsused by the server to store users’ files: backup versions,archive copies, and files migrated from Tivoli SpaceManager client nodes (space-managed files). See storagepool.

shared library. A library device that is shared amongmultiple Tivoli Storage Manager servers.

storage agent. A program that enables Tivoli StorageManager to back up and restore client data directly toand from SAN-attached storage.

storage agent options file. A file that specifies optionsfor the storage agent. This includes the name of theTivoli Storage Manager server with which the storageagent communicates, the number of sessions that canbe kept open to the server, and the name of the deviceconfiguration file. Also called the dsmsta.opt file.

storage pool. A named set of storage volumes that isthe destination that the Tivoli Storage Manager serveruses to store client data. The client data consists ofbackup versions, archive copies, and migrated files. Youcan back up a primary storage pool to a copy storagepool.

44 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 57: Tivoli Storage Manager Storage Agent

Ttape library. A term used to refer to a collection ofdrives and tape cartridges. The tape library may be anautomated device that performs tape cartridge mountsand demounts without operator intervention.

Glossary 45

Page 58: Tivoli Storage Manager Storage Agent

46 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 59: Tivoli Storage Manager Storage Agent

Index

AACSLS support 5, 21, 37

Ddata movement, SAN

prerequisites 7tasks 9

device configuration file 34disk device

SANergy 2.2 11server install 15

dsm.opt file 11, 22DSMSTA SETSTORAGESERVER 14, 24dsmsta.opt 15, 25, 34

Eenablelanfree option 11, 22external library support 5, 21, 37

FFILE library

configuration considerations 4disk devices 15

Hhow to determine LAN-free data

movement 20, 29

LLAN-free data movement

enabling, dsm.opt 11, 22guidelines for determining 20, 29

library client 3library manager 3limit the SAN drives 18

MManaged System for SAN

description 1FILE library 4planning configurations 3policy considerations 16, 27SANergy Metadata Controller 4

Nnetwork requirements 10, 21no-query restore 2

Oobtaining tape device information 17option, enablelanfree 11, 22options file

client 11, 22storage agent 15, 25, 34

Ppath

defining 18disk devices 19tape devices 18

policy for Managed System for SAN 16,27

SSAN data movement

prerequisites 7tasks 9

storage agentcomponent configuration 7configuring device access 17device configuration file 34installing 12, 23options file 34starting 19, 28usage requirements 7verify configuration 20, 28

Ttape device information, obtaining 17TSM API

install 11, 22upgrade 11, 22

© Copyright IBM Corp. 2000, 2002 47

Page 60: Tivoli Storage Manager Storage Agent

48 Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent User’s Guide

Page 61: Tivoli Storage Manager Storage Agent
Page 62: Tivoli Storage Manager Storage Agent

Program Number: 5698-ISE

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

GC32-0771-00