Tivoli Storage Manager Storage Agent

Tivoli Storage Manager for AIX
Managed System for SAN Storage Agent Users Guide

V ersion 5 Release 1
GC32-0771-00
Tivoli Storage Manager for AIX
Managed System for SAN Storage Agent Users Guide

V ersion 5 Release 1
GC32-0771-00
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 any subsequent 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 any comments about this book or any other Tivoli Storage Manager documentation, please see Contacting Customer Support 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 Contract with IBM Corp.
Contents
About This Book . . . . . . . . . . . v
Where to Look for Information . . . . . . Contacting Customer Support . . . . . Internet . . . . . . . . . . . . . Tivoli Storage Manager Publications . . . Related IBM Hardware Products Publications IBM Redbooks . . . . . . . . . . . Translations . . . . . . . . . . . . . v . v . . vi . . vi viii . viii . viii . . Configuring Devices for the Storage Agent to Access Step 4. Client System . . . . . . . . . . Step 5. Server. . . . . . . . . . . . . Step 6. Client System . . . . . . . . . . . Start the Storage Agent . . . . . . . . . Verify the LAN-free Configuration. . . . . . Procedure 2 External Library Environment with an ACSLSManaged Library. . . . . . . . . Step 1. Network . . . . . . . . . . . . Establishing Communications among Client, Storage Agent, and Server . . . . . . . . Configuring Devices for the Storage Agent to Access . . . . . . . . . . . . . . . Step 4. Client System . . . . . . . . . . 17 17 18 19 19 20 21 21 21 28 28
Summary of Changes for Tivoli Storage Manager . . . . . . . . . . . . . . ix

Technical Changes for Version 5 Release 1March 2002 . . . . . . . . . . . . . . . . . ix
Chapter 1. Storage Agent Overview . . . 1

LAN-free Client Data Backup Scenario. . . . . Dual-session No-Query Restore for LAN-free Path. . 2 . 2
Appendix A. Administration and Configuration Reference . . . . . . . 31

Starting and Stopping the Storage Agent . . . . Obtaining Tape Device Information on the Client System . . . . . . . . . . . . . . . . Set Installation Data for the Storage Agent: DSMSTA SETSTORAGESERVER. . . . . . . . . . . The Storage Agent Options File. . . . . . . . The Device Configuration File for the Storage Agent 31 31 32 34 34
Chapter 2. Planning. . . . . . . . . . 3
Types of Configurations . . . . . . . . Sharing Tape Storage using TSM Library Manager/Client . . . . . . . . . . Sharing Disk Storage using Tivoli SANergy . External Library Sharing ACSLS-Managed Libraries . . . . . . . . . . . . . System Requirements . . . . . . . . . . . . . . . 3 . 3 . 4 . 5 . 7
Appendix B. Legacy ACSLS Data Migration and Coexistence . . . . . . 37

Data Migration . Data Coexistence . . . . . . . . . . . . . . . . . . . . . . . 37 . 38
Chapter 3. Installation and Configuration 9

Summary of Tasks for Procedure 1 . . . . . . . 9 Summary of Tasks for Procedure 2 . . . . . . 10 Procedure 1 Tape and File Sharing with SCSI and 349X Tape and File Devices . . . . . . . . . 10 Step 1. Network . . . . . . . . . . . . . 10 Establishing Communications among Client, Storage Agent, and Server . . . . . . . . . . . . 11 Step 2. Client System . . . . . . . . . . 11 Step 3. Tivoli Storage Manager Server . . . . 15
Appendix C. Notices . . . . . . . . . 39
Trademarks . . . . . . . . . . . . . . 40
Glossary . . . . . . . . . . . . . . 43 Index . . . . . . . . . . . . . . . 47
Copyright IBM Corp. 2000, 2002
iii
iv
Tivoli Storage Manager for AIX: Managed System for SAN Storage Agent Users Guide
About This Book

This users guide is intended for anyone who will be using the Tivoli Managed System for SAN product, commonly referred to as the storage agent. This document provides an overview of LAN-free data transfer. It also provides detailed 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 additional publications during configuration of the storage agent environment. Refer to the listing of Tivoli Storage Manager Publications in Where to Look for Information. Note: Tivoli Managed System for SAN is only supported in US English. At the time of publishing this document no other language support was available. For information about Tivoli Storage Manager, see http://www.tivoli.com/support/storage_mgr/tivolimain.html.
Where to Look for Information

The following describes the service that IBM provides for Tivoli Managed System for SAN Storage Agent and tells you where to look for more information about Tivoli Storage Manager products.
Contacting Customer Support

For support for this or any Tivoli product, you can contact Tivoli Customer Support 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 at http://www2.ibmlink.ibm.com. v Submit a problem management record (PMR) electronically at http://www.tivoli.com/support. See Reporting a Problem on page vi for details. v Send e-mail to support@tivoli.com. Customers in the United States can also call 1-800-TIVOLI8 (1-800-848-6548). For product numbers 5697-TS9, 5697-DRS or 5697-DPM call 1-800-237-5511. International customers should consult the Web site for customer support telephone numbers. You can also review the Customer Support Handbook, which is available on our Web site at http://www.tivoli.com/support/handbook/. When you contact Tivoli Customer Support, be prepared to provide identification information for your company so that support personnel can readily assist you. Company identification information may also be needed to access various online services available on the Web site.
The support Web site offers extensive information, including a guide to support services (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 in both PDF and HTML formats. Translated documents are also available for some product releases. You can order documentation by e-mail at swdist@tivoli.com. Please provide the publication number, part number, or order number of the desired document. Alternatively, you can provide the document title, version number, and date of publication. We are very interested in hearing about your experience with Tivoli products and documentation. We also welcome your suggestions for improvements. If you have comments or suggestions about our documentation, please contact us in one of the following ways: v Send e-mail to pubs@tivoli.com. v Complete our customer feedback survey at http://www.tivoli.com/support/feedback/.
Reporting a Problem
Please 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 STATUS command at the TSM command line. v The Tivoli Storage Manager client version, release, modification, and service level number. You can get this information by entering dsmc at the command line. v The communication protocol (for example, TCP/IP), version, and release number you are using. v The activity you were doing when the problem occurred, listing the steps you followed before the problem occurred. v The exact text of any error messages.
Internet
You 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, listserv@marist.edu, is implemented by a third party. IBM supports this newsgroup on a best-effort basis only.
Tivoli Storage Manager Publications

The following table lists Tivoli Storage Manager server publications.
Publication Title Tivoli Storage Management Products License Information Tivoli Storage Manager Messages Tivoli Storage Manager for AIX Administrators Guide Tivoli Storage Manager for AIX Administrators Reference Tivoli Storage Manager for AIX Quick Start Order Number GH09-4572 GC32-0767 GC32-0768 GC32-0769 GC32-0770
vi
The following table lists Tivoli Storage Manager storage agent publications.
Publication Title Order Number
Tivoli Storage Manager for AIX Managed System for SAN Storage Agent GC32-0771 Users Guide Tivoli Storage Manager for HP-UX Managed System for SAN Storage Agent Users Guide GC32-0727
Tivoli Storage Manager for Sun Solaris Managed System for SAN Storage GC32-0781 Agent Users Guide Tivoli Storage Manager for Windows Managed System for SAN Storage Agent Users Guide GC32-0785
The following table lists the Tivoli Storage Manager client publications.
Publication Title Tivoli Space Manager for UNIX: Using the Hierarchical Storage Management Clients Tivoli Storage Manager for Macintosh: Backup-Archive Installation and Users Guide Tivoli Storage Manager for NetWare: Backup-Archive Installation and Users Guide Order Number GC32-0794 GC32-0787 GC32-0786
Tivoli Storage Manager for UNIX: Backup-Archive Installation and Users GC32-0789 Guide Tivoli Storage Manager for Windows: Backup-Archive Installation and Users Guide Tivoli Storage Manager Trace Facility Guide Tivoli Storage Manager Using the Application Program Interface GC32-0788 GC32-0792 GC32-0793
The following table lists Tivoli Data Protection publications.

Publication Title Tivoli Data Protection for EMC Symmetrix for R/3 Installation and Users Guide Tivoli Data Protection for IBM ESS for Oracle Databases DB2 UDB Installation and Users Guide Tivoli Data Protection for IBM ESS for R/3 Installation and Users Guide Tivoli Data Protection for Informix Installation and Users Guide Tivoli Data Protection for Lotus Domino for UNIX Installation and Users Guide Tivoli Data Protection for Lotus Domino for Windows Installation Tivoli Data Protection for Lotus Domino, S/390 Edition Licensed Program Specifications Tivoli Data Protection for Lotus Notes on AIX Installation and Users Guide Tivoli Data Protection for Lotus Notes on Windows NT Installation and Users Guide Order Number SC33-6386 SH26-4125 SC33-6387 SH26-4095 SH26-4088 GC26-7320 GC26-7305 SH26-4067 SH26-4065
Tivoli Data Protection for Microsoft Exchange Server Installation and Users Guide SH26-4110 Tivoli Data Protection for Microsoft SQL Server Installation and Users Guide Tivoli Data Protection for Oracle for UNIX Installation and Users Guide Tivoli Data Protection for Oracle for Windows Installation and Users Guide SH26-4111 SH26-4112 SH26-4113
About This Book
vii
Publication Title Tivoli Data Protection for R/3 Installation and Users Guide for Oracle Tivoli Data Protection for R/3 Installation and Users Guide for DB2 UDB Tivoli Data Protection for R/3 Installation and Users Guide Tivoli Data Protection for WebSphere Application Server Installation and Users Guide Tivoli Data Protection for Workgroups for NetWare Users Guide
Order Number SC33-6340 SC33-6341 SC33-6389 SC33-6399 GC32-0444
Related IBM Hardware Products Publications

The following table lists related IBM hardware products publications.
Title IBM Magstar 3494 Tape Library Introduction and Planning Guide IBM 3490E Model E01 and E11 Users Guide IBM Magstar MP 3570 Tape Subsystem Operators Guide IBM SCSI Tape Drive, Medium Changer, and Library Device Drivers: Installation and Users Guide IBM TotalStorage Enterprise Tape System 3590 Operator Guide IBM Magstar 3494 Tape Library Dataserver Operator Guide Order Number GA32-0279 GA32-0298 GA32-0345 GC35-0154 GA32-0330 GA32-0280
IBM Redbooks
The International Technical Support Center (ITSC) publishes redbooks, which are books on specialized topics, such as, Using TSM to Back Up Databases. You can order publications through your IBM representative or the IBM branch office serving your locality. You can also search for and order books of interest to you by visiting the IBM Redbooks home page on the World Wide Web at this address: http://www.redbooks.ibm.com.
Translations
Tivoli Storage Agent is supported in only US English. Other language support is not available at this time.
viii
Summary of Changes for Tivoli Storage Manager

This section summarizes changes made to the Storage Agent product and to this publication.
Technical Changes for Version 5 Release 1March 2002

The 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 UPDATE PATH 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 PATH command. v Drive mapping is no longer supported and has been replaced by the DEFINE PATH command. Data Validation with Cyclic Redundancy Checking Tivoli Storage Manager provides the option of specifying whether a cyclic redundancy check (CRC) is performed during a client session with the server, storage agent, or for storage pools. The server or storage agent validates the data by using a cyclic redundancy check which can help identify data corruption. Data validation can be enabled for one or all of the following: v Tivoli Storage Manager storage agents at Version 5.1 v Tivoli Storage Manager client nodes at Version 5.1 v Storage Pools See the DEFINE SERVER, UPDATE SERVER, DEFINE STGPOOL, UPDATE STGPOOL, DEFINE NODE and UPDATE NODE commands in the TSM Administrators Reference.
ix
Chapter 1. Storage Agent Overview

Managed System for SAN is a feature of Tivoli Storage Manager (TSM) that enables LAN-free TSM client data movement. The TSM client data moves directly to and from a storage device attached to a Storage Area Network (SAN), thereby off-loading the data movement from the LAN and from the Tivoli Storage Manager server. The storage agent is installed on the client machine and shares storage resources with the Tivoli Storage Manager server. The storage agent can write directly 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 data that the client has stored. TSM continues to use a LAN connection to exchange control information, such as policy information and data about the objects that are backed up. Using the SAN for client data movement decreases the load on the TSM server and allows the server to support a greater number of simultaneous client connections. See Figure 1.
Client Storage Agent installed
Library Control Client Metadata LAN
Storage Manager Server
Client Data
SAN
Library Control
File Library
Tape Library
Figure 1. SAN Data Movement. Solid lines indicate data movement. Broken lines indicate movement of control information and metadata.
To use Managed System for SAN you must install a storage agent on the client system. The storage agent communicates with the server to obtain and store database information and to coordinate device and volume access. The server determines if the client is requesting access to storage for which the client has a SAN path defined. If a SAN path is defined, the client (by means of the storage
agent) transfers data on that path. If a failure occurs on the SAN path, failover occurs and the client uses its LAN connection to the TSM server and moves the client 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 TSM to share ACSLS-managed libraries. In this environment the device sharing capability is provided by third-party software, such as Gresham Extended Data Technology DistribuTAPE (EDT-DistribuTAPE) a middleware software program that takes advantage of TSMs external library interface to allow tape drives in ACSLS-managed libraries to be shared among TSM servers. For additional information about these configurations, see Types of Configurations on page 3.
LAN-free Client Data Backup Scenario

The following outlines a typical backup scenario for a TSM client that uses SAN data 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 pool that uses a device on the SAN. That device must also have a defined path between 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 a volume 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 Path

When performing a No-Query restore the TSM server builds a list of files to restore and sends data to the client while continuing to build the list. This type of restore is more efficient especially in a LAN-free environment, and allows the restore to be restarted if interrupted. Two sessions are used for the restore when data for the restore resides on devices with a LAN-free path and devices with a LAN-only path. One session restores data from the server with a LAN-only path. The other session uses the storage agent to restore data over the LAN-free path. This works only with clients at the 4.2 level or above.
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 system setup and into production. As part of your planning, you need to identify the following: v Which configuration to implement v Devices to be used for LAN-free data movement v Clients to use LAN-free data movement v For tape libraries (except ACSLS-managed StorageTek tape libraries), which servers, library manager or library client manage which clients data.
Types of Configurations
There are different types of configurations that take advantage of what can be accomplished using a storage agent in a LAN-free environment. Your environment is dependent upon the type of storage device you will be using for LAN-free data storage. The following sections cover descriptions and planning considerations for several 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/Client

When TSM servers share a SCSI tape or 349X storage device using a library manager and library clients, one server, the library manager, owns and controls the tape library device. The library manager operations include checking volumes into and out of the library, labeling volumes, mounting and dismounting volumes, auditing volumes, and creating an inventory of library contents, see Figure 2 on page 4. The library manager also manages the storage hierarchy and performs such server functions as storage pool migrations, reclamation, collocation, and backup and restore of storage pools and the database. All of the other TSM servers sharing this library are considered library clients. A library client requests shared library resources such as, drives or media from the TSM server acting as the library manager, but uses the resources independently. The library manager coordinates the access to these resources. Data moves over the SAN between the storage device and either the library manager or the library client. Either the library manager or any library client can manage the LAN-free movement of client data as long as the client system includes a storage agent. The Library Manager and Library Client configurations are represented in Figure 2 on page 4.
Figure 2. Library Manager/Client LANfree Configuration
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 clients data, which is stored on a tape library. v A TSM server library client manages a clients data, which is stored on a tape library.
Sharing Disk Storage using Tivoli SANergy

When TSM servers share access to disk storage, the environment contains a FILE library (TSM server File device class) and utilizes the SANergy product. SANergy provides a file sharing accelerator. If you will be using a FILE library, you must determine where the Tivoli SANergy client and the Tivoli SANergy Metadata Controller (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. See Figure 3 on page 5 and Table 1 on page 5 for the possible Tivoli SANergy configurations. See the SANergy publications for additional information about configuring SANergy.
1 TSM Client Storage Agent 3 Another Node
LAN
2 TSM Server
SAN
FILE Library
Figure 3. Tivoli SANergy Configurations
In the following table, the numbers refer to those numbers in Figure 3. For example, one possible configuration is for the Tivoli SANergy client to be installed on the TSM client machine ( 1 ) and the Tivoli SANergy MDC to be installed on the TSM server ( 2 ). These configurations can also consist of multiple platforms. For example, an environment can consist of a SUN MDC working with a Windows and AIX client.
Table 1. Tivoli SANergy Configurations Tivoli SANergy Component Tivoli SANergy Client Tivoli SANergy MDC 1 2 2 1 Where Installed 1 and 2 3
External Library Sharing ACSLS-Managed Libraries

When TSM servers share access to ACSLS-managed libraries, the sharing is enabled by middleware (such as, Gresham EDT-DistribuTAPE) between the data storage manager (TSM) and a media manager (StorageTek ACSLS). See Figure 4 on page 6. The ACSLS Server (or Library Station) manages the physical aspects of tape cartridge storage and retrieval. The external library manager, in this discussion Gresham EDT, communicates with the ACSLS Server or LibraryStation to access tape cartridges in an automated StorageTek library. The storage agent installed on a machine containing Gresham EDT and a TSM or Tivoli Data Protection (TDP) client provides access to SAN-attached storage devices resulting in LAN-free data movement. The continued connection to the LAN provides a meta data (control
Chapter 2. Planning
information) path. If the storage agent is not available, the LAN provides a failover path for data backup and recovery.
Library Manager on z/OS
LAN
Data Owner
or
ACSLS Server
Tivoli Storage Manager Client Gresham EDT Storage Agent
Tivoli Storage Manager Server Gresham EDT
Changer Control
3270
LAN-free Data Movement Changer Control
SAN
Changer Control
1 2 3 4
1 2 3 4
TCP/IP Communication Fibre Channel 3270 Communications-Library Control Commands Tape Drives
STK Tape Library
Figure 4. External Library Environment
For detailed installation, configuration, and system administration of ACSLS, refer to the appropriate StorageTek documentation. For detailed installation, configuration, data migration, and system administration of Gresham EDT-DistribuTAPE, refer to the Gresham EDT Users Manual.
Data Migration and Coexistence

If you currently have data associated with the TSM ACSLS library type and want to take advantage of LAN-free, you will need to consider coexistence and migration issues, see Appendix B. Legacy ACSLS Data Migration and Coexistence on page 37.
System Requirements
To use the Managed System for SAN feature configure the following components at the latest available software levels. See http://www.tivoli.com/support/storage_mgr/tivolimain.html v Your SAN configuration must meet the applicable hardware and software requirements (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 the storage agent. v A Tivoli Storage Manager server with this feature (version 5.1.0 or higher). The server and the storage agent must be at the same version, release, and maintenance level. The TSM servers for the AIX, HP-UX, Sun Solaris, and Windows operating systems support the Managed System for SAN feature. v A Tivoli Storage Management client or a Tivoli Data Protection client). Client software must be installed on a client system (check http://www.tivoli.com/support/storage_mgr/tivolimain.html for the clients that are currently supporting the Managed System for SAN feature). v A Tivoli Storage Manager storage agent. The storage agent must be installed on the same system as the client software. Also, the storage agent must be at the same level as the server with which it communicates (including maintenance (PTF) level). You can download the latest PTF from the Tivoli Web site at http://www.tivoli.com/support/storage_mgr/tivolimain.html. v The TSM application program interface (API) software must be at the version 4.2 or higher. You can obtain the API by downloading the latest version of the backup-archive client for AIX from the Web site at http://www.tivoli.com/support/storage_mgr/tivolimain.html. v If you are sharing disk storage, Tivoli SANergy Version 2.2 or higher must be installed. Note: If you are sharing only tape devices, Tivoli SANergy is not required. 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. For additional information and product download, see http:www.greshamstorage.com/products/download/distributape.html. Note: External library support only applies to Tivoli Storage Manager environments sharing Storage Technology (STK) tape devices.
Chapter 2. Planning
Chapter 3. Installation and Configuration

The following information describes the installation and configuration of the storage agent LAN-free environment. There are two procedures, which procedure you choose to follow depends upon the type of environment you are implementing. The first procedure covers environments that are using one or more of the following: v SCSI and 349X Tape Library sharing using the TSM Library Manager and Client v File device sharing using SANergy For installation and configuration steps, see Procedure 1 Tape and File Sharing with SCSI and 349X Tape and File Devices on page 10 . The second procedure specifically describes external library support for ACSLS library environment configuration, see Procedure 2 External Library Environment with an ACSLSManaged Library on page 21. For high-level descriptions of these environments, see Chapter 1. Storage Agent Overview on page 1 and Types of Configurations on page 3. To begin the installation and configuration process, read the summary of the procedure, review the complete procedure, and then perform the steps described in the procedure. The summary itself briefly describes the overall configuration. It is a good idea to understand the overall process before beginning the procedure, since the process takes place on multiple machines at differing times. Following the summary is the complete procedure containing the step-by-step installation and configuration instructions.
Summary of Tasks for Procedure 1

The following summarizes the installation and configuration tasks provided in the procedure: v Verifying network configuration Network: Ensure that your system meets the prerequisites for the SAN configuration. 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-free option Install and set up the storage agent TSM Server: If your environment is using tape devices, configure the library and drives on the SAN If your environment is using disk devices, configure Enterprise Management and define the FILE device class v Configuring devices for the storage agent to access
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 2

The following summarizes the installation and configuration tasks provided in the procedure: v Verifying network configuration Network: Ensure that your system meets the prerequisites for the SAN configuration. v Establishing communications and configuring the client, storage agent, and TSM server Client System: Install the TSM client or TDP client, and the TSM API. Specify the LAN-free option 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 File Devices
The following steps describe configuring a storage agent environment consisting of either shared libraries or shared disk, or both. If you are configuring an external library, that is, an ACSLS-managed library environment, see Procedure 2 External Library Environment with an ACSLSManaged Library on page 21.
Step 1. Network
The server system and the client systems must be attached to the SAN along with appropriate storage devices. The server system and the client systems must also be connected by means of a LAN. The Managed System for SAN feature requires specific levels and models of hardware and software. Ensure that your system configuration meets the hardware
10
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 have installed Tivoli SANergy Version 2.2 on the applicable machines. See Figure 3 on page 5 for possible Tivoli SANergy configurations. See the Tivoli SANergy Administrators Guide for details.
Establishing Communications among Client, Storage Agent, and Server

For a pictorial representation of what you will accomplish during the next two steps, see Figure 5 on page 17 .
Step 2. Client System

The sections in this step describe installation of TSM client, API, and storage agent software.
Install or Upgrade the Client and API Software

1. Check that the client system meets the prerequisites for client software. See the Users Guide for the client. Install the client software and API if it is not already installed on the system, or upgrade the software to the latest level as necessary. The latest levels can be downloaded from the Tivoli Storage Manager Web 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-Archive Installation and Users Guide. a. Edit the dsm.sys file to specify the communications method between the TSM client and server. For example:
COMMmethod TCPip TCPServeraddress tsmsrver.tucson.ibm.com TCPPort 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 edited in 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; when the path is available, during backup, restore, archive, and retrieve processing.
enablelanfree yes LANFREECommmethod TCPIP LANFREETCPPort 1500
or
LANFREECommmethod SharedMem LANFREESHMPORT 1510
3. If your are using a TDP client, configure the API by performing the following procedure: a. Set up the environment variables. The TSM API uses unique environment variables to locate files.
11
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.opt export DSMI_DIR=/usr/tivoli/tsm/client/api/bin export DSMI_LOG=/home/user_a/logdir
Note: The quickest method to set the environment variables is to add these variables to the users .profile file. b. Edit the dsm.sys file to specify the communications method between the TSM 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 installation directory. 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 to specify the options for connecting to the TSM server. For example:
SErvername COMMmethod TCPPort TCPServeraddress tsmsrver TCPip 1502 tsmsrver.tucson.ibm.com
Note: For illustrative purposes a tcpport of 1502 is used in the examples, however, the default tcpport is 1500. It is assumed that the dsm.sys file is controlled by the system administrator. The Tivoli Storage Manager server administrator should supply the name and IP address of the Tivoli Storage Manager server, as well as the node name and password. c. Edit the dsm.opt file specified by the DSMI_CONFIG environment variable to 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 TSM server. On the same system as the client, install the storage agent. The default installation directory is /usr/tivoli/tsm/StorageAgent/bin. The instructions in this section are shown using the Software Management and Installation 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 be different in your environment. Loading the storage agent files can take several minutes. Installation using the SMIT procedure:
12
1. Record the following information. This information is required throughout the remainder 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 to define 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 will need in order to communicate with the server. This is the same TSM server with 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 STATUS command from a TSM administrative command-line. b. The Server Password Set displayed in the QUERY STATUS output must be equal to YES and for this example the password is set to not4u. To set the server password issue the SET SERVERPASSWORD command from 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 Software Install and Update from the LATEST Available Software

Install Software Install 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 the device list. If you click on List, select the CD-ROM drive that you are using for the installation (for example, /dev/cd0). 6. Click on OK. 7. Locate the line Software to Install. a. To install all components listed in the table at step 8 on page 14, continue at step 10 on page 14.
13
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 2. Package and Fileset Names for Installation. AIX 4.3.3 Platforms
Package Name tivoli.tsm.StorageAgent.rte tivoli.tsm.devices.aix43.rte tivoli.tsm.msg.en_US.devices tivoli.tsm.msg.en_US.server Fileset Names tivoli.tsm.StorageAgent.rte tivoli.tsm.devices.aix43.rte tivoli.tsm.msg.en_US.devices tivoli.tsm.msg.en_US.server Description StorageAgent common functions, examples SCSI runtime device support SMIT screens Message catalog and Online help
Table 3. Package and Fileset Names for Installation. AIX 5.1 Platforms
Package Name tivoli.tsm.StorageAgent.rte tivoli.tsm.devices.aix5.rte64 tivoli.tsm.msg.en_US.devices tivoli.tsm.msg.en_US.server Fileset Names tivoli.tsm.StorageAgent.rte tivoli.tsm.devices.aix5.rte64 tivoli.tsm.msg.en_US.devices tivoli.tsm.msg.en_US.server Description StorageAgent common functions, examples SCSI runtime device support SMIT screens Message catalog and Online help
9. Click OK. 10. Check the default settings for the options on this window. 11. Click OK. SMIT responds:
ARE YOU SURE?...
12. Click OK. This installation may take several minutes. 13. Click Done after the installation is complete, remove the CD, and exit from SMIT. 14. Ensure that the DEVCONFIG option is specified in the dsmsta.opt file. For example, for a device configuration file named devconfig.out located at /usr/tivoli/tsm/StorageAgent/bin, edit the dsmsta.opt file and enter the following line:
DEVCONFIG devconfig.out
15. Use the information that you collected in step 1 on page 13 to issue the DSMSTA SETSTORAGESERVER command. For example:
dsmsta setstorageserver myname=storagnt mypassword=fun4me myhladdress=agent.tucson.ibm.com servername=tsmsrver serverpassword=not4u hladdress=tsmsrver.tucson.ibm.com lladdress=1502
See Set Installation Data for the Storage Agent: DSMSTA SETSTORAGESERVER on page 32 for details about the command parameters. The command generates the following lines in the device configuration file for the storage agent:
14
set staname storagnt SET STAPASSWORD xxxxxxx SET STAHLADDRESS agent.tucson.ibm.com DEFINE SERVER tsmsrver serverpassword=xxxxxxxxxxx HLADDRESS=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 Device Configuration File for the Storage Agent on page 34 for details on these files.
Step 3. Tivoli Storage Manager Server

The following provides the steps that you need to perform on the TSM server. If further explanation is required, see Administrators Guide. 1. For each client that you want to enable SAN data transfer, define the clients storage agent to the TSM server as if the storage agent is a server. You must use the same name and password that you set for the storage agent when you installed it on the client system. The DEFINE SERVER command must be issued from the TSM server (library manager or library client) that will manage the clients data. For example:
define server storagnt serverpassword=fun4me hladdress=agent.tucson.ibm.com lladdress=1500 validateprotocol=all
Note: The VALIDATEPROTOCOL parameter in the previous example is optional. This parameter determines whether a cyclic redundancy check should be performed to validate data on all metadata transferred between the storage agent and the TSM server. See the Administrators Reference for additional information about the DEFINE SERVER command. See the Administrators Guide for additional information about data validation. 2. Configure the SAN drives. This involves the following steps: Tape Device a. Define a shared SCSI or 3494 library b. Define paths to the library using the DEFINE PATH command on the server c. Define drives that are associated with the library d. Define paths to the drives using the DEFINE PATH command on the server e. Define the device class f. Define the storage pool
Disk Device Configure Enterprise Management and define a device class of DEVTYPE=FILE and SHARED=YES. TSM automatically defines a new FILE library and also defines drives corresponding to the mount limit for the FILE device class. The FILE library name is the same as the device class name. Each drive uses the library name with a numeric suffix. If the mount limit is changed, the number of drives also changes.
15
Note: As each session gets exclusive access to a file volume, the mount limit should 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 client must use a management class that has copy groups with a destination storage pool. The destination storage pool must be associated with the library. The library must be the one you have defined paths to the drives for the client. For example, 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 SAN drives that you configured. Note: If you decide not to use the default management class for the SAN drives, you will need to create a new management class. Clients that want to use the SAN drives need to use an include statement to bind their files to this new management class. See Backup-Archive Installation and Users 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 Administrators Guide for details on changing policy for clients that can use SAN drives. For details about the commands, see Administrators 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 provide more details.
16
TSM Client Workstation

Client - DATAOWNER dsm.sys file enablelanfree yes lanfreecommmethod tcpip lanfreetcpport 1500 tcpserveraddress tsmsrver.tucson.ibm.com tcpport 1502 Storage Agent - STORAGNT dsmsta.opt file servername tsmsrver devconfig devconfig.out devconfig.out file set staname storagnt set stapassword xxxxxxx set stahladdress agent.tucson.ibm.com define server tsmsrver serverpassword=xxxxxxxx hladdress=tsmsrver.tucson.ibm.com lladdress=1502
TSM Server - TSMSRVER

define server storagnt serverpassword=fun4me hladdress=agent.tucson.ibm.com lladdress=1500 register node dataowner bak2work domain=sandomain
Figure 5. Communications information. Results of Steps 2 and 3. The passwords are shown as xxxxxxx because they are encrypted in the file.
Configuring Devices for the Storage Agent to Access

Figure 6 on page 19 shows the results of completing Step 4. Client System and Step 5. Server on page 18.

Note: If you are configuring a FILE Library, skip this step and proceed to Step 5. Perform the following:
Obtain Tape Device Information

Use SMIT and issue the following commands to obtain information about tape devices. v For IBM devices:
Select Devices -> Tape Drive -> List All Defined Tape Drives
17
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. Server
The following provides information to help you define paths from the storage agent to the drives that are available to the TSM server. Paths allow a client, by means of a storage agent, access to drives in a library. The requirements are different depending on the device you are using. Consider the following guidelines before you begin defining paths to your SAN drives: 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, all drives that have paths can be used by storage agents backing up data. Backup operations will fail if you try to use other drives in a library that do not have defined paths. When paths are defined for each drive in a library, backup operations wait until the next drive is available for the transfer of data. Note: Backup operations can fail if no mount points are found to satisfy the request. If this occurs, it is likely that all available drives do not have a path to the client. v If you want to limit the number of drives available to a node, you can use the MAXNUMMP parameter on the REGISTER NODE or UPDATE NODE command. This will limit the number of drives that are available for the storage agent to use on behalf of the client. v Review tape device names. For the same tape device, the device name as known to the server will probably not match the device name as known to the storage agent.
Tape Devices
Define paths on the server using the device names as seen by the storage agent on each 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 on each client system. Note: The DEFINE PATH command must be issued from the server (library manager or library client) that will manage the clients data. For example, you would issue the following:
define path storagnt drive1 srctype=server desttype=drive library=sanlib1 device=/dev/mt1
See the Administrators Reference for your system platform for additional details on the DEFINE PATH command. Depending on the operating system of the TSM server, there may not be a quick way to confirm which device names on the storage agent correspond to device names on the TSM server without using a trial and error method. To confirm device names, you should work with one online drive at a time, and cycle through the storage agent device names until a successful backup can be run. On AIX, the serial number from lscfg -v -l rmt# is useful in finding the corresponding device name on the TSM server.
18
For a review of the results of the steps that you have just completed, see Figure 6.
Disk Devices
Define paths on the server using the device names as seen by the storage agent on each client system. For example, on the server side, the directory, d:\tsmdata\server1, is exported on the NFS server running on the TSM Server machine. On the storage agent, the directory is NFS mounted as /tsmdata/server1. Because the two directory names do not match, a path needs to be created for each file drive in the library. The following is the command issued to create the path for this scenario. In this example, file3 represents the destination file drive in the disk library with a name of disklib.
define path storagnt file3 srctype=server desttype=drive library=disklib device=file directory="/tsmdata/server1"
For command information, see the Administrators Reference. The following figure displays the results of completing steps three, four and five.

Storage Agent device name: /dev/mt1
SAN
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.

During this final step you will start the storage agent and verify the LAN-free configuration.
Start the Storage Agent

Start the storage agent by changing to the storage agent directory and issue the following command:
dsmsta
When the storage agent starts, it determines if the TSM server is a library client or library manager. If the TSM server is a library client, the storage agent uses information about the library manager from the library client in order to cross define itself to the library manager.
19
Verify the LAN-free Configuration

To verify that you have configured your system correctly for LAN-free data movement, perform the following procedure: 1. Run a backup operation from the client. Verify that the backup is LAN-free by using a TSM Administrative Command Line client to login to the TSM server and storage agent to verify the proper sessions have been established. When LAN-free data movement is occurring, a QUERY SESSION on the storage agent should show bytes received (displayed as Bytes Recvd) for the node increasing to the total amount of data being backed up. The QUERY SESSION on the TSM server should show a very small amount of bytes received (metadata) for the same node. If the nodes session exhibits this behavior, and you receive a message stating that the backup has been successful, you have configured your system correctly. 2. Ensure the following if you receive a message saying that the backup has failed. Note: If you retry the backup operation after the first failure, the client attempts to use the LAN connection for data movement. The client will continue 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 storage agent will not start. b. The client, storage agent, and server are communicating with each other as expected. 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-free

Use the following guidelines to help determine whether the data movement is using 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 perform this action by using a TSM administrative command-line client to login to the TSM server and storage agent to verify the proper sessions have been established. When LAN-free data movement is occurring, a QUERY SESSION on the storage agent should show bytes received (displayed as Bytes Recvd) for the node increasing to the total amount of data being backed up. The QUERY SESSION on the TSM server should show a very small amount of bytes received (metadata) for the same node. If the nodes session exhibits this behavior, the data movement is LAN-free. v Issue either of the following QUERY ACTLOG commands on the server to which the client is connected:
query actlog search=storage_agent_name msgno=8337
or
query actlog search=storage_agent_name
Note: If the query finds entries in the activity log that relates to the storage agent, the client is using LAN-free data transfer. v Review the amount of data being transmitted from the client to the server. The amount of data being transferred to the server should be considerably less than the amount of data being backed up. This is because the actual backup data is passed over the SAN. From the operating system command-line, issue:
netstat -D
20
Procedure 2 External Library Environment with an ACSLSManaged Library

If you will be using a Tivoli storage agent with ACSLS-managed libraries, you must have the ACSLS software and the third-party external library software (such as, Gresham EDT-DistribuTAPE) installed and configured. See the StorageTek ACSLS and the Gresham EDT documentation for installation instructions. See Figure 4 on page 6 for an example of a storage agent in an ACSLS-managed library environment. Complete the following steps to configure your storage agent external library environment:
Step 1. Network
The server system and the client systems must be attached to the SAN along with appropriate storage devices. The server system and the client systems must also be connected by means of a LAN. The Managed System for SAN feature requires specific levels and models of hardware and software. Ensure that your system configuration meets the hardware and 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 two steps, see Figure 7 on page 28.

The 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 library enablement is allowed. For installation information, see the Gresham or other middleware products documentation. Install or Upgrade the Client and API Software: 1. Check that the client system meets the prerequisites for client software. See the Users Guide for the client. Install the client software and API if it is not already installed on the system, or upgrade the software to the latest level as necessary. The latest levels can be downloaded from the Tivoli Storage Manager Web 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-Archive Installation and Users Guide. a. Edit the dsm.sys file to specify the communications method between the TSM client and server. For example:
COMMmethod TCPip TCPServeraddress tsmsrver.tucson.ibm.com TCPPport 1502
b. Edit the dsm.opt file to specify the servername of the dsm.sys stanza edited in step a. For example,
servername tsmsrver
21
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; when the path is available, during backup, restore, archive, and retrieve processing.
enablelanfree yes LANFREECommmethod TCPIP LANFREETCPPORT 1500
or
LANFREECommmethod SharedMem LANFREESHMPORT 1510
3. If your are using a TDP client, configure the API by performing the following procedure: 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.opt export DSMI_DIR=/usr/tivoli/tsm/client/api/bin export DSMI_LOG=/home/user_a/logdir
Note: The quickest method to set the environment variables is to add these variables to the users .profile file. b. Edit the dsm.sys file to specify the communications method between the TSM 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 installation directory. 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 to specify the options for connecting to the TSM server. For example:
SErvername COMMmethod TCPPort TCPServeraddress tsmsrver TCPip 1502 tsmsrver.tucson.ibm.com
It is assumed that the dsm.sys file is controlled by the system administrator. The Tivoli Storage Manager server administrator should supply the name and IP address of the Tivoli Storage Manager server, as well as the node name and password. c. Edit the dsm.opt file specified by the DSMI_CONFIG environment variable to 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
Note: The Storage Agent should not be installed on the same machine as the TSM server. On the same system as the client, install the storage agent. The default installation directory is /usr/tivoli/tsm/StorageAgent/bin. The instructions in this section are shown using the Software Management and Installation 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 be different in your environment. Loading the storage agent files can take several minutes. 1. Record the following information. This information is required throughout the remainder 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 to define 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 will need in order to communicate with the server. This is the same TSM server with 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 STATUS command from a TSM administrative command-line. b. The Server Password Set displayed in the QUERY STATUS output must be equal to YES and for this example the password is set to not4u. To set the server password issue the SET SERVERPASSWORD command from 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 &

Install and Update Software Install and Update from the LATEST Available Software
23
Install Software Install 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 the device list. If you click on List, select the CD-ROM drive that you are using for the installation (for example, /dev/cd0). 6. Click on OK. 7. Locate the line Software to Install. a. To install all components listed in the table at step 8, continue at step 10. b. To selectively install components, click on List for the latest available 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 tivoli.tsm.StorageAgent.rte tivoli.tsm.devices.aix43.rte tivoli.tsm.msg.en_US.devices tivoli.tsm.msg.en_US.server Fileset Names tivoli.tsm.StorageAgent.rte tivoli.tsm.devices.aix43.rte tivoli.tsm.msg.en_US.devices tivoli.tsm.msg.en_US.server Description StorageAgent common functions, examples SCSI runtime device support SMIT screens Message catalog and Online help
Table 5. Package and Fileset Names for Installation. AIX 5.1 Platforms
Package Name tivoli.tsm.StorageAgent.rte tivoli.tsm.devices.aix5.rte64 tivoli.tsm.msg.en_US.devices tivoli.tsm.msg.en_US.server Fileset Names tivoli.tsm.StorageAgent.rte tivoli.tsm.devices.aix5.rte64 tivoli.tsm.msg.en_US.devices tivoli.tsm.msg.en_US.server Description StorageAgent common functions, examples SCSI runtime device support SMIT screens Message catalog and Online help
9. Click OK. 10. Check the default settings for the options on this window. 11. Click OK. SMIT responds:
ARE YOU SURE?...
12. Click OK. This installation may take several minutes. 13. Click Done after the installation is complete, remove the CD, and exit from SMIT. 14. Use the information that you collected in step 1 on page 23 to issue the DSMSTA SETSTORAGESERVER command. For example:
24
Note: The TSM server, in this example TSMSRVER, must be running when the DSMSTA SETSTORAGESERVER command is issued. See Set Installation Data for the Storage Agent: DSMSTA SETSTORAGESERVER on page 32 for details about the command parameters. The command generates the following lines in the device configuration file for the storage agent:
SET STANAME storagnt SET STAPASSWORD xxxxxxx SET STAHLADDRESS agent.tucson.ibm.com DEFINE SERVER tsmsrver serverpassword=not4u HLADDRESS=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 Device Configuration 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 has completed successfully. Use the library information that you collected in step 1 on page 23 to add library definition information to the device configuration file. For example: Incorporate the following library definition information: v v v v Add the library named stk-lib Set the libtype to external Set lanfree to YES Set obeymountretention to YES
Using the editor of your choice, open device configuration file and add the following 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 storagnt SET STAPASSWORD xxxxxxx SET STAHLADDRESS agent.tucson.ibm.com DEFINE SERVER tsmsrver serverpassword=xxxxxxxxxxx HLADDRESS=tsmsrver.tucson.ibm.com LLADDRESS=1502 DEFINE 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 ACSLS library 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=library externalmanager=/usr/lpp/dtelm/bin/elm
25
For additional information about the DEFINE PATH command, see the Tivoli Storage Manager Administrators Reference.
Step 3.Tivoli Storage Manager Server

The following provides the steps that you need to perform on the TSM server. If further explanation is required, see Administrators Guide. On the server, perform the following: 1. Install Gresham EDT or any other third-party software that provides external library enablement. For installation information, see the Gresham documentation. 2. For each client that you want to enable SAN data transfer, define the clients storage agent to the TSM server as if the storage agent is a server. You must use the same name and password that you set for the storage agent when you installed it on the client system. The DEFINE SERVER command must be issued from the TSM server that will manage the clients data. For example:
define server storagnt serverpassword=fun4me hladdress=agent.tucson.ibm.com lladdress=1500 validateprotocol=all
Note: The VALIDATEPROTOCOL parameter in the previous example is optional. This parameter determines whether a cyclic redundancy check should be performed to validate data on all metadata transferred between the storage agent and the TSM server. See the Administrators Reference for additional information about the DEFINE SERVER command. See the Administrators Guide for additional information about data 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. Gresham EDT-DistribuTape is the external library manager interfacing with the ACSLS 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=library externalmanager=/usr/lpp/dtelm/bin/elm
In the previous example the path provided for the external manager is dependent upon the operating system where the TSM server resides. For example, an AIX TSM server external manager path is /usr/lpp/dtelm/bin/elm in contrast to a TSM Sun server external manager path of /opt/OMIdtelm/bin/elm or a TSM Windows server external manager path of c:\program files\GES\EDT\bin\elm.exe. For additional information about the DEFINE PATH command, see theAdministrators Reference. c. Define a path from the storage agent to the external manager. The DEFINE PATH command must be issued from the TSM server. Gresham EDT-DistribuTape is the external library manager interfacing with the ACSLS 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=library externalmanager=/opt/OMIdtelm/bin/elm
For additional information about the DEFINE PATH command, see the Tivoli Storage Manager Administrators Reference. d. Define a device class with a device type of ECARTRIDGE
26
e. Define the storage pool 4. 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 client must use a management class that has copy groups with a destination storage pool. The destination storage pool must be associated with the library. The library must be the one that you have defined paths to its drives for the client. For example, 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 SAN drives that you configured. Note: If you decide not to use the default management class for the external library, you will need to create a new management class. Clients that want to use the SAN attached library need to use an include statement to bind their files to this new management class. See Backup-Archive Installation and Users 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 Administrators Guide for details on changing policy for clients that can use SAN drives. For additional command information, see Administrators 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 provide more details.
27

Client - DATAOWNER dsm.sys file enablelanfree yes lanfreecommmethod tcpip lanfreetcpport 1500 tcpserveraddress tsmsrver.tucson.ibm.com tcpport 1502 Storage Agent - STORAGNT dsmsta.opt file servername tsmsrver devconfig devconfig.out devconfig.out file set staname storagnt set stapassword xxxxxxx set stahladdress agent.tucson.ibm.com define server tsmsrver serverpassword=xxxxxxxx hladdress=tsmsrver.tucson.ibm.com lladdress=1502

define server storagnt serverpassword=fun4me hladdress=agent.tucson.ibm.com lladdress=1500 register node dataowner bak2work domain=sandomain
Figure 7. Communications information. Results of Steps 2 and 3. The passwords are shown as xxxxxxx because they are encrypted in the file.
Configuring Devices for the Storage Agent to Access Step 4. Client System
During this step you will start the storage agent and verify the LAN-free configuration.
Start the Storage Agent

Start the storage agent by changing to the storage agent directory and issue the following command:
dsmsta
Verify the LAN-free Configuration

To verify that you have configured your system correctly for LAN-free data movement, perform the following procedure: 1. Run a backup operation from the client. Verify that the backup is LAN-free by using a TSM Administrative Command Line client to login to the TSM server and storage agent to verify the proper sessions have been established. When
28
LAN-free data movement is occurring, a QUERY SESSION on the storage agent should show bytes received (displayed as Bytes Recvd) for the node increasing to the total amount of data being backed up. The QUERY SESSION on the TSM server should show a very small amount of bytes received (metadata) for the same node. If the nodes session exhibits this behavior, and you receive a message stating that the backup has been successful, you have configured your system correctly. 2. Ensure the following if you receive a message saying that the backup has failed. Note: If you retry the backup operation after the first failure, the client attempts to use the LAN connection for data movement. The client will continue 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 storage agent will not start. b. The client, storage agent, and server are communicating with each other as expected. c. The mount and message is displayed on the storage agent console. Determining Whether the Data Movement was LAN-free: Use the following guidelines to help determine whether the data movement is using 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 perform this action by using a TSM administrative command-line client to login to the TSM server and storage agent to verify the proper sessions have been established. When LAN-free data movement is occurring, a QUERY SESSION on the storage agent should show bytes received (displayed as Bytes Recvd) for the node increasing to the total amount of data being backed up. The QUERY SESSION on the TSM server should show a very small amount of bytes received (metadata) for the same node. If the nodes session exhibits this behavior, the data movement is LAN-free. v Issue either of the following QUERY ACTLOG commands on the server to which the client is connected:
query actlog search=storage_agent_name msgno=8337
or
query actlog search=storage_agent_name
Note: If the query finds entries in the activity log that relates to the storage agent, the client is using LAN-free data transfer. v Review the amount of data being transmitted from the client to the server. The amount of data being transferred to the server should be considerably less than the amount of data being backed up. This is because the actual backup data is passed over the SAN. From the command, issue:
netstat -D
29
30
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 Agent

Start the storage agent by accessing the storage agent directory and issue the following command:
dsmsta
Stop the storage agent by typing the following command at the command line prompt:
halt
Obtaining Tape Device Information on the Client System

To complete the setup of the storage agent, you must obtain the device names from the client system. You can get this information by using SMITTY and issuing the following 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
31
Set Installation Data for the Storage Agent: DSMSTA SETSTORAGESERVER Purpose
Use this utility on the client system where the storage agent has been installed. The utility adds communication information to the device configuration file and the dsmsta.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 appends information to the existing files. The option devconfig, which sets a name for the device configuration file, must exist in the dsmsta.opt file for the command to work. 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
Parameters
All parameters are required. MYName Specifies the name of the storage agent. This name appears in the SET STANAME command that is inserted into the device configuration file. Note: You must use the same name when you define the storage agent as a server to the TSM server. MYPAssword Specifies the password of the storage agent. This value is encrypted and used in the SET STAPASSWORD command that is inserted into the device configuration file. Note: You must use the same password when you define the storage agent as a server to the TSM server. MYHLAddress Specifies the TCP/IP address of the storage agent. This value is used internally in the SET STAHLAddress command which is inserted into the device configuration file.
32
SERVERName Specifies the name of the TSM server. This name appears in the DEFINE SERVER command that is inserted into the device configuration file. SERVERPAssword Specifies the password of the server. This value is encrypted and appears in the SERVERPASSWORD field of the DEFINE SERVER command that is inserted into the device configuration file. HLAddress Specifies the TCP/IP address of the server. This value is used in the HLADDRESS field of the DEFINE SERVER command. LLAddress Specifies the TCP/IP port on which to access the server. This value is used in the LLADDRESS field of the DEFINE SERVER command.
Examples
Issue the DSMSTA SETSTORAGESERVER command with the following information: v Storage agent Name: storagnt Password: fun4me TCP/IP address: agent.tucson.ibm.com v TSM server Name: tsmsrver Password: not4u TCP/IP address: tsmsrver.tucson.ibm.com TCP/IP port: 1502 The command is:
The command generates the following lines in the device configuration file for the storage agent:
SET STANAME storagnt SET STAPASSWORD xxxxxxx SET STAHLADDRESS agent.tucson.ibm.com DEFINE SERVER tsmsrver serverpassword=xxxxxxxx HLADDRESS=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 the storage agent:
SERVERNAME tsmsrver
33
The Storage Agent Options File

The options file for the storage agent is named dsmsta.opt. The dsmsta.opt file for the storage agent contains the name of the server with which the storage agent communicates, along with other options. The dsmsta.opt file is located where the storage agent program 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 TSM server changes, you may need to make changes to this file. The required options are: SERVERName server_name The name of the TSM server with which the storage agent communicates. The DSMSTA SETSTORAGESERVER command inserts this option. DEVCONFig file_name The name of the device configuration file for the storage agent. A typical name for the file is devconfig. The following options are also available, but not required: RESOURCETimeout minutes Specifies the maximum number of minutes that a storage agent waits for a resource on the server. The default value is 10 minutes. The minimum value is 1 minute. This parameter is optional. STAMaxpooledsessions number The number of sessions that the storage agent keeps open to the TSM server. The default value is 25. Possible values are 0 to 150. If the storage agent needs more sessions than specified, additional sessions are considered 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 Agent

The device configuration file for the storage agent includes information on the storage agent itself and information about the TSM server with which the storage agent communicates. The file is typically named devconfig and is with the storage agent program at this location: /usr/tivoli/tsm/StorageAgent/bin . The DSMSTA SETSTORAGESERVER command normally generates the contents of the file. If you have changes to the TSM server or if a service representative directs you, you may need to make changes to the information. You can use the DSMSTA SETSTORAGESERVER 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 second device configuration file example.
SET STANAME storagnt SET STAPASSWORD fun4me SET STAHLADDRESS agent.tucson.ibm.com DEFINE SERVER tsmsrver serverpassword=not4u HLADDRESS=tsmsrver.tucson.ibm.com LLADDRESS=1502
In this example, STORAGNT is the name of the storage agent and TSMSRVER is the name of the TSM server.
34
Typical contents of the device configuration file for an ACSLS-managed library environment are as follows:
SET STANAME storagnt SET STAPASSWORD fun4me SET STAHLADDRESS agent.tucson.ibm.com DEFINE SERVER tsmsrver serverpassword=not4u HLADDRESS=tsmsrver.tucson.ibm.com LLADDRESS=1502 DEFINE LIBRARY stk-lib libtype=external lanfree=yes obeymountretention=no
In this example, STORAGNT is the name of the storage agent, TSMSRVER is the name of the TSM server, and STK-LIB is the name of the ACSLS-managed tape library. The following describes the contents of the file: SET STANAME Sets the name of the storage agent. The name must be the same as the name that was used to define the storage agent as a server to the TSM server. SET STAPASSWORD Sets the password of the storage agent. The password must be the same as the password that was used when defining the storage agent as a server to the TSM server. The password is encrypted. SET STAHLADDRESS Sets the TCP/IP address of the storage agent. DEFINE SERVER The definition of the TSM server with which the storage agent communicates. DEFINE LIBRARY The definition of an ACSLS-managed library to the TSM server.
35
36
Appendix B. Legacy ACSLS Data Migration and Coexistence

Note: For the latest information concerning migration and coexistence, see the Tivoli Storage Manager readme. If your environment consists of TSM storage pools associated with an ACSLS library type and a device class containing the GENERICTAPE device type, you need to consider migration and coexistence issues for existing data. To take advantage of LAN-free data transfer, the data must be migrated to a storage pool associated with an EXTERNAL library type and a device class containing the ECARTRIDGE device type. Data migration is recommended over coexistence.
Data Migration
Data migration of ACSLS to EXTERNAL is recommended. Migrate the existing data from existing (old) storage pools to new storage pools associated with the appropriate policy, device class, and library definitions. Migration of data also allows the entire environment to be LAN-free, providing better performance and better utilization of tape drives and media. Figure 8 displays the normal migration path from an old storage pool containing the data associated with the ACSLS library type to a new storage pool associated with an EXTERNAL library type and an ECARTRIDGE device class.
Figure 8. Legacy ACSLS Data Migration
37
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 moving any expired files in the aggregates. For more information, see the Managing Storage Pools and Volumes section of the Administrators Guide. v Use the Tivoli Storage Manager server storage pool reclamation function. This method works by reclaiming the active files from the legacy ACSLS storage pools. Reclamation processing, however, is very resource intensive and should be performed during periods of low resource utilization. For more information, see Reclaiming Space in Sequential Access Storage Pools section of the Administrators Guide.
Data Coexistence
Storage pool volumes created using the ACSLS library type cannot be accessed using the EXTERNAL library type, but the two library types can coexist on the same STK library. Even though ACSLS and EXTERNAL data coexistence is not recommended, coexistence might provide a temporary solution during the migration for certain environments, such as, large amounts of legacy ACSLS data and very small migration time-windows. Allowing ACSLS and EXTERNAL library types to coexist requires that tape drives within the library be partitioned. The ACSLS library type requires at least one dedicated tape drive. If you choose to have data coexist, either temporarily or long-term, be sure to implement the following 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 the ACSLS 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
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 in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the users responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product, 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 it believes appropriate without incurring any obligation to you.
39
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation Information Enabling Requests Dept. M13 5600 Cottle Road San Jose CA 95193-0001 U.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 material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. If you are viewing this information softcopy, the photographs and color illustrations may not appear.
Trademarks
The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: AIX IBM IBMLink Tivoli is a trademark of Tivoli Systems Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft 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
EDT-DistribuTAPE is a trademark of Gresham in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others.
Appendix C. Notices
41
42
Glossary
The terms in this glossary are defined as they pertain to the Tivoli Storage Manager library. If you do not find the term you need, refer to the IBM Software Glossary on the Web at this URL: www.ibm.com/ibm/terminology/. You can also refer to IBM Dictionary of Computing, New York: McGraw-Hill, 1994. For a complete Tivoli Storage Manager glossary, see Administrators 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 may be 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 the International Organization for Standardization and the International Electrotechnical Commission (ISO/IEC JTC2/SC1).
A
ACSLS. Automated cartridge system library software. application client. One of the Tivoli Data Protection for application programs installed on a system. The Tivoli Storage Manager server provides backup services to these clients. archive. To copy one or more files to a storage pool for long-term storage. Archived files can include descriptive information and can be retrieved by archive date, by file name, or by description. Contrast with retrieve. automated cartridge system library software (ACSLS). A library-enablement application from StorageTek. ACSLS functions as the central service provider for library operations.
client node. A file server or workstation on which the backup-archive client program has been installed, and which has been registered to the server. client options file. A file that a client can change, containing a set of processing options that identify the server, communication method, and options for backup, archive, hierarchical storage management, and scheduling. Also called the dsm.opt file.
D
device class. A named set of characteristics applied to a group of storage devices. Each device class has a unique name and represents a device type of disk, file, optical disk, or tape. device configuration file. (1) On a Tivoli Storage Manager storage agent, a file that contains the name and password of the storage agent, and the DEFINE SERVER command for the Tivoli Storage Manager server that is managing the SAN-attached libraries and drives. (2) On a Tivoli Storage Manager server, a file that contains information about defined device classes, and, on some Tivoli Storage Manager servers, defined libraries and drives. device driver. A collection of subroutines that control the interface between I/O device adapters and the processor. dsm.opt file. See client options file. dsmserv.opt. See server options file. dsmsta.opt. See storage agent options file.
B
back up. To copy information to another location to ensure against loss of data. In Tivoli Storage Manager, you can back up user files, the Tivoli Storage Manager database, and storage pools. Contrast with restore. backup-archive client. A program that runs on a workstation or file server and provides a means for users to back up, archive, restore, and retrieve files.
C
client. A program running on a PC, workstation, file server, LAN server, or mainframe that requests services of another program, called the server. The following types of clients can obtain services from a Tivoli Storage Manager server: administrative client, application client, API client, backup-archive client, and HSM client (also known as space manager client).
E
external library. A type of enablement provided by Tivoli Storage Manager to allow LAN-free data
43
movement for ACSLS-managed StorageTek libraries. To activate this support the Tivoli Storage Manager library type must be EXTERNAL.
only one policy set is active at one time. See policy domain and management class.
F
FILE device type. A device type that specifies the use of sequential access files on disk storage as volumes.
R
reclamation. A process of consolidating the remaining data from many sequential access volumes onto fewer new sequential access volumes. restore. To copy information from its backup location to the active storage location for use. In Tivoli Storage Manager, you can restore the server database, storage pools, storage pool volumes, and users backed-up files. The backup version in the storage pool is not affected by the restore operation. Contrast with backup.
L
LAN. Local area network. LAN-free data transfer. The movement of client data directly between a client and a storage device over a SAN, rather than over the LAN. library. (1) A repository for demountable recorded media, such as magnetic tapes. (2) For Tivoli Storage Manager, a collection of one or more drives, and possibly robotic devices (depending on the library type), which can be used to access storage volumes. library manager. A Tivoli Storage Manager server that controls device operations when multiple Tivoli Storage Manager servers share a storage device. The device operations include mount, dismount, volume ownership, and library inventory.
S
SAN. Storage area network. SCSI. Small computer system interface. server. The program that provides backup, archive, space management, and administrative services to clients. The server program must be at the necessary level to provide all of these services. server options file. A file that contains settings that control various server operations. These settings, or options, affect such things as communications, devices, and performance. server storage. The primary and copy storage pools used by the server to store users files: backup versions, archive copies, and files migrated from Tivoli Space Manager client nodes (space-managed files). See storage pool. shared library. A library device that is shared among multiple Tivoli Storage Manager servers. storage agent. A program that enables Tivoli Storage Manager to back up and restore client data directly to and from SAN-attached storage. storage agent options file. A file that specifies options for the storage agent. This includes the name of the Tivoli Storage Manager server with which the storage agent communicates, the number of sessions that can be kept open to the server, and the name of the device configuration file. Also called the dsmsta.opt file. storage pool. A named set of storage volumes that is the destination that the Tivoli Storage Manager server uses to store client data. The client data consists of backup versions, archive copies, and migrated files. You can back up a primary storage pool to a copy storage pool.
M
management class. A policy object that users can bind to each file to specify how the server manages the file. The management class can contain a backup copy group, an archive copy group, and space management attributes. The copy groups determine how the server manages backup versions or archive copies of the file. The space management attributes determine whether the file is eligible to be migrated by the space manager client to server storage, and under what conditions the file is migrated.
N
node. A workstation or file server that is registered with a Tivoli Storage Manager server to receive its services. See also client node.
P
policy domain. A policy object that contains policy sets, management classes, and copy groups that are used by a group of client nodes. See policy set and management class. policy set. A policy object that contains a group of management classes that exist for a policy domain. Several policy sets can exist within a policy domain but
44
T
tape library. A term used to refer to a collection of drives and tape cartridges. The tape library may be an automated device that performs tape cartridge mounts and demounts without operator intervention.
Glossary
45
46
Index A
ACSLS support 5, 21, 37
O
obtaining tape device information 17 option, enablelanfree 11, 22 options file client 11, 22 storage agent 15, 25, 34
D
data movement, SAN prerequisites 7 tasks 9 device configuration file 34 disk device SANergy 2.2 11 server install 15 dsm.opt file 11, 22 DSMSTA SETSTORAGESERVER 14, 24 dsmsta.opt 15, 25, 34
P
path defining 18 disk devices 19 tape devices 18 policy for Managed System for SAN 16, 27
E
enablelanfree option 11, 22 external library support 5, 21, 37
S
SAN data movement prerequisites 7 tasks 9 storage agent component configuration 7 configuring device access 17 device configuration file 34 installing 12, 23 options file 34 starting 19, 28 usage requirements 7 verify configuration 20, 28
F
FILE library configuration considerations 4 disk devices 15
H
how to determine LAN-free data movement 20, 29
T
tape device information, obtaining 17 TSM API install 11, 22 upgrade 11, 22
L
LAN-free data movement enabling, dsm.opt 11, 22 guidelines for determining 20, 29 library client 3 library manager 3 limit the SAN drives 18
M
Managed System for SAN description 1 FILE library 4 planning configurations 3 policy considerations 16, 27 SANergy Metadata Controller 4
N
network requirements 10, 21 no-query restore 2
47
48
Program Number: 5698-ISE
Printed in the United States of America on recycled paper containing 10% recovered post-consumer fiber.
GC32-0771-00

Tivoli Storage Manager Storage Agent

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Tivoli Storage Manager Storage Agent

Uploaded by

Copyright:

Available Formats

Tivoli Storage Manager for AIX

Managed System for SAN Storage Agent Users Guide

Tivoli Storage Manager for AIX

Managed System for SAN Storage Agent Users Guide

Summary of Changes for Tivoli Storage Manager . . . . . . . . . . . . . . ix

Chapter 1. Storage Agent Overview . . . 1

Appendix A. Administration and Configuration Reference . . . . . . . 31

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

Chapter 3. Installation and Configuration 9

Copyright IBM Corp. 2000, 2002

About This Book

Where to Look for Information

Contacting Customer Support

Copyright IBM Corp. 2000, 2002

Tivoli Storage Manager Publications

The following table lists Tivoli Data Protection publications.

Order Number SC33-6340 SC33-6341 SC33-6389 SC33-6399 GC32-0444

Related IBM Hardware Products Publications

Summary of Changes for Tivoli Storage Manager

Technical Changes for Version 5 Release 1March 2002

Copyright IBM Corp. 2000, 2002

Chapter 1. Storage Agent Overview

Client Storage Agent installed

Library Control Client Metadata LAN

Storage Manager Server

Copyright IBM Corp. 2000, 2002

LAN-free Client Data Backup Scenario

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

Sharing Tape Storage using TSM Library Manager/Client

Copyright IBM Corp. 2000, 2002

Figure 2. Library Manager/Client LANfree Configuration

Sharing Disk Storage using Tivoli SANergy

1 TSM Client Storage Agent 3 Another Node

Figure 3. Tivoli SANergy Configurations

External Library Sharing ACSLS-Managed Libraries

Library Manager on z/OS

Tivoli Storage Manager Client Gresham EDT Storage Agent

Tivoli Storage Manager Server Gresham EDT

LAN-free Data Movement Changer Control

STK Tape Library

Figure 4. External Library Environment

Data Migration and Coexistence

Chapter 3. Installation and Configuration

Summary of Tasks for Procedure 1

Summary of Tasks for Procedure 2

Establishing Communications among Client, Storage Agent, and Server

Step 2. Client System

Install or Upgrade the Client and API Software

Install and Configure the Storage Agent

For AIX 4.3, select:

For AIX 5.1, select:

Step 3. Tivoli Storage Manager Server

Chapter 3. Installation and Configuration

TSM Client Workstation

TSM Server - TSMSRVER

Configuring Devices for the Storage Agent to Access

Step 4. Client System

Obtain Tape Device Information

Chapter 3. Installation and Configuration

v For other devices:

TSM Client Workstation

TSM Server - TSMSRVER

Step 6. Client System