ibm tivoli storage manager for linux: managed …publib.boulder.ibm.com › tividd › td › itsml...

IBM Tivoli Storage Managerfor Linux

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

GC23-4693-00

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

First Edition (October 2002)

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

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

Your feedback is important in helping to provide the most accurate and high-quality information. If you have anycomments about this book or any other IBM Tivoli Storage Manager documentation, please see “ContactingCustomer 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 Contractwith IBM Corp.

Contents

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

Contacting Customer Support . . . . . . . vInternet . . . . . . . . . . . . . . . viIBM Tivoli Storage Manager Publications . . . viIBM Redbooks . . . . . . . . . . . . viii

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

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

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

System Requirements . . . . . . . . . . . 6

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

Step 2. Client System . . . . . . . . . . 10Step 3. IBM Tivoli Storage Manager Server . . . 14

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

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

Summary of Tasks for Procedure 2 . . . . . . 20Procedure 2 — External Library Environment withan ACSLS–Managed Library. . . . . . . . . 20

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

Appendix A. Administration andConfiguration Reference . . . . . . . 29Starting and Stopping the Storage Agent . . . . 29Obtaining Tape Device Information on the ClientSystem . . . . . . . . . . . . . . . . 29

IBM Tape Devices . . . . . . . . . . . 29Non-IBM Tape Devices . . . . . . . . . 29

Set Installation Data for the Storage Agent: DSMSTASETSTORAGESERVER. . . . . . . . . . . 31The Storage Agent Options File. . . . . . . . 33The Device Configuration File for the Storage Agent 33

Appendix B. Notices . . . . . . . . . 35Trademarks . . . . . . . . . . . . . . 36

Glossary . . . . . . . . . . . . . . 37

Index . . . . . . . . . . . . . . . 41

© Copyright IBM Corp. 2000, 2002 iii

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

About This Book

This user’s guide is intended for anyone who will be using the Tivoli ManagedSystem for SAN product, commonly referred to as the storage agent. Thisdocument provides an overview of LAN-free data transfer. It also providesdetailed explanations about configuring and using the IBM Tivoli Storage Manager(Storage Manager) client, storage agent, and Storage Manager server. You shouldbe familiar with Storage Manager, SAN, and Linux operating systemadministration. You may require additional publications during configuration ofthe storage agent environment. Refer to the listing of IBM Tivoli Storage ManagerPublications in “Where to Look for Information”.

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

Where to Look for InformationThe following describes the service that IBM provides for Managed System forSAN Storage Agent and tells you where to look for more information about IBMTivoli Storage Manager products.

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

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

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

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

v Send e-mail to [email protected].

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

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

You can also review the Customer Support Handbook, which is available on our Website at http://www.tivoli.com/support/handbook/.

When you contact Tivoli Customer Support, be prepared to provide identificationinformation for your company so that support personnel can readily assist you.Company identification information may also be needed to access various onlineservices available on the Web site.

The support Web site offers extensive information, including a guide to supportservices (the Customer Support Handbook); frequently asked questions (FAQs);and documentation for all Tivoli products, including Release Notes, Redbooks™,

© Copyright IBM Corp. 2000, 2002 v

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


http://www2.ibmlink.ibm.com

http://www.tivoli.com/support

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

and Whitepapers. The documentation for some product releases is available inboth PDF and HTML formats. Translated documents are also available for someproduct releases.

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

We are very interested in hearing about your experience with Tivoli products anddocumentation. We also welcome your suggestions for improvements. If you havecomments or suggestions about our documentation, please contact us in one of thefollowing ways:v Send e-mail to [email protected] Complete our customer feedback survey at

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

Reporting a ProblemPlease have the following information ready when you report a problem:v The Storage Manager server version, release, modification, and service level

number. You can get this information by entering the QUERY STATUS command atthe Storage Manager command line.

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

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

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

v The exact text of any error messages.

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

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

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

Publication Title Order Number

IBM Tivoli Storage Management Products License Information GH09-4572

IBM Tivoli Storage Manager Messages GC32-0767

IBM Tivoli Storage Manager for Linux Administrator’s Guide GC23-4690

IBM Tivoli Storage Manager for Linux Administrator’s Reference GC23-4691

IBM Tivoli Storage Manager for Linux Quick Start GC23-4692

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

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

ftp://ftp.software.ibm.com

The following table lists Storage Manager storage agent publications.


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

GC32-0771

IBM Tivoli Storage Manager for HP-UX Managed System for SANStorage Agent User’s Guide

GC32-0727

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

GC23-4693

IBM Tivoli Storage Manager for Sun Solaris Managed System for SANStorage Agent User’s Guide

GC32-0781

IBM Tivoli Storage Manager for Windows Managed System for SANStorage Agent User’s Guide

GC32-0785

The following table lists Storage Manager client publications.


IBM Tivoli Space Manager for UNIX: Using the Hierarchical StorageManagement Clients

GC32-0794

IBM Tivoli Storage Manager for Macintosh: Backup-Archive ClientsInstallation and User’s Guide

GC32-0787

IBM Tivoli Storage Manager for NetWare: Backup-Archive ClientsInstallation and User’s Guide

GC32-0786

IBM Tivoli Storage Manager for UNIX: Backup-Archive ClientsInstallation and User’s Guide

GC32-0789

IBM Tivoli Storage Manager for Windows: Backup-Archive ClientsInstallation and User’s Guide

GC32-0788

IBM Tivoli Storage Manager Using the Application Program Interface GC32-0793

The following table lists Tivoli Data Protection publications.

Publication TitleOrderNumber

IBM Tivoli Data Protection for EMC Symmetrix for R/3 Installation and User’sGuide

SC33-6386

IBM Tivoli Storage Manager for Hardware: Data Protection for Enterprise StorageServer Databases (DB2 UDB) Installation and User’s Guide

SC32-9060-00

IBM Tivoli Storage Manager for Hardware: Data Protection for Enterprise StorageServer Databases (Oracle) Installation and User’s Guide

SC32-9061-00

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

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

IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino forUNIX and OS/400 Installation and User’s Guide

SC32-9056-00

IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino forWindows Installation and User’s Guide

SC32-9057-00

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

GC26-7305

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

About This Book vii

Publication TitleOrderNumber

IBM Tivoli Data Protection for Lotus Notes on Windows NT Installation andUser’s Guide

SH26-4065

IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft ExchangeServer Installation and User’s Guide

SC32-9058-00

IBM Tivoli Storage Manager for Databases: Data Protection for Microsoft SQLServer Installation and User’s Guide

SC32-9059-00

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

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

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

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

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

IBM Tivoli Data Protection for WebSphere Application Server Installation andUser’s Guide

SC33-6399

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

IBM RedbooksThe International Technical Support Center (ITSC) publishes redbooks, which arebooks on specialized topics, such as, Using Storage Manager to Back Up Databases.You can order publications through your IBM representative or the IBM branchoffice serving your locality. You can also search for and order books of interest toyou by visiting the IBM Redbooks home page on the World Wide Web at thisaddress: http://www.redbooks.ibm.com.

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

http://www.redbooks.ibm.com

Chapter 1. Storage Agent Overview

Managed System for SAN is a feature of IBM Tivoli Storage Manager (StorageManager) that enables LAN-free Storage Manager client data movement. TheStorage Manager client data moves directly to and from a storage device attachedto a Storage Area Network (SAN), thereby off-loading the data movement from theLAN and from the Storage Manager server. The storage agent is installed on theclient machine and shares storage resources with the Storage Manager server. Thestorage agent can write directly to storage media in a format that is consistent withthat used by the server. The Storage Manager server or servers control the storagedevices and keep track of the data that the client has stored. Storage Managercontinues to use a LAN connection to exchange control information, such as policyinformation and data about the objects that are backed up. Using the SAN forclient data movement decreases the load on the Storage Manager server and allowsthe server to support a greater number of simultaneous client connections. SeeFigure 1.

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

ClientStorage Agent installed

Tape Library

File Library

Library ControlClient Metadata

LibraryControl

ClientData

SAN

LAN

Storage Manager Server

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

© Copyright IBM Corp. 2000, 2002 1

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

Storage Manager supports SAN-attached device sharing in one of the followingways:v Storage Manager 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 enablesStorage Manager to share ACSLS-managed libraries. In this environment thedevice sharing capability is provided by third-party software, such as GreshamExtended Data Technology DistribuTAPE (EDT-DistribuTAPE) a middlewaresoftware program that takes advantage of Storage Manager’s external libraryinterface to allow tape drives in ACSLS-managed libraries to be shared amongStorage Manager servers.

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

LAN-free Client Data Backup ScenarioThe following outlines a typical backup scenario for a Storage Manager client thatuses SAN data movement. This scenario does not apply to External libraryenvironments.1. The client begins a backup operation. The client and the server exchange policy

information over the LAN to determine the destination of the backed up data.For a client using LAN-free data movement, the destination is a storage poolthat uses a device on the SAN. That device must also have a defined pathbetween the device and the storage agent.

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

3. The server contacts the storage device and mounts the appropriate media.4. The server notifies the client of the location where the mounted media resides.5. The client, by means of the storage agent, writes the backup data directly to the

device over the SAN.6. The storage agent sends file attribute information to the Storage Manager

server, and the server stores the information in its database.

Dual-session No-Query Restore for LAN-free PathWhen performing a No-Query restore the Storage Manager server builds a list offiles to restore and sends data to the client while continuing to build the list. Thistype of restore is more efficient, especially in a LAN-free environment, and allowsthe restore to be restarted if interrupted. Two sessions are used for the restorewhen data for the restore resides on devices with a LAN-free path and deviceswith a LAN-only path. One session restores data from the server with a LAN-onlypath. The other session uses the storage agent to restore data over the LAN-freepath. This works only with clients at the 4.2 level or above.

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

Chapter 2. Planning

You can set up a Managed System for SAN in a number of configurations.Planning the system configuration provides a smooth transition through systemsetup and into production. As part of your planning, you need to identify thefollowing:v Which configuration to implementv Devices to be used for LAN-free data movementv Clients to use LAN-free data movementv For tape libraries (except ACSLS-managed StorageTek tape libraries), which

servers, library manager or library client, will manage which client’s data.

Types of ConfigurationsThere are different types of configurations that take advantage of what can beaccomplished using a storage agent in a LAN-free environment. Your environmentis dependent upon the type of storage device you will be using for LAN-free datastorage. The following sections cover descriptions and planning considerations forseveral typical LAN-free environments. These environments are:1. SCSI and 349X Tape Library sharing using the Storage Manager Library

Manager and Client. See “Sharing Tape Storage using Storage Manager LibraryManager/Client”.

2. File device sharing using SANergy. See “Sharing Disk Storage using TivoliSANergy” on page 4.

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

Sharing Tape Storage using Storage Manager LibraryManager/Client

When Storage Manager servers share a SCSI tape or 349X storage device using alibrary manager and library clients, one server, the library manager, owns andcontrols the tape library device. The library manager operations include checkingvolumes into and out of the library, labeling volumes, mounting and dismountingvolumes, auditing volumes, and creating an inventory of library contents. Thelibrary manager also manages the storage hierarchy and performs such serverfunctions as storage pool migrations, reclamation, collocation, and backup andrestore of storage pools and the database. All of the other Storage Manager serverssharing this library are considered library clients. A library client requests sharedlibrary resources, such as drives or media from the Storage Manager server actingas the library manager, but uses the resources independently. The library managercoordinates the access to these resources. Data moves over the SAN between thestorage device and either the library manager or the library client. Either thelibrary manager or any library client can manage the LAN-free movement of clientdata as long as the client system includes a storage agent.

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


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

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

stored on a tape library.v A Storage Manager server library client manages a client’s data, which is stored

on a tape library.

Sharing Disk Storage using Tivoli SANergyWhen Storage Manager servers share access to disk storage, the environmentcontains a FILE library (Storage Manager server File device class) and utilizes theSANergy product. SANergy provides a file sharing accelerator. Because you will beusing a FILE library, you must determine where the Tivoli SANergy client and theTivoli SANergy Metadata Controller (MDC) will be installed. You will also requirea Windows share (CIFS) or a Network File Share (NFS) on a Unix system toachieve file sharing. See Figure 3 on page 5 and Table 1 on page 5 for the possibleTivoli SANergy configurations. See the SANergy publications for additionalinformation about configuring SANergy.

Figure 2. Library Manager/Client LAN—free Configuration


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

Table 1. Tivoli SANergy Configurations

Tivoli SANergyComponent

Where Installed

Tivoli SANergyClient

�1� �2� �1� and �2�

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

External Library — Sharing ACSLS-Managed LibrariesWhen Storage Manager servers share access to ACSLS-managed libraries, thesharing is enabled by middleware (such as Gresham EDT-DistribuTAPE) betweenthe data Storage Manager and a media manager (StorageTek ACSLS). See Figure 4on page 6. The ACSLS Server (or Library Station) manages the physical aspects of

tape cartridge storage and retrieval. The external library manager, in thisdiscussion Gresham EDT, communicates with the ACSLS Server or LibraryStationto access tape cartridges in an automated StorageTek library. The storage agentinstalled on a machine containing Gresham EDT and a Storage Manager or TivoliData Protection (TDP) client provides access to SAN-attached storage devicesresulting in LAN-free data movement. The continued connection to the LAN

TSM ClientStorage Agent

TSM Server

Another Node

LAN

SAN

FILE Library

1

2

3

Figure 3. Tivoli SANergy Configurations

Chapter 2. Planning 5

provides a meta data (control information) path. If the storage agent is notavailable, the LAN provides a failover path for data backup and recovery.

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

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

v Table 2 on page 7 lists which Linux distributions and the minimum vendorkernel levels that the Linux storage agent server supports.

LAN

SAN

1234

LAN-freeData

Movement

1 2 3 4

Tivoli StorageManagerServer

GreshamEDT

Data Owner

Tivoli StorageManager

Client

GreshamEDT

StorageAgent

STK Tape Library

ChangerControl

ChangerControl

3270ChangerControl

Tape Drives

TCP/IP CommunicationFibre Channel3270 Communications-Library Control Commands

Library Manageron

z/OS

ACSLSServer

or

Figure 4. External Library Environment



Table 2. Minimum Vendor Kernel Levels

Linux Distribution OS Level Kernel Level Architecture

Red Hat 7.2 2.4.9–31 SMP,UP IA32 or IA64

SuSE Enterprise Server 7 2.4.18 SMP, UP IA32

v Version 2.2.4 or higher of the GNU libc libraries is installed on the storage agentmachine.

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

v TCP/IP is required for communication among the Storage Manager server, theclient, and the storage agent.

v An IBM Tivoli Storage Manager server with the storage agent feature (version5.1.0 or higher). The server and the storage agent must be at the same version,release, and maintenance level. The Storage Manager servers for the AIX,HP-UX, Linux, Sun Solaris, and Windows operating systems support theManaged System for SAN feature.

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

v A IBM Tivoli Storage Manager storage agent. The storage agent must beinstalled on the same system as the client software. Also, the storage agent mustbe at the same level as the server with which it communicates (includingmaintenance (PTF) level). You can download the latest PTF from the Tivoli Website at http://www.tivoli.com/support/storage_mgr/tivolimain.html.

v The Storage Manager application program interface (API) software must be atversion 5.1 or higher. You can obtain the API by downloading the latest versionof the backup-archive client for Linux from the Web site athttp://www.tivoli.com/support/storage_mgr/tivolimain.html.

v If you are sharing disk storage, Tivoli SANergy for Linux 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 that supports Linux must be installed. Foradditional information and product download, see http:www.greshamstorage.com.

Chapter 2. Planning 7

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




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

Chapter 3. Installation and Configuration

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

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

Manager and Clientv File device sharing using SANergy

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

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

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

To begin the installation and configuration process, read the summary of theprocedure, review the complete procedure which follows the summary, and thenperform the steps described in the procedure. The summary itself briefly describesthe overall configuration. It is a good idea to understand the overall process beforebeginning the procedure, since the process takes place on multiple machines atdifferent times. Following the summary is the complete procedure containing thestep-by-step installation and configuration instructions.

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

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

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

Client System:

– Install the Storage Manager client or TDP client, and the Storage ManagerAPI. Specify the LAN-free option

– Install and set up the storage agent

Storage Manager Server:

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


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

v Configuring devices for the storage agent to access

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

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

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

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

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

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

Establishing Communications among Client, Storage Agent, andServer

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

Step 2. Client SystemThe procedures in this step describe installation of the Storage Manager client, API,and storage agent software.

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

User’s Guide for the client. Install the client software and API if it is notalready installed on the system, or upgrade the software to the latest level as



necessary. The latest levels can be downloaded from the IBM Tivoli StorageManager Web site at http://www.tivoli.com/support/storage_mgr/tivolimain.html.

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

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

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

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

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

LANFREECommmethod TCPIPLANFREETCPPort 1500

3. If your are using a TDP client, configure the API by performing the followingprocedure:a. Set up the environment variables. The Storage Manager 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 of how to set up these environment variables.export DSMI_CONFIG=/opt/tivoli/tsm/client/api/bin/dsm.optexport DSMI_DIR=/opt/tivoli/tsm/client/api/binexport DSMI_LOG=/home/user_a/logdir

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

b. Edit the dsm.sys file to specify the communications method between theStorage Manager 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 Storage Manager clientinstallation directory. For example:ln -s /opt/tivoli/tsm/client/ba/bin/dsm.sys /opt/tivoli/tsm/client/api/bin/dsm.sys

2) Edit an existing stanza in the dsm.sys file or create a new stanza tospecify the options for connecting to the Storage Manager server. Forexample:

Chapter 3. Installation and Configuration 11


SErvername tsmsrverCOMMmethod TCPipTCPPort 1502TCPServeraddress tsmsrver.tucson.ibm.com

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

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

servername tsmsrver

Install and Configure the Storage Agent

Note: The Storage Agent should not be installed on the same machine as theStorage Manager server.

On the same system as the client, install the storage agent by performing thefollowing steps. The default installation directory is /opt/tivoli/tsm/Storageagent/bin.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 definethe storage agent as a server to the Storage Manager server. For example:– Name: storagnt– Password: fun4me– TCP/IP address: agent.tucson.ibm.com

v Storage Manager server: Information about the Storage Manager server thatthe storage agent will need in order to communicate with the server. This isthe same Storage Manager server with which the client communicates. Forexample:– Name: tsmsrver– Password: not4u– TCP/IP address: tsmsrver.tucson.ibm.com– TCP/IP port: 1502

Notes:

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

b. The ’Server Password Set’ displayed in the QUERY STATUS output mustbe equal to YES and for this example the password is set to not4u. To setthe server password issue the SET SERVERPASSWORD command from aStorage Manager administrative command-line. For example:set serverpassword not4u

2. Log in as the root user.3. Verify that version 2.2.4 or higher of the GNU libc libraries is installed.4. Insert the storage agent CD-ROM into a CD-ROM drive. The following

discussion assumes that the CD-ROM is mounted on directory /mnt/cdrom.5. See the README.STA file on the CD-ROM for changes to the installation

procedure.6. Use the rpm command to install the storage agent packages. For example:


rpm -ivh <packagename>

Where packagename is one or more package names (separated by a space) listedin Table 3.

Table 3. Storage Agent PackagesPackage: Installs:TIVsm-stagent-5.1.5-0.i386.rpm Storage agent (32 bit)TIVsm-stagent-5.1.5-0.ia64.rpm Storage agent (64 bit)TIVsm-license-5.1.5-0.i386.rpm License enabler for Intel x86 (32 bit)TIVsm-license-5.1.5-0.ia64.rpm License enabler for Intel x86 (64 bit)TIVsm-license_keys-5.1.5-0.noarch.rpm

License keys for various licensed features

TIVsm-tsmscsi-5.1.5-0.i386.rpm TSM SCSI device drivers and utilities (32 bit)TIVsm-tsmscsi-5.1.5-0.ia64.rpm TSM SCSI device drivers and utilities (64 bit)

7. When the installation is finished, remove the CD from the drive.8. Ensure that the DEVCONFIG option is specified in the dsmsta.opt file. If not,

edit the dsmsta.opt file, which is located in/opt/tivoli/tsm/Storageagent/bin, andenter the following line:DEVCONFIG devconfig.out

Note: devconfig.out is an example of a device configuration file name.9. Use the information that you collected in step 1 on page 12 to issue the

DSMSTA SETSTORAGESERVER command. For example:dsmsta setstorageserver myname=storagnt mypassword=fun4me

myhladdress=agent.tucson.ibm.comservername=tsmsrver serverpassword=not4uhladdress=tsmsrver.tucson.ibm.com lladdress=1502

Note: The hladdress must match the TCPServeraddress located in the dsm.sysfile on the Storage Manager client.

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

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

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

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

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

SERVERNAME tsmsrver

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


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

storage agent to the Storage Manager server as if the storage agent is a server.You must use the same name and password that you set for the storage agentwhen you installed it on the client system. The DEFINE SERVER commandmust be issued from the Storage Manager server (library manager or libraryclient) that will manage the client’s data. For example:define server storagnt serverpassword=fun4mehladdress=agent.tucson.ibm.com lladdress=1500 validateprotocol=all

Note: The VALIDATEPROTOCOL parameter in the previous example isoptional. This parameter determines whether a cyclic redundancy checkshould be performed to validate data on all metadata transferredbetween the storage agent and the Storage Manager server. See theAdministrator’s Reference for additional information about the DEFINESERVER command. See the Administrator’s Guide for additionalinformation about data validation.

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

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

Disk Device

Configure Enterprise Management and define a device class of DEVTYPE=FILEand SHARED=YES. Storage Manager automatically defines a new FILE libraryand also defines drives corresponding to the mount limit for the FILE deviceclass. The FILE library name is the same as the device class name. Each driveuses the library name with a numeric suffix. If the mount limit is changed, thenumber of drives also changes.

Note: Because each session gets exclusive access to a file volume, the mountlimit 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 clientmust use a management class that has copy groups with a destination storagepool.The destination storage pool must be associated with the library. The librarymust be the one on which drive paths have been defined. For example, do thefollowing:a. Create a policy domain for clients that will use the SAN devices for direct

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

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


Note: If you decide not to use the default management class for the SANdrives, you will need to create a new management class. Clients thatwant to use the SAN drives need to use an include statement to bindtheir files to this new management class. See Backup-Archive ClientsInstallation and User’s Guide for details on the include-exclude list.

d. Activate the policy set.e. Register or update the client nodes so that they are in the new policy

domain.

See Administrator’s Guide for details on changing policy for clients that can useSAN drives. For details about the commands, see Administrator’s Reference.

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

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

TSM Client Workstation

Client - DATAOWNER

Storage Agent - STORAGNT

TSM Server - TSMSRVER

dsm.sys file

dsmsta.opt file

define server serverpassword=fun4me

hladdress=agent.tucson.ibm.com

lladdress=1500

register node bak2work

domain=sandomain

storagnt

dataowner

devconfig.out file

set staname storagnt

set stapassword xxxxxxx

set stahladdress agent.tucson.ibm.com

define server serverpassword=xxxxxxxx

hladdress=tsmsrver.tucson.ibm.com

lladdress=1502

tsmsrver

servername

devconfig

tsmsrver

devconfig.out

enablelanfree yes

lanfreecommmethod tcpip

lanfreetcpport 1500

tcpserveraddress .tucson.ibm.com

tcpport 1502

tsmsrver

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


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

Step 4. Client System

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

Tape DevicesPerform the following:

Obtain Tape Device Information: Obtaining tape device information in a Linuxenvironment is different depending on whether your environment supports IBMdevices or non-IBM devices as follows:

IBM Tape Devices: After installing and loading the IBMtape device driver for yourIBM tape and SCSI tape drives and libraries, a set of special file names areavailable for each device. To see the special file names, use the command:

ls /dev/IBM*

The name for tape drives typically has the form:

/dev/IBMtapex

where x is a number.

The name for tape libraries typically has the form:

/dev/IBMchangerx


Non-IBM Tape Devices: To use the Storage Manager device drivers, you mustperform the following:1. Verify that the device is connected to your system, and is powered on and

active2. Ensure that the Storage Manager device driver package is loaded. (Depending

on your system environment you will load one of the following, eitherTIVsm-tsmscsi-5.1.5-0.i386.rpm for 32 bit or TIVsm-tsmscsi-5.1.5-0.ia64.rpm for64 bit).

Note: To load the device driver, enter ./tsmscsi from the install location of theStorage Manager device driver.

3. Copy the two sample configuration files located in the installation directoryfrom lb.conf.smp and mt.conf.smp to lb.conf and mt.conf, respectively.

4. Edit the lb.conf and mt.conf files. Add one stanza (as shown in the example atthe top of the file) for each SCSI target ID and LUN combination you want thedevice driver to probe for supported tape drives.

5. To load the device driver, run the tsmscsi script from the device driverinstallation directory.

6. Determine the special file names for the tape drives and libraries.


The special file for each tape drive and library appears in the /dev/tsmscsidirectory. The tape drive special file has the form /dev/tsmscsi/mtx, where x isa number. The library special file has the form /dev/tsmscsi/lbx, where x is anumber. To determine the names for the tape drives, issue the followingcommand:

> ls /dev/tsmscsi/mt*

To determine the names for the libraries issue the following command:

> ls /dev/tsmscsi/lb*

Step 5. ServerThe following provides information to help you define paths from the storageagent to the drives that are available to the Storage Manager server. Paths allow aclient, by means of a storage agent, access to drives in a library. The requirementsare different depending on the device you are using.

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

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

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

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

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

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

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

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

For example, you would issue the following:define path storagnt drive1 srctype=server desttype=drivelibrary=sanlib1 device=/dev/mt1


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

Depending on the operating system of the Storage Manager server, there may notbe a quick way to confirm which device names on the storage agent correspond todevice names on the Storage Manager server without using a trial and errormethod. To confirm device names, you should work with one online drive at atime, and cycle through the storage agent device names until a successful backupcan be run.

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

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

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

For command information, see the Administrator’s Reference.

The following figure displays the results of completing steps three, four and fivefor a tape device.

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


SAN


Storage Agent

device name: /dev/tsmscsi/mt1

Tape Library Drive

define drive sanlib1 drive1

define path tsmsrver drive1 srctype=server

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

define path storagnt drive1 srctype=server

destype=drive library=sanlib1

device=/dev/tsmscsi/mt1

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


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

When the storage agent starts, it determines if the Storage Manager server is alibrary client or library manager. If the server is a library client, the storage agentdefines itself to the library manager.

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

using a Storage Manager Administrative Command Line client to login to theStorage Manager server and storage agent to verify the proper sessions havebeen established. When LAN-free data movement is occurring, a QUERYSESSION on the storage agent should show bytes received (displayed as BytesRecvd) for the node increasing to the total amount of data being backed up.The QUERY SESSION on the Storage Manager server should show a very smallamount of bytes received (metadata) for the same node. If the node’s sessionexhibits this behavior, and you receive a message stating that the backup hasbeen successful, you have configured your system correctly.

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

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

a. The Storage Manager server is running. If the Storage Manager server is notrunning, the storage agent will not start.

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

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

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

LAN-free backup. Review the Bytes Sent and Bytes Received. You can performthis action by using a Storage Manager administrative command-line client tologin to the Storage Manager server and storage agent to verify the propersessions have been established. When LAN-free data movement is occurring, aQUERY SESSION on the storage agent should show bytes received (displayed asBytes Recvd) for the node increasing to the total amount of data being backedup. The QUERY SESSION on the Storage Manager server should show a verysmall amount of bytes received (metadata) for the same node. If the node’ssession exhibits this behavior, the data movement is LAN-free.

v Issue either of the following QUERY ACTLOG commands on the server towhich the client is connected:query actlog search=storage_agent_name msgno=8337

or


query actlog search=storage_agent_name

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

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

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

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

v Establishing communications and configuring the client, storage agent, andStorage Manager server

Client System:

– Install the Storage Manager client or TDP client, and the Storage ManagerAPI. Specify the LAN-free option

– Install and set up the storage agent

Storage Manager 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 2 — External Library Environment with an ACSLS–ManagedLibrary

If you will be using a Tivoli storage agent with ACSLS-managed libraries, youmust have the ACSLS software and the third-party external library software (suchas Gresham EDT-DistribuTAPE) installed and configured. See the StorageTekACSLS and the Gresham EDT documentation for installation instructions. SeeFigure 4 on page 6 for an example of a storage agent in an ACSLS-managed libraryenvironment. Complete the following steps to configure your storage agentexternal library environment:

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

The Managed System for SAN feature requires specific levels and models ofhardware and software. Ensure that your system configuration meets the 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 twosteps, see Figure 7 on page 27.

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

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

Install or Upgrade the Client and API Software:

1. Check that the client system meets the prerequisites for client software. See theUser’s Guide for the client. Install the client software and API if it is notalready installed on the system, or upgrade the software to the latest level asnecessary. The latest levels can be downloaded from the IBM Tivoli StorageManager 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 ClientsInstallation and User’s Guide.a. Edit the dsm.sys file to specify the communications method between the

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

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

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

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

LANFREECommmethod TCPIPLANFREETCPPORT 1500

3. If you are using a TDP client, configure the API by performing the followingprocedure:a. Set up the environment variables. The Storage Manager 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=/opt/tivoli/tsm/client/api/bin/dsm.optexport DSMI_DIR=/opt/tivoli/tsm/client/api/binexport DSMI_LOG=/home/user_a/logdir

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

b. Edit the dsm.sys file to specify the communications method between theStorage Manager 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 Storage Manager clientinstallation directory. For example:ln -s /opt/tivoli/tsm/client/ba/bin/dsm.sys /opt/tivoli/tsm/client/api/bin/dsm.sys

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

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

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

servername tsmsrver

Install and Configure the Storage Agent:

Note: The Storage Agent should not be installed on the same machine as theStorage Manager server.

On the same system as the client, install the storage agent by performing thefollowing steps. The default installation directory is /opt/tivoli/tsm/StorageAgent/bin.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 todefine the storage agent as a server to the Storage Manager server. Forexample:– Name: storagnt– Password: fun4me– TCP/IP address: agent.tucson.ibm.com

v Storage Manager server: Information about the Storage Manager server thatthe storage agent will need in order to communicate with the server. This isthe same Storage Manager server with which the client communicates. Forexample:– Name: tsmsrver– Password: not4u– TCP/IP address: tsmsrver.tucson.ibm.com– TCP/IP port: 1502– Tape Library Name: stk-lib


Notes:

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

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

2. Log in as the root user.3. Verify that version 2.2.4 or higher of the GNU libc libraries is installed.4. Insert the storage agent CD-ROM into a CD-ROM drive. The following

discussion assumes that the CD-ROM is mounted on directory /mnt/cdrom.5. See the README.STA file on the CD-ROM for changes to the installation

procedure.6. Use the rpm command to install the storage agent packages. For example:

rpm -ivh <packagename>

Where packagename is one or more package names (separated by a space)listed in Table 4.

Table 4. Storage Agent PackagesPackage: Installs:TIVsm-stagent-5.1.5-0.i386.rpm Storage agent (32 bit)TIVsm-stagent-5.1.5-0.ia64.rpm Storage agent (64 bit)TIVsm-license-5.1.5-0.i386.rpm License enabler for Intel x86 (32 bit)TIVsm-license-5.1.5-0.ia64.rpm License enabler for Intel x86 (64 bit)TIVsm-license_keys-5.1.5-0.noarch.rpm

License keys for various licensed features

TIVsm-tsmscsi-5.1.5-0.i386.rpm Storage Manager SCSI device drivers and utilities(32 bit)

TIVsm-tsmscsi-5.1.5-0.ia64.rpm Storage Manager SCSI device drivers and utilities(64 bit)

7. When the installation is finished, remove the CD from the drive.8. Ensure that the DEVCONFIG option is specified in the dsmsta.opt file. If not,

edit the dsmsta.opt file, which is located in /opt/tivoli/tsm/StorageAgent/bin andenter the following line:DEVCONFIG devconfig.out

Note: devconfig.out is an example of a device configuration file name.9. Use the information that you collected in step 1 on page 22 to issue the

DSMSTA SETSTORAGESERVER command. For example:dsmsta setstorageserver myname=storagnt mypassword=fun4memyhladdress=agent.tucson.ibm.comservername=tsmsrver serverpassword=not4uhladdress=tsmsrver.tucson.ibm.com lladdress=1502

Notes:

a. The Storage Manager server, in this example TSMSRVER, must be runningwhen the DSMSTA SETSTORAGESERVER command is issued.

b. The hladdress must match the TCPServeraddress located in the dsm.sysfile on the Storage Manager client.


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

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

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


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

SERVERNAME tsmsrver

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

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

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

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

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

The resulting device configuration file would appear as:

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

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

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

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


Step 3. IBM Tivoli Storage Manager ServerThe following provides the steps that you need to perform on the Storage Managerserver. If further explanation is required, see Administrator’s Guide.1. Install Gresham EDT or other middleware 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 client’s

storage agent to the Storage Manager server as if the storage agent is a server.You must use the same name and password that you set for the storage agentwhen you installed it on the client system. The DEFINE SERVER commandmust be issued from the Storage Manager server that will manage the client’sdata. For example:define server storagnt serverpassword=fun4mehladdress=agent.tucson.ibm.com lladdress=1500 validateprotocol=all

Note: The VALIDATEPROTOCOL parameter in the previous example isoptional. This parameter determines whether a cyclic redundancy checkshould be performed to validate data on all metadata transferredbetween the storage agent and the Storage Manager server. See theAdministrator’s Reference for additional information about the DEFINESERVER command. See the Administrator’s Guide for additionalinformation 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. GreshamEDT-DistribuTape is the external library manager interfacing with theACSLS library software. The EDT executable is located in its default path/usr/dtelm/bin/elm. For example:define path tsmsrver stk-lib srctype=server desttype=libraryexternalmanager=/usr/dtelm/bin/elm

In the previous example the path provided for the external manager isdependent upon the operating system where the Storage Manager serverresides. For example, a Linux Storage Manager server external managerpath is /usr/dtelm/bin/elm in contrast to a Storage Manager Sun serverexternal manager path of /opt/OMIdtelm/bin/elm or a Storage ManagerWindows server external manager path of c:\programfiles\GES\EDT\bin\elm.exe. For additional information about the DEFINEPATH command, see the Administrator’s Reference.

c. Define a device class with a device type of ECARTRIDGEd. 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 use the drives on the SAN. The clientmust use a management class that has copy groups with a destination storagepool.The destination storage pool must be associated with the library. The librarymust be the one on which drive paths have been defined. For example, do thefollowing:a. Create a policy domain for clients that will use the SAN devices for direct

data transfer.b. Create a policy set in that domain.


c. In the default management class for that policy set, modify the copy groups.Set the destination storage pool to the storage pool associated with the SANdrives that you configured.

Note: If you decide not to use the default management class for theexternal library, you will need to create a new management class.Clients that want to use the SAN attached library need to use aninclude statement to bind their files to this new management class.See Backup-Archive Clients Installation and User’s Guide for details onthe include-exclude list.

d. Activate the policy set.e. Register or update the client nodes so that they are in the new policy

domain.

See Administrator’s Guide for details on changing policy for clients that can useSAN drives. For additional command information, see Administrator’s Reference.

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

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


Configuring Devices for the Storage Agent to Access

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

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

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

using a Storage Manager Administrative Command Line client to login to theStorage Manager server and storage agent to verify the proper sessions have


Client - DATAOWNER

Storage Agent - STORAGNT


dsm.sys file

dsmsta.opt file

define server serverpassword=fun4me

hladdress=agent.tucson.ibm.com

lladdress=1500

register node bak2work

domain=sandomain

storagnt

dataowner

devconfig.out file

set staname storagnt

set stapassword xxxxxxx

set stahladdress agent.tucson.ibm.com

define server serverpassword=xxxxxxxx

hladdress=tsmsrver.tucson.ibm.com

lladdress=1502

tsmsrver

servername

devconfig

tsmsrver

devconfig.out

enablelanfree yes

lanfreecommmethod tcpip

lanfreetcpport 1500

tcpserveraddress .tucson.ibm.com

tcpport 1502

tsmsrver

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


been established. When LAN-free data movement is occurring, a QUERYSESSION on the storage agent should show bytes received (displayed as BytesRecvd) for the node increasing to the total amount of data being backed up.The QUERY SESSION on the Storage Manager server should show a very smallamount of bytes received (metadata) for the same node. If the node’s sessionexhibits this behavior, and you receive a message stating that the backup hasbeen successful, you have configured your system correctly.

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

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

a. The Storage Manager server is running. If the Storage Manager server is notrunning, the storage agent will not start.

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

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

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

LAN-free backup. Review the Bytes Sent and Bytes Received. You can performthis action by using a Storage Manager administrative command-line client tologin to the Storage Manager server and storage agent to verify the propersessions have been established. When LAN-free data movement is occurring, aQUERY SESSION on the storage agent should show bytes received (displayed asBytes Recvd) for the node increasing to the total amount of data being backedup. The QUERY SESSION on the Storage Manager server should show a verysmall amount of bytes received (metadata) for the same node. If the node’ssession exhibits this behavior, the data movement is LAN-free.

v Issue either of the following QUERY ACTLOG commands on the server towhich the client is connected:query actlog search=storage_agent_name msgno=8337

orquery actlog search=storage_agent_name

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

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


Appendix A. Administration and Configuration Reference

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

Starting and Stopping the Storage AgentStart the storage agent as follows:v Reboot the client systemv From the operating system command line, change to the storage agent directory

and issue the following command:dsmsta

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

Obtaining Tape Device Information on the Client SystemHow you obtain tape device information depends on whether the devices are IBMor non-IBM.

IBM Tape DevicesAfter installing and loading the IBMtape device driver for your IBM tape and SCSItape drives and libraries, a set of special file names are available for each device.To see the special file names, use the command:

ls /dev/IBM*

The name for tape drives typically has the form:

/dev/IBMtapex


The name for tape libraries typically has the form:

/dev/IBMchangerx


Non-IBM Tape DevicesTo use the Storage Manager device drivers, you must perform the following:1. Verify that the device is connected to your system, and is powered on and

active2. Ensure that the Storage Manager device driver package is loaded. (Depending

on your system environment you will load one of the following, eitherTIVsm-tsmscsi-5.1.5-0.i386.rpm for 32 bit or TIVsm-tsmscsi-5.1.5-0.ia64.rpm for64 bit).


Note: To load the device driver, enter ./tsmscsi from the install location of theStorage Manager device driver.

3. Copy the two sample configuration files located in the installation directoryfrom lb.conf.smp and mt.conf.smp tolb.conf and mt.conf, respectively.

4. Edit the lb.conf and mt.conf files. Add one stanza (as shown in the example atthe top of the file) for each SCSI target ID and LUN combination you want thedevice driver to probe for supported tape drives.

5. To load the device driver, run the tsmscsi script from the device driverinstallation directory.

6. Determine the special file names for the tape drives and libraries.The special file for each tape drive and library appears in the /dev/tsmscsidirectory. The tape drive special file has the form /dev/tsmscsi/mtx, where x isa number. The library special file has the form /dev/tsmscsi/lbx, where x is anumber. To determine the names for the tape drives, issue the followingcommand:

> ls /dev/tsmscsi/mt*

To determine the names for the libraries issue the following command:

> ls /dev/tsmscsi/lb*


Set Installation Data for the Storage Agent: DSMSTASETSTORAGESERVER

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

This utility does not remove any previous entries in the files. It appendsinformation to the existing files. The option devconfig, which sets a name for thedevice configuration file, must exist in the dsmsta.opt file for the command towork. See the example for details on the information that the command adds.

Format

@@ DSMSTA SETSTORAGESERVER MYName = storage_agent_name @

@ MYPAssword = storage_agent_password @

@ MYHLAddress = storage_agent_hladdress SERVERName = server_name @

@ SERVERPAssword = server_password HLAddress = server_tcpip_address @

@ LLAddress = server_tcpip_port @A

ParametersAll parameters are required.

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

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

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

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

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

SERVERNameSpecifies the name of the Storage Manager server. This name appears in theDEFINE SERVER command that is inserted into the device configuration file.

SERVERPAsswordSpecifies the password of the server. This value is encrypted and appears in

Appendix A. Administration and Configuration Reference 31

the SERVERPASSWORD field of the DEFINE SERVER command that isinserted into the device configuration file.

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

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

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

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

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

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

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

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


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

SERVERNAME tsmsrver


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

Normally you do not need to make any changes to the options file unless yourStorage Manager server changes. The required options are:

SERVERName server_nameThe name of the Storage Manager server with which the storage agentcommunicates. The DSMSTA SETSTORAGESERVER command inserts thisoption.

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

The following options are also available, but not required:

RESOURCETimeout minutesSpecifies the maximum number of minutes that a storage agent waits for aresource on the server. The default value is 10 minutes. The minimumvalue is 1 minute. This parameter is optional.

STAMaxpooledsessions numberThe number of sessions that the storage agent keeps open to the StorageManager server. The default value is 25. Possible values are 0 to 150. If thestorage agent needs more sessions than specified, additional sessions areconsidered temporary and close when the transaction is complete.

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

The Device Configuration File for the Storage AgentThe device configuration file for the storage agent includes information on thestorage agent itself and information about the Storage Manager server with whichthe storage agent communicates. The file is typically named devconfig and is withthe storage agent program at this location: /opt/tivoli/tsm/Storageagent/bin. TheDSMSTA SETSTORAGESERVER command normally generates the contents of thefile. If you have changes to the Storage Manager server or if a servicerepresentative directs you, you may need to make changes to the information. Youcan use the DSMSTA SETSTORAGESERVER command to add information to thefile.

Typical contents of the device configuration file are as follows:

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

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

The following describes the contents of the file:

Appendix A. Administration and Configuration Reference 33

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

SET STAPASSWORDSets the password of the storage agent. The password must be the same asthe password that was used when defining the storage agent as a server tothe Storage Manager server. The password is encrypted.

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

DEFINE SERVERThe definition of the Storage Manager server with which the storage agentcommunicates.


Appendix B. Notices

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

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

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

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

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

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

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

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

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


Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

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

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

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

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

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

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

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

AIXIBMIBMLink

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

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

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

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


Glossary

AACSLS. Automated cartridge system library software.

application client. One of the Tivoli Data Protectionfor application programs installed on a system. TheIBM Tivoli Storage Manager server provides backupservices to these clients.

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

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

Bback up. To copy information to another location toensure against loss of data. In IBM Tivoli StorageManager, you can back up user files, the IBM TivoliStorage Manager database, and storage pools. Contrastwith restore.

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

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

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

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

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

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

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

dsm.opt file. See client options file.

dsmserv.opt. See server options file.

dsmsta.opt. See storage agent options file.

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

The terms in this glossary are defined as they pertain to the IBM Tivoli Storage Manager library. If you do not findthe 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 IBM Tivoli StorageManager glossary, see Administrator’s Guide.

This glossary may include terms and definitions from:

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

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


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

movement for ACSLS-managed StorageTek libraries. Toactivate this support the IBM Tivoli Storage Managerlibrary type must be EXTERNAL.

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

LLAN. Local area network.

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

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

library manager. A IBM Tivoli Storage Manager serverthat controls device operations when multiple IBMTivoli Storage Manager servers share a storage device.The device operations include mount, dismount,volume ownership, and library inventory.

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

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

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

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

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

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

restore. To copy information from its backup locationto the active storage location for use. In IBM TivoliStorage Manager, you can restore the server database,storage pools, storage pool volumes, and users’backed-up files. The backup version in the storage poolis not affected by the restore operation. Contrast withbackup.

SSAN. Storage area network.

SCSI. Small computer system interface.

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

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

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

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

storage agent. A program that enables IBM TivoliStorage Manager to back up and restore client datadirectly to and from SAN-attached storage.

storage agent options file. A file that specifies optionsfor the storage agent. This includes the name of theIBM Tivoli Storage Manager server with which thestorage agent communicates, the number of sessionsthat can be kept open to the server, and the name ofthe device configuration file. Also called the dsmsta.optfile.

storage pool. A named set of storage volumes that isthe destination that the IBM Tivoli Storage Managerserver uses to store client data. The client data consistsof backup versions, archive copies, and migrated files.You can back up a primary storage pool to a copystorage pool.


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

Glossary 39

Index

AACSLS support 5, 20

Ddata movement, SAN

prerequisites 6tasks 9

device configuration file 33disk device

SANergy 2.2 10server install 14

dsm.opt file 11, 21DSMSTA SETSTORAGESERVER 13, 23dsmsta.opt 13, 24, 33

Eenablelanfree option 11, 21external library support 5, 20

FFILE library

configuration considerations 4disk devices 14

Hhow to determine LAN-free data movement 19, 28

LLAN-free data movement

enabling, dsm.opt 11, 21guidelines for determining 19, 28

library client 3library manager 3limit the SAN drives 17

MManaged System for SAN

description 1FILE library 4planning configurations 3policy considerations 14, 25SANergy Metadata Controller 4

Nnetwork requirements 10, 20no-query restore 2

Oobtaining tape device information 16option, enablelanfree 11, 21options file

client 11, 21storage agent 13, 24, 33

Ppath

defining 17disk devices 18tape devices 17

policy for Managed System for SAN 14, 25

SSAN data movement

prerequisites 6tasks 9

storage agentcomponent configuration 6configuring device access 16device configuration file 33installing 12, 22options file 33starting 19, 27usage requirements 6verify configuration 19, 27

Ttape device information, obtaining 16TSM API

install 11, 21upgrade 11, 21


Program Number: 5698-ISE

Printed in U.S.A.

GC23-4693-00

ibm tivoli storage manager for linux: managed …publib.boulder.ibm.com › tividd › td › itsml...

Documents