IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent

IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent
Tivoli Storage Manager for SAN for Sun Solaris
®
Version 6.1
Storage Agent User’s Guide
SC23-9800-00
Tivoli Storage Manager for SAN for Sun Solaris
®
Version 6.1
Storage Agent User’s Guide
SC23-9800-00
Note
Before using this information and the product it supports, read the information in “Notices” on page 57.
This edition applies to Version 6.1 of IBM Tivoli Storage Manager for Storage Area Networks and to all subsequent
releases and modifications until otherwise indicated in new editions or technical newsletters.
© Copyright International Business Machines Corporation 2000, 2009.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Preface . . . . . . . . . . . . . . . v
Who should read this guide . . . . . . . . . v
Publications . . . . . . . . . . . . . . v
Tivoli Storage Manager publications . . . . . v
Support information . . . . . . . . . . . vii
Getting technical training . . . . . . . . viii
Searching knowledge bases . . . . . . . . viii
Contacting IBM Software Support . . . . . . ix
Conventions used in this publication . . . . . . xi
New for Tivoli Storage Manager for
Storage Area Networks Version 6.1 . . xiii
Chapter 1. Storage agent overview . . . 1
Scenario: LAN-free client data backup . . . . . . 3
Scenario: Multi-session no-query restore for LAN-free
path . . . . . . . . . . . . . . . . . 4
Communications between the client, storage agent,
and Tivoli Storage Manager server . . . . . . . 4
Chapter 2. Planning for storage agent
installation and configuration . . . . . 5
Supported operating systems . . . . . . . .
Storage devices and the configuration of your
environment . . . . . . . . . . . . .
ACSLS, SCSI, and 349X tape library sharing . .
File device sharing using Tivoli SANergy . . .
External Libraries . . . . . . . . . .
System requirements . . . . . . . . . .
Obtaining system configuration information for
clients and servers . . . . . . . . . . .
Client-system and server-system configuration
work sheets . . . . . . . . . . . .
Obtaining device information . . . . . .
Verifying and updating client node information
. 6
. 6
. 6
. 9
. 10
. 12
© Copyright IBM Corp. 2000, 2009
29
29
29
30
Chapter 4. Installing and configuring
external library environments . . . . . 33
Establishing network connections . . . . . .
Installing software on UNIX and Linux client
systems. . . . . . . . . . . . . . .
Installing or upgrading the client and API . .
Installing and configuring the storage agent .
Defining the storage agent and configuring devices
on the server . . . . . . . . . . . . .
Setting up server-to-server communication . .
Installing an external media manager . . . .
Defining storage agents to the Tivoli Storage
Manager server . . . . . . . . . . .
Configuring a path to the library manager . .
Defining paths for ACSLS . . . . . . .
Setting the LAN-free destination . . . . .
Confirming client node registration and
configuration . . . . . . . . . . . .
Verifying the LAN-free configuration . . . . .
Verifying the LAN-free configuration . . . .
Determining whether the data movement was
LAN-free . . . . . . . . . . . . . .
Determining whether the data movement was
LAN-free . . . . . . . . . . . . .
. 33
. 34
. 34
. 35
. 37
. 37
. 38
.
.
.
.
38
38
39
40
. 40
. 41
. 41
. 41
. 42
. 13
. 14
. 17
18
Chapter 3. Installing and configuring
tape-library and file-device-sharing
environments . . . . . . . . . . . . 19
Establishing network connections . . . . . .
Installing software on Sun Solaris client systems .
Installing or upgrading the client and API . .
Installing and configuring the storage agent .
Defining the storage agent and configuring devices
on the server . . . . . . . . . . . . .
Setting up server-to-server communication . .
Defining storage agents to the Tivoli Storage
Manager server . . . . . . . . . . .
Configuring SAN drives . . . . . . . .
Setting the LAN-free destination . . . . .
Confirming client node registration and
configuration . . . . . . . . . . . .
Defining paths from the storage agent to drives .
Defining paths for tape devices . . . . . .
Defining paths for disk devices . . . . . . .
(z/OS data-manager server) Formatting volumes for
LAN-free data movement. . . . . . . . . .
Verifying the LAN-free configuration . . . . . .
Determining whether the data movement was
LAN-free . . . . . . . . . . . . . . .
.
.
.
.
19
20
20
22
Appendix A. Administration and
configuration information. . . . . . . 43
Starting and stopping the storage agent . . . . .
Automating the storage agent startup . . . .
Manually starting and stopping the storage agent
Setting up LAN-free data movement using the
Administration Center wizard . . . . . . . .
Configuring multiple clients to use the same storage
agent . . . . . . . . . . . . . . . .
DSMSTA SETSTORAGESERVER . . . . . . .
The storage agent options file . . . . . . . .
The device configuration file for the storage agent
43
43
43
44
44
45
47
50
. 24
. 24
Appendix B. ACSLS legacy data
migration and coexistence . . . . . . 53
. 25
. 25
. 26
Appendix C. Accessibility features for
Tivoli Storage Manager. . . . . . . . 55
. 26
. 27
. 28
Notices . . . . . . . . . . . . . . 57
Trademarks .
.
.
.
.
.
.
.
.
.
.
.
.
. 59
iii
Glossary . . . . . . . . . . . . . . 61
iv
Index . . . . . . . . . . . . . . . 63
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Preface
This publication contains installation and operating instructions for the IBM®
Tivoli® Storage Manager for Storage Area Networks.
Who should read this guide
This guide is for administrators who install and use the storage agent component
of the Tivoli Storage Manager for Storage Area Networks product (referred to as
the storage agent throughout this publication).
It provides:
v An overview of LAN-free data transfer
v Detailed explanations for installing, configuring, and using the Tivoli Storage
Manager client and storage agent, and the Tivoli Storage Manager server)
To use this guide, you must know:
v The operating system on which the server will be installed
v The devices that can use Tivoli Storage Manager
v The workstation operating systems on which the clients reside
v The communication protocols installed on your client and server systems
v Storage area network (SAN) administration
Publications
Tivoli Storage Manager publications and other related publications are available
online.
You can search all publications in the Tivoli Storage Manager Information Center:
http://publib.boulder.ibm.com/infocenter/tsminfo/v6.
You can download PDF versions of publications from the Tivoli Storage Manager
Information Center or from the IBM Publications Center at http://www.ibm.com/
shop/publications/order/.
You can also order some related publications from the IBM Publications Center
Web site. The Web site provides information for ordering publications from
countries other than the United States. In the United States, you can order
publications by calling 800-879-2755.
Tivoli Storage Manager publications
Publications are available for the server, storage agent, client, and Data Protection.
Table 1. Tivoli Storage Manager server publications
Publication title
Order number
IBM Tivoli Storage Manager Messages
GC23-9787
IBM Tivoli Storage Manager Performance Tuning Guide
GC23-9788
IBM Tivoli Storage Manager Problem Determination Guide
GC23-9789
IBM Tivoli Storage Manager for AIX Installation Guide
GC23-9781
© Copyright IBM Corp. 2000, 2009
v
Table 1. Tivoli Storage Manager server publications (continued)
Publication title
Order number
IBM Tivoli Storage Manager for AIX Administrator’s Guide
SC23-9769
IBM Tivoli Storage Manager for AIX Administrator’s Reference
SC23-9775
IBM Tivoli Storage Manager for HP-UX Installation Guide
GC23-9782
IBM Tivoli Storage Manager for HP-UX Administrator’s Guide
SC23-9770
IBM Tivoli Storage Manager for HP-UX Administrator’s Reference
SC23-9776
IBM Tivoli Storage Manager for Linux Installation Guide
GC23-9783
IBM Tivoli Storage Manager for Linux Administrator’s Guide
SC23-9771
IBM Tivoli Storage Manager for Linux Administrator’s Reference
SC23-9777
IBM Tivoli Storage Manager for Sun Solaris Installation Guide
GC23-9784
IBM Tivoli Storage Manager for Sun Solaris Administrator’s Guide
SC23-9772
IBM Tivoli Storage Manager for Sun Solaris Administrator’s Reference
SC23-9778
IBM Tivoli Storage Manager for Windows Installation Guide
GC23-9785
IBM Tivoli Storage Manager for Windows Administrator’s Guide
SC23-9773
IBM Tivoli Storage Manager for Windows Administrator’s Reference
SC23-9779
IBM Tivoli Storage Manager Server Upgrade Guide
SC23-9554
IBM Tivoli Storage Manager for System Backup and Recovery Installation SC32-6543
and User’s Guide
Table 2. Tivoli Storage Manager storage agent publications
Publication title
Order number
IBM Tivoli Storage Manager for SAN for AIX Storage Agent User’s
Guide
SC23-9797
IBM Tivoli Storage Manager for SAN for HP-UX Storage Agent User’s
Guide
SC23-9798
IBM Tivoli Storage Manager for SAN for Linux Storage Agent User’s
Guide
SC23-9799
IBM Tivoli Storage Manager for SAN for Sun Solaris Storage Agent
User’s Guide
SC23-9800
IBM Tivoli Storage Manager for SAN for Windows Storage Agent User’s
Guide
SC23-9553
Table 3. Tivoli Storage Manager client publications
Publication title
Order number
IBM Tivoli Storage Manager for UNIX and Linux: Backup-Archive
Clients Installation and User’s Guide
SC23-9791
IBM Tivoli Storage Manager for Windows: Backup-Archive Clients
Installation and User’s Guide
SC23-9792
IBM Tivoli Storage Manager for Space Management for UNIX and Linux: SC23-9794
User’s Guide
IBM Tivoli Storage Manager for HSM for Windows Administration Guide SC23-9795
vi
IBM Tivoli Storage Manager Using the Application Program Interface
SC23-9793
Program Directory for IBM Tivoli Storage Manager z/OS Edition
Backup-Archive Client
GI11-8912
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Table 3. Tivoli Storage Manager client publications (continued)
Publication title
Order number
Program Directory for IBM Tivoli Storage Manager z/OS Edition
Application Program Interface
GI11-8911
Table 4. Tivoli Storage Manager Data Protection publications
Publication title
Order number
IBM Tivoli Storage Manager for Advanced Copy Services: Data Protection SC33-8331
for Snapshot Devices Installation and User’s Guide
IBM Tivoli Storage Manager for Databases: Data Protection for Microsoft
SQL Server Installation and User’s Guide
SC32-9059
IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for SC32-9064
UNIX and Linux Installation and User’s Guide
IBM Tivoli Storage Manager for Databases: Data Protection for Oracle for SC32-9065
Windows Installation and User’s Guide
IBM Tivoli Storage Manager for Enterprise Resource Planning: Data
Protection for SAP Installation and User’s Guide for DB2
SC33-6341
IBM Tivoli Storage Manager for Enterprise Resource Planning: Data
Protection for SAP Installation and User’s Guide for Oracle
SC33-6340
IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino® SC32-9056
for UNIX, Linux, and OS/400® Installation and User’s Guide
IBM Tivoli Storage Manager for Mail: Data Protection for Lotus Domino
for Windows Installation and User’s Guide
SC32-9057
IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft
Exchange Server Installation and User’s Guide
SC23-9796
Program Directory for IBM Tivoli Storage Manager for Mail (Data
Protection for Lotus Domino)
GI11-8909
Related software publications
Publication Title
Order Number
IBM TotalStorage SAN File System Administrator’s Guide and Reference
GA27–4317
IBM Tivoli SANergy Administrator’s Guide
GC26–7389
General Parallel File System: Concepts, Planning, and Installation Guide
GA76-0413
Support information
You can find support information for IBM products from a variety of sources.
Preface
vii
Getting technical training
Information about Tivoli technical training courses is available online.
Go to http://www.ibm.com/software/tivoli/education/.
Searching knowledge bases
If you have a problem with Tivoli Storage Manager, there are several knowledge
bases that you can search.
You can begin with the Tivoli Storage Manager Information Center at
http://publib.boulder.ibm.com/infocenter/tsminfo/v6. From this Web site, you
can search all Tivoli Storage Manager publications.
Searching the Internet
If you cannot find an answer to your question in the Tivoli Storage Manager
information center, search the Internet for the latest, most complete information
that might help you resolve your problem.
To search multiple Internet resources, go to the support Web site for Tivoli Storage
Manager at http://www.ibm.com/software/sysmgmt/products/support/
IBMTivoliStorageManager.html. From there, you can search a variety of resources
including:
v IBM technotes
v IBM downloads
v IBM Redbooks®
If you still cannot find the solution to the problem, you can search forums and
newsgroups on the Internet for the latest information that might help you resolve
your problem. To share your experiences and learn from others in the user
community, go to the Tivoli Storage Manager wiki at http://www.ibm.com/
developerworks/wikis/display/tivolistoragemanager/Home.
Using IBM Support Assistant
At no additional cost, you can install on any workstation the IBM Support
Assistant, a stand-alone application. You can then enhance the application by
installing product-specific plug-in modules for the IBM products that you use.
The IBM Support Assistant helps you gather support information when you need
to open a problem management record (PMR), which you can then use to track the
problem. The product-specific plug-in modules provide you with the following
resources:
v Support links
v Education links
v Ability to submit problem management reports
For more information, see the IBM Support Assistant Web site at
http://www.ibm.com/software/support/isa/.
viii
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Finding product fixes
A product fix to resolve your problem might be available from the IBM Software
Support Web site.
You can determine what fixes are available by checking the Web site:
1. Go to the IBM Software Support Web site at http://www.ibm.com/software/
tivoli/products/storage-mgr/product-links.html.
2. Click the Support Pages link for your Tivoli Storage Manager product.
3. Click Download, and then click Fixes by version.
Getting e-mail notification of product fixes
You can get notifications about fixes and other news about IBM products.
To receive weekly e-mail notifications about fixes and other news about IBM
products, follow these steps:
1. From the support page for any IBM product, click My support in the
upper-right corner of the page.
2. If you have already registered, skip to the next step. If you have not registered,
click Register in the upper-right corner of the support page to establish your
user ID and password.
3. Sign in to My support.
4. On the My support page, click Edit profiles in the left navigation pane, and
scroll to Select Mail Preferences. Select a product family and check the
appropriate boxes for the type of information you want.
5. Click Submit.
6. For e-mail notification for other products, repeat steps 4 and 5.
Contacting IBM Software Support
You can contact IBM Software Support if you have an active IBM software
maintenance contract and if you are authorized to submit problems to IBM.
Before you contact IBM Software Support, follow these steps:
1. Set up a software maintenance contract.
2. Determine the business impact of your problem.
3. Describe your problem and gather background information.
Then see “Submit the problem to IBM Software Support” on page xi for
information on contacting IBM Software Support.
Setting up a software maintenance contract
Set up a software maintenance contract. The type of contract that you need
depends on the type of product you have.
v For IBM distributed software products (including, but not limited to, Tivoli,
Lotus®, and Rational® products, as well as IBM DB2® and IBM WebSphere®
products that run on Microsoft® Windows® or UNIX® operating systems), enroll
in IBM Passport Advantage® in one of the following ways:
– Online: Go to the Passport Advantage Web page at http://www.ibm.com/
software/lotus/passportadvantage/, click How to enroll, and follow the
instructions.
– By Phone: For the phone number to call in your country, go to the IBM
Software Support Handbook Web page at http://www14.software.ibm.com/
webapp/set2/sas/f/handbook/home.html and click Contacts.
Preface
ix
v For server software products, you can purchase a software maintenance
agreement by working directly with an IBM sales representative or an IBM
Business Partner. For more information about support for server software
products, go to the IBM Technical support advantage Web page at
http://www.ibm.com/servers/.
If you are not sure what type of software maintenance contract you need, call
1-800-IBMSERV (1-800-426-7378) in the United States. For a list of telephone
numbers of people who provide support for your location, go to the Software
Support Handbook page at http://www14.software.ibm.com/webapp/set2/sas/f/
handbook/home.html.
Determine the business impact
When you report a problem to IBM, you are asked to supply a severity level.
Therefore, you need to understand and assess the business impact of the problem
you are reporting.
Severity 1
Critical business impact: You are unable to use the program,
resulting in a critical impact on operations. This condition
requires an immediate solution.
Severity 2
Significant business impact: The program is usable but is
severely limited.
Severity 3
Some business impact: The program is usable with less
significant features (not critical to operations) unavailable.
Severity 4
Minimal business impact: The problem causes little impact on
operations, or a reasonable circumvention to the problem has
been implemented.
Describe the problem and gather background information
When explaining a problem to IBM, it is helpful to be as specific as possible.
Include all relevant background information so that IBM Software Support
specialists can help you solve the problem efficiently.
To save time, know the answers to these questions:
v What software versions were you running when the problem occurred?
v Do you have logs, traces, and messages that are related to the problem
symptoms? IBM Software Support is likely to ask for this information.
v Can the problem be recreated? If so, what steps led to the failure?
v Have any changes been made to the system? For example, hardware, operating
system, networking software, and so on.
v Are you currently using a workaround for this problem? If so, be prepared to
explain it when you report the problem.
x
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Submit the problem to IBM Software Support
You can submit the problem to IBM Software Support online or by phone.
Online
Go to the IBM Software Support Web site at http://www.ibm.com/
software/support/probsub.html. Enter your information into the
appropriate problem submission tool.
By phone
For the phone number to call in your country, go to the contacts page of
the IBM Software Support Handbook at http://www14.software.ibm.com/
webapp/set2/sas/f/handbook/home.html.
If the problem that you submit is for a software defect or for missing or inaccurate
documentation, IBM Software Support creates an Authorized Program Analysis
Report (APAR). The APAR describes the problem in detail. If a workaround is
possible, IBM Software Support provides one for you to implement until the APAR
is resolved and a fix is delivered. IBM publishes resolved APARs on the Tivoli
Storage Manager product support Web site at http://www.ibm.com/software/
sysmgmt/products/support/IBMTivoliStorageManager.html, so that users who
experience the same problem can benefit from the same resolutions.
Conventions used in this publication
The typographic conventions used in Storage Agent User’s Guide.
Command to be entered on the command line:
> dsmadmc
Command to be entered on the command line of an administrative client:
query devclass
Preface
xi
xii
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
New for Tivoli Storage Manager for Storage Area Networks
Version 6.1
With Tivoli Storage Manager for Storage Area Networks Version 6.1, you can use
the file-device-sharing software IBM General Parallel File System™. You can also
continue to use either Tivoli SANergy® or IBM TotalStorage® SAN File System.
IBM General Parallel File System is the preferred option for the operating systems
on which it is supported.
© Copyright IBM Corp. 2000, 2009
xiii
xiv
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Chapter 1. Storage agent overview
Tivoli Storage Manager for Storage Area Networks allows client systems to write
data directly to, or read data directly from, storage devices attached to a SAN. This
is called LAN-free data movement.
LAN-free data movement makes LAN bandwidth available for other uses and
decreases the load on the Tivoli Storage Manager server, allowing it to support a
greater number of concurrent client connections.
The key component of Tivoli Storage Manager for Storage Area Networks is the
storage agent. You install the storage agent on a client system that shares storage
resources with the Tivoli Storage Manager server, as shown in Figure 1.
Client
Storage Agent installed
Library Control
Client Metadata
LAN
Tivoli Storage Manager Server
Client
Data
Library
Control
SAN
File Library
Tape Library
Figure 1. SAN data movement. Solid lines indicate data movement. Broken lines indicate
movement of control information and metadata.
As shown in Figure 2 on page 2, the storage agent can support several clients
while installed on only one of the clients. You can also install the storage agent on
a client system that does not share storage resources with the Tivoli Storage
Manager server, but that is connected to a client system that does share storage
resources. The LANFREECOMMMETHOD option allows a client system that
shares storage resources to communicate with the storage agent. The
LANFREECOMMMETHOD option also allows the storage agent to support several
clients while installed on only one of the clients.
© Copyright IBM Corp. 2000, 2009
1
Library Control
Client Metadata
LAN
Client
Client
Data
Tivoli Storage Manager Server
Client
Client
with
Storage Agent
Client
Data
Library
Control
SAN
File Library
Tape Library
Figure 2. SAN data movement with the LANFREECOMMMETHOD option. Solid lines indicate
data movement. Broken lines indicate movement of control information and metadata.
A Tivoli Storage Manager server, acting as a library manager, controls the storage
devices. This server can be the server working in conjunction with the storage
agent or another Tivoli Storage Manager server in the enterprise. The Tivoli
Storage Manager server keeps track of the metadata that the client has stored. The
metadata, such as policy information and file name and size, is passed over the
LAN connection between the storage agent and server.
The storage agent communicates with the server to obtain and store database
information and to coordinate device and volume access. The server and client
coordinate and transfer data access through the SAN. The client uses the storage
agent for operations where appropriate. For example, if a SAN path is defined, the
client (by means of the storage agent) transfers data on that path. If a failure occurs
on the SAN path, failover occurs and the client uses its LAN connection to the
Tivoli Storage Manager server and moves the client data over the LAN.
The storage agent can send the data directly to the server using the LAN control
paths between the storage agent and the server. An example is a LAN-free storage
pool that is updated to read-only after the client connects to the server and obtains
its initial policy information. The storage agent, instead of failing the operation,
sends the data to the server. If the storage hierarchy is configured so that the Next
storage pool destination is available, the server performs the operation.
You can also prevent data from transferring over the LAN by specifying the Tivoli
Storage Manager server parameters DATAREADPATH and DATAWRITEPATH
with the REGISTER NODE or UPDATE NODE commands for the desired node. To
review these settings, issue the following command on the server for the node:
query node node_name format=detailed
Tivoli Storage Manager supports SAN-attached device sharing in the following
environments:
2
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
v Tivoli Storage Manager native library management support consisting of an
ACSLS, SCSI, or 349X library manager and library clients or just a library
manager.
v Shared disk storage using a FILE library and the integration of IBM General
Parallel File System, Tivoli SANergy, or IBM TotalStorage SAN File System. IBM
General Parallel File System is the preferred option for operating systems on
which it is supported.
v External libraries. For a description of external libraries, see the Administrator’s
Guide.
Related concepts
“ACSLS, SCSI, and 349X tape library sharing” on page 6
When Tivoli Storage Manager servers share an ACSLS, SCSI tape, or 349X tape
library device, one server, the library manager, owns and controls the device.
“File device sharing using Tivoli SANergy” on page 9
When Tivoli Storage Manager servers share access to disk storage, the environment
contains a shared FILE device class and utilizes file-sharing software such as Tivoli
SANergy.
“External Libraries” on page 10
If Tivoli Storage Manager native library (SCSI, 3494, and ACSLS) support cannot be
used, the alternative is to configure external library support.
Scenario: LAN-free client data backup
Media to be used for client backup data resides in a storage pool that uses a device
shared on a SAN. A library manager sends the location to a storage agent. Backup
data goes directly to the device over a SAN.
A typical scenario for LAN-free data movement consists of the following steps:
1. The backup-archive client begins a backup operation. The server reports policy
information to the client, including whether a destination is LAN-free. As the
client assigns policy settings for files during backup processing, it sends the
data LAN-free when the destination for that policy is LAN-free enabled.
A storage pool is a LAN-free destination when the storage pool uses a device
shared on a SAN. That device must also have a defined path between the
device and the storage agent.
2. The storage agent receives data for those files backed up by the client and
assigned to policy settings that use a LAN-free enabled storage pool. The
storage agent sends a request for a volume mount to the library manager
server. In external libraries, the storage agent contacts the external library
manager, using the path to the executable.
3. A request is made to the storage device to mount the appropriate media.
4. The library manager notifies the storage agent of the location where the
mounted media resides. In external libraries, the storage agent is informed of
the device location by the external library manager.
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 metadata information to the Tivoli Storage Manager
server, and the server stores the information in its database.
Chapter 1. Storage agent overview
3
Scenario: Multi-session no-query restore for LAN-free path
When performing a no-query restore, the Tivoli Storage Manager server builds a
list of files to restore and sends data to the client while continuing to build the list.
This allows the restore to be restarted if interrupted.
Multiple sessions are used for the no-query restore when data for the restore
resides on devices with a LAN-free path and devices with a LAN-only path. Some
sessions restore data from the server with a LAN-only path. The other sessions use
the storage agent to restore data over the LAN-free path. This works only with
clients at Version 4.2 or above.
The number of sessions used for the restore is dependent on the value of the client
RESOURCEUTILIZATION option and the number of server volumes that contain
the client data to be restored.
The following actions outline a typical multi-session no-query restore for a
LAN-free path:
1. The client requests a file space to be restored. This request is forwarded to the
server.
2. The server determines the files to restore and the volume on which those files
reside. The server generates a list, sorted by the volume name.
3. The client is informed of the progress and the number of volumes. The client
can start more sessions to restore the information.
4. The location of the volume, and whether or not the storage agent can access the
volume, will determine how the data is handled. When the volume can be
mounted on a shared device that the storage agent can access, the data is read
from the volume by the storage agent and sent to the client. When the volume
cannot be mounted on a shared device that the storage agent can access, the
data is read from the volume by the server and sent directly to the client. The
client then begins additional sessions: some to the storage agent for the
volumes that are LAN-free enabled and some sessions to the server for those
volumes that are not LAN-free enabled.
The process repeats until all files in the list are restored.
Communications between the client, storage agent, and Tivoli Storage
Manager server
Configuration tasks link the storage agent, the client, and the Tivoli Storage
Manager server.
Figure 3 on page 5 shows how configuration connects the storage agent, client, and
the Tivoli Storage Manager server. Use this figure as a reference point while
installing software on client systems and while defining the storage agent and
configuring devices on the server.
4
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Tivoli Storage Manager Client Workstation
Client - DATAOWNER
dsm.sys file
servername server_c
enablelanfree yes
lanfreecommmethod tcpip
lanfreetcpserveraddress test.example.com
lanfreetcpport 1500
commmethod TCPip
tcpserveraddress server_c.example.com
Storage Agent - STORAGNT
dsmsta.opt file
servername tsmsrver
devconfig devconfig.out
commmethod tcpip
tcpport 1500
devconfig.out file
set staname storagnt
set stapassword xxxxxxx
set stahladdress agent.example.com
define server tsmsrver serverpassword=xxxxxxxx
hladdress=tsmsrver.example.com
lladdress=1502
Tivoli Storage Manager Server - TSMSRVER
define server storagnt serverpassword=fun4me
hladdress=agent.example.com
lladdress=1500
register node dataowner bak2work
domain=sandomain
Figure 3. Connections between the client, storage agent, and server. The passwords are
shown as xxxxxxx because they are encrypted in the file.
Chapter 2. Planning for storage agent installation and
configuration
Planning the system configuration provides a smooth transition through system
setup and into production.
As part of your planning, you need to identify the following:
v Which environment to implement.
v Devices to be used for LAN-free data movement.
v The clients that will use LAN-free data movement.
v The server that will manage particular clients’ data.
© Copyright IBM Corp. 2000, 2009
5
v The library used for the LAN-free enabled device. If the library is a Tivoli
Storage Manager shared library, you must identify the Tivoli Storage Manager
server that is the library manager. If the library is an externally managed library
using Sun StorageTek ACSLS, you must identify the control point.
Supported operating systems
Tivoli Storage Manager for Storage Area Networks is supported on AIX®, HP-UX,
Linux®, Sun Solaris, and Microsoft Windows. The storage agent can also work in
conjunction with a Tivoli Storage Manager server on z/OS®.
The storage agents on the designated operating systems can work in conjunction
with a Tivoli Storage Manager server on any of the same platforms. If you are
using the storage agent with a Tivoli Storage Manager server on z/OS, you must
install and configure another server on another operating system (AIX, HP-UX,
Linux, Solaris, or Windows) to function as the library manager. Alternatively, you
can implement library support through an external library manager, for example,
IBM Integrated Removable Media Manager. For details about using the storage
agent with z/OS, see the Administrator’s Guide and the Administrator’s Reference.
When using a shared ACSLS library, the library manager must be a Tivoli Storage
Manager server on AIX, HP-UX, Linux, Solaris, or Windows.
Storage devices and the configuration of your environment
The type of storage device you use for LAN-free data storage determines how to
configure your environment.
ACSLS, SCSI, and 349X tape library sharing
When Tivoli Storage Manager servers share an ACSLS, SCSI tape, or 349X tape
library device, one server, the library manager, owns and controls the device.
The library manager operations include checking volumes into and out of the
library, labeling volumes, mounting and dismounting volumes, auditing volumes,
and tracking an inventory of library contents. The storage agents, along with other
Tivoli Storage Manager servers that share this library are library clients. As a library
client, the storage agent stores data and requests drives, tapes, and volumes.
When the Tivoli Storage Manager server (data manager server) is also the library
manager for the devices where data is stored by the storage agent, then the storage
agent communicates requests to this Tivoli Storage Manager server. When the
Tivoli Storage Manager server (data manager server) is another library client, then
the storage agent communicates requests for itself or the metadata server directly
to the library manager. The library manager operations include checking volumes
into and out of the library, labeling volumes, mounting and dismounting volumes,
auditing volumes, and tracking an inventory of library contents.
When using a shared ACSLS library, the library manager must be a Tivoli Storage
Manager server on AIX, HP-UX, Linux, Solaris, or Windows.
A library client requests shared library resources, such as drives or media, from the
library manager, but uses the resources independently. The library manager
coordinates the access to these resources. Data moves over the SAN between the
storage device and either the library manager or the library client. Either the
6
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
library manager or any library client can manage the LAN-free movement of client
data as long as the client system includes a storage agent.
In this library-sharing environment, the most important relationship is the one
between the server and the storage agent. The server, working in conjunction with
the storage agent, manages the storage hierarchy. The server could be a library
client or library manager. It is responsible for:
v Migrations
v Expiration of files based on policy information
v Reclamation of free space on volumes and consolidation of the volumes
v Disaster recovery
The storage agent contributes information to the storage hierarchy through various
operations, but this role is independent of the library sharing role.
The library manager and library client configurations are represented in Figure 4
and Figure 5 on page 8.
Tivoli Storage Manager
Clients with Storage Agents
Tivoli Storage Manager
Server Library Manager
LAN
Tivoli Storage Manager
Server Library Client
SAN
Tape Library
Figure 4. Library manager and client LAN-free configuration
Tips:
v An environment can have a library manager without a library client.
v In an environment where ACSLS library support is required, the library client
can reside on a Tivoli Storage Manager server on AIX, HP-UX, Linux, Solaris,
Chapter 2. Planning for storage agent installation and configuration
7
Windows, or z/OS. The library manager must reside on a Tivoli Storage
Manager server on AIX, HP-UX, Linux, Solaris, or Windows.
The following configurations are shown in Figure 4 on page 7:
v A Tivoli Storage Manager server library manager manages a client’s data, which
is stored in a tape library.
v A Tivoli Storage Manager server library client manages a client’s data, which is
stored in a tape library.
Client Metadata
LAN
Client
Storage Agent
installed
Library Manager
Server
(Library Client)
Library Control
LAN
Client
Data
Data Manager Server
z/OS
Library
Control
SAN
ESCON/FICON
Shared Tape Library
(IBM 3494 or
Storage Tek Tape Library)
Figure 5. Library manager and client LAN-free configuration on z/OS
The following requirements apply to the library manager server:
v If your environment consists of native ACSLS support with a Sun StorageTek
tape library, the library manager server can be a Tivoli Storage Manager server
residing on an AIX, Solaris, or Windows operating system.
v If your environment consists of an IBM 3494 tape library, the library manager
server can be a Tivoli Storage Manager server residing on an AIX, HP-UX,
Linux, Solaris, or Windows operating system.
v Both environments can support the storage agent (library client) on an AIX,
HP-UX, Linux, Solaris, or Windows operating system.
Remember: When using a server running on a z/OS system with shared library
support and a 3494 automated tape library, you must configure a Tivoli Storage
Manager server on AIX, Linux, HP-UX, Solaris, or Windows as a library manager
to control storage agent mount requests. When using a Sun StorageTek library
controlled by Sun StorageTek LibraryStation software, you must configure an AIX,
Solaris, or Windows server as a library manager with ACSLS support to control
storage agent mount requests.
8
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
File device sharing using Tivoli SANergy
When Tivoli Storage Manager servers share access to disk storage, the environment
contains a shared FILE device class and utilizes file-sharing software such as Tivoli
SANergy.
Remember: SANergy is just one option for file-sharing software. IBM General
Parallel File System is the preferred option for the operating systems on which it is
supported. IBM TotalStorage SAN File System is another option.
SANergy provides a file-sharing accelerator. Because you are using a FILE library,
you must determine the location in which to install the Tivoli SANergy client and
the Tivoli SANergy Metadata Controller (MDC). On UNIX systems, Common
Internet File System (CIFS) or a Network File Share (NFS) are required software.
Restriction: The Tivoli SANergy license (included with the storage agent media) is
provided with Tivoli Storage Manager only for supporting LAN-free backup to
disk.
Figure 6 shows the possible Tivoli SANergy configurations. (For additional
information about configuring SANergy, refer to the SANergy publications.)
1
Tivoli Storage Manager
client with storage agent
Another node
LAN
2
Tivoli Storage Manager
server
SAN
FILE library
Figure 6. Tivoli SANergy configurations
One possible configuration is to install the Tivoli SANergy client on the Tivoli
Storage Manager client system (1) and to install the Tivoli SANergy MDC on the
Tivoli Storage Manager server (2). Configurations can also consist of multiple
platforms. For example, an environment can consist of a SANergy MDC working
with Windows and AIX clients.
Chapter 2. Planning for storage agent installation and configuration
9
External Libraries
If Tivoli Storage Manager native library (SCSI, 3494, and ACSLS) support cannot be
used, the alternative is to configure external library support.
A typical external library configuration includes an external library manager such
as the IBM Removable Media Manager (IRMM).
The Sun StorageTek Automated Cartridge System Library Software (ACSLS) Server
or the LibraryStation on z/OS manages the physical aspects of tape cartridge
storage and retrieval. (See Figure 7 on page 11.) The external library manager
communicates with the ACSLS Server or the LibraryStation on z/OS to access tape
cartridges in an automated Sun StorageTek library. The storage agent is installed
on a system containing the external library manager and a Tivoli Storage Manager
backup-archive client or a Tivoli Storage Manager data protection application
client. This configuration provides access to SAN-attached storage devices using
LAN-free data movement. The continued connection to the LAN provides a
metadata (control information) path. If the storage agent is not available, the SAN
provides a failover path for data backup and recovery.
10
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
LibraryStation
on
z/OS
LAN
or
Data Owner
ACSLS
Server
Tivoli Storage
Manager
Client
Tivoli Storage
Manager
Server
Storage
Agent
Library Client
Library
Manager
Changer
Control
3270
LAN-free
Data
Movement
Changer
Control
SAN
Changer
Control
1 2 3 4
TCP/IP Communication
Fibre Channel
3270 Communications-Library Control Commands
Tape Drives
1
2
3
4
Storage Tek Tape Library
Figure 7. ACSLS library environment
For detailed information about ACSLS, refer to the appropriate Sun StorageTek
documentation. For detailed information about an external library manager, such
as IRMM, refer to the product’s documentation.
If you currently have data associated with the Tivoli Storage Manager ACSLS
library type and want to take advantage of LAN-free, you need to consider
coexistence and migration issues.
If you stored data using external library support for ACSLS library access and plan
to migrate to a native Tivoli Storage Manager library sharing environment, see the
Administrator’s Guide.
Related concepts
Appendix B, “ACSLS legacy data migration and coexistence,” on page 53
If ACSLS shared-library support is not possible in your configuration, data
migration is required.
Chapter 2. Planning for storage agent installation and configuration
11
System requirements
Tivoli Storage Manager for Storage Area Networks requires specific levels of
hardware and software.
TCP/IP
TCP/IP is required for communication among the Tivoli Storage Manager server,
the client, and the storage agent.
The Tivoli Storage Manager storage agent can use TCP/IP Version 6 (IPv6) as its
communications protocol. IPv6 is interoperable with TCP/IP Version 4. You can
specify either IPv4 or both IPv4 and IPv6 as the value of the COMMMETHOD
option before starting the server, the backup-archive client, or the storage agent.
The same port numbers are used by the server, the backup-archive client, and
storage agent for both IPv4 and IPv6.
The server and storage agent use COMMMETHOD V6TCPIP to specify support for
both IPv4 and IPv6 simultaneously, depending on the protocols configured on the
system on which the server or storage agent are running. As in prior releases,
COMMMETHOD TCPIP specifies that only IPv4 is used. When configuring the
storage agent using the DSMSTA SETSTORAGESERVER command, use addresses
that correspond to the communications method used by the backup-archive client.
The backup-archive client supports either IPv4 (COMMMETHOD TCPIP) or IPv6
(COMMMETHOD V6TCPIP), but not both at the same time. Other client
components (CAD, Web Client ) use COMMMETHOD V6TCPIP to support both
IPv4 and IPv6 simultaneously.
IPv6 address formats are acceptable for all functions that support IPv6. However, if
you use IPv6 addresses for the Shared Memory Protocol function, which does not
support IPv6, communications will fail. Continue to use IPv4 for Shared Memory
Protocol.
Server licensing and compatibility
You must have an AIX, HP-UX, Linux, Sun Solaris, Windows, or z/OS Tivoli
Storage Manager server that has a license for LAN-free operations.
To ensure compatibility between the storage agent and the server, check the Web
site for Tivoli Storage Manager storage agent and server compatibility at
http://www.ibm.com/support/docview.wss?uid=swg21302789.
To download the latest interim fix, see the IBM Tivoli Storage Manager product
support Web site at http://www.ibm.com/software/sysmgmt/products/support/
IBMTivoliStorageManager.html.
Clients and API
To perform LAN-free data movement, you must install a Tivoli Storage Manager
backup-archive client or a Tivoli Storage Manager Date Protection application
client on client systems.
v For information about LAN-free requirements for data-protection clients, see the
Tivoli Storage Manager data-protection documentation.
v For information about supported versions of the backup-archive client and client
API, check the Web site at http://www.ibm.com/support/
12
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
entdocview.wss?rs=663&context=SSGSG7&q=5.1+os
%2F390+supported+windows+clients+and+tsm&uid=swg21053218.
v You can download the latest software levels from the Tivoli Storage Manager
product support Web site at http://www.ibm.com/software/sysmgmt/
products/support/IBMTivoliStorageManager.html. The client API is packaged
with the backup-archive client.
File sharing software
If you are sharing disk storage, IBM General Parallel File System, Tivoli SANergy,
or IBM TotalStorage SAN File System must be installed. Tivoli SANergy is
included with the storage-agent media.
Use of the Tivoli SANergy components included with the Tivoli Storage Manager
for Storage Area Networks product is limited to use to enable LAN-free backup
and restore to disk in conjunction with your licensed use of the Tivoli Storage
Manager for Storage Area Networks product.
If you are sharing only tape devices, file-sharing software is not required.
Encryption support
Encryption provides security and protects sensitive data on tape media. With Tivoli
Storage Manager for Storage Area Networks, you can use IBM and HP LTO-4, 3592
generation 2, 3592 generation 3, and client-side encryption:
v When LTO-4 encryption is enabled, Tivoli Storage Manager manages data
encryption and decryption according to specifications set when defining the LTO
device class. To enable drive encryption with IBM LTO-4, you must have the
IBM RMSS Ultrium device driver installed. IBM LTO-4 SCSI drives do not
support encryption.
v Tivoli Storage Manager for Storage Area Networks supports client-side
encryption and the Tivoli Storage Manager automatically-generated password.
Concurrent access to volumes in storage pools associated with
the FILE device type
Concurrent access improves restore performance by allowing two or more client
sessions, two or more storage agents, or a combination of client sessions and
storage agents to access the same volume at the same time. Multiple client sessions
and storage agents can read a FILE volume concurrently. In addition, one client
session or storage agent can write to the volume while it is being read. To take
advantage of concurrent access, both the storage-agent and the Tivoli Storage
Manager server must be at version 5.5.0 or later.
Obtaining system configuration information for clients and servers
To be more efficient, obtain client- and server-system information before installing
and configuring the storage agent.
Chapter 2. Planning for storage agent installation and configuration
13
Client-system and server-system configuration work sheets
Work sheets help organize the information that you need to configure the storage
agent for LAN-free data movement.
Client-system information
Client-system information includes information about storage agents, client
communication protocols and ports, and devices.
Storage agent properties
Type of
information
Description
Storage agent
name
The name for the storage agent (for example,
storagnt)
Storage agent
password
The password for the storage agent (for
example, fun4me)
TCP/IP address
The TCP/IP address of the storage agent (for
example, agent.example.com)
TCP/IP port
The TCP/IP port of the client system
Use this column to
record the values for
your environment
Client properties
Type of
information
LAN-free
communications
protocol
Description
Use this column to
record the values for
your environment...
The communications protocol between the
client and the storage agent. The following
protocols are available. Use the value in
parentheses as the value of the client
LANFREECOMMMETHOD option.
v TCP/IP Version 4 (TCPIP)
v TCP/IP Version 4 or Version 6 (V6TCPIP)
v Shared Memory (SHAREDMEM))
LAN-free port
The TCP/IP port that is used for LAN-free data
movement. Use this value as the value of the
client LANFREETCPPORT option.
Tip: For details about the LANFREECOMMMETHOD option, see the Backup-Archive
Clients Installation and User’s Guide.
Device information
Table 5. External library environment
Type of
information
14
Description
Executable file
location
The fully qualified path to the
external-library-manager executable file for
each storage agent to which Tivoli Storage
Manager sends media-access requests.
Library name
A 1- through 32-character name of your
choosing.
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Use this column to
record the values for
your environment...
Table 6. ACSLS, 3494, or SCSI tape-library sharing environment
Type of
information
Device name
Description
Use this column to
record the value or
values for your
environment...
The name of each tape drive for which you
will define a path
Table 7. Shared disk environment
Type of
information
Local path name
Description
Use this column to
record the value for
your environment...
The name of the local path to the
network-mounted file system (for example,
/shareddisk)
Related tasks
“Obtaining device information” on page 17
You use the device information when defining paths for the server that functions
as the library manager. Device information is obtained from the system on which
the storage agent is installed. If you are configuring a FILE Library, you do not
need device information.
Server-system information
Server-system information includes information that the storage agent needs to
communicate with the Tivoli Storage Manager server. You also need information
about devices and client nodes.
To verify server information, use the QUERY STATUS command. You can issue the
command from a Tivoli Storage Manager administrative command-line client.
Server properties
Type of
information
Description
Name
The name of the server (for example, tsmsrver)
Password
The password for the server (for example, not4u)
TCP/IP
address
The TCP/IP address for the server. (for example,
tsmsrver.example.com)
TCP/IP port
The TCP/IP port for the server (for example,
1502)
Use this column to
record the values for
your environment
Chapter 2. Planning for storage agent installation and configuration
15
Device information
Table 8. External library environment
Type of
information
Description
Use this column to
record the values for
your environment...
Executable file The fully qualified path to the
location
external-library-manager executable file for each
storage agent to which Tivoli Storage Manager
can send media access requests
Library name
A 1- through 32-character name of your choosing
Table 9. ACSLS, 3494, or SCSI library environment
Type of
information
Description
Library name
The name of an ACSLS, 3494, or SCSI library
Library device
name
The device name for an ACSLS, 3494, or SCSI
library, which you use when you define the path
Device name
The name of each tape drive for which you will
define a path
Use this column to
record the values for
your environment...
Table 10. Shared disk environment
Type of
information
Description
Use this column to
record the value for
your environment...
Local path name The name of the local path to the
network-mounted file system (for example,
/shareddisk)
Client node information
Type of
information
Client node
names
Description
Use this column to
record the values for
your environment...
The names of the client nodes on which you
will install and configure the storage agent. You
need this information when you register the
nodes, set the policy for them, and place any
needed restrictions on them.
Related tasks
“Obtaining device information” on page 17
You use the device information when defining paths for the server that functions
as the library manager. Device information is obtained from the system on which
the storage agent is installed. If you are configuring a FILE Library, you do not
need device information.
“Verifying and updating client node information” on page 18
Configuring LAN-free data movement requires registration and policy information
about client nodes. You can also restrict when a client node uses a LAN-free path.
16
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Obtaining device information
You use the device information when defining paths for the server that functions
as the library manager. Device information is obtained from the system on which
the storage agent is installed. If you are configuring a FILE Library, you do not
need device information.
In the z/OS environment, use the information for a Sun Solaris server because the
z/OS servers cannot function as library managers.
Obtaining tape device information in a Sun Solaris environment is different
depending on whether your environment supports IBM devices or non-IBM
devices.
Obtaining special file names of IBM tape devices
After installing device drivers for your IBM tape drives, a set of special file names
is available for each device.
To obtain special file names, enter the following command:
ls /dev/rmt/*st
A name typically has the form /dev/rmt/xst, where x is a number.
Obtaining special file names of non-IBM tape devices
Special file names are available for non-IBM devices.
To determine the special file names:
1. Verify that the device is connected to your system and active.
2. Ensure the Tivoli Storage Manager device driver package (TIVsmSdev) is
installed.
3. Edit the /usr/kernel/drv/mt.conf file. Add one stanza (as shown in the
example at the top of the file) for each SCSI target ID and LUN combination
that you want the device driver to probe for supported tape drives.
4. To configure the drives, enter the following command:
/usr/sbin/add_drv -m '* 0666 bin bin' /usr/kernel/drv/mt
5. Determine the special file names for the tape drives. The device special files for
the tape drives display in the /dev/rmt directory. Their names have the form
/dev/rmt/xmt, where x is a number.
6. Optional: To determine the relationship between a physical device and the
special file that was created for it, enter the following command: .
ls
/dev/rmt/*mt
The special file name typically has the form /dev/rmt/xmt, where x is a
number.
Chapter 2. Planning for storage agent installation and configuration
17
Verifying and updating client node information
Configuring LAN-free data movement requires registration and policy information
about client nodes. You can also restrict when a client node uses a LAN-free path.
To verify client node information:
1. Identify the client node or nodes that will use the storage agent. In a typical
environment, a storage agent is used only by the client node residing on the
same system as the storage agent. However, you can configure two or more
client nodes to use the same storage agent.
2. Verify that the nodes are registered. If they are not, you need to register them.
For details, see the Administrator’s Guide.
3. Verify the policy information for the nodes. The copy group for backup and
archive must point to a storage pool that has a LAN-free path for a particular
storage agent. You define drive LAN-free paths and make them available for
the storage pool. To view the destinations that are capable of LAN-free data
movement, you can issue the VALIDATE LANFREE command on the server.
For details about this command, see the Administrator’s Reference.
4. After you verify the registration and policy information for the nodes, you can
place restrictions on when a node can use the LAN-free path. The node
attributes DATAWRITEPATH and DATAREADPATH determine the restriction
placed on the node:
v To use only the LAN-free path on backup and archive operations, specify
DATAWRITEPATH .
Important: Backup and archive operations can fail if the LAN-free path is
unavailable.
v To use the LAN path on restore and retrieve operations, specify
DATAREADPATH .
For more information about commands and their attributes, see the
Administrator’s Reference.
Related tasks
“Configuring multiple clients to use the same storage agent” on page 44
You can configure two or more clients to use the same storage agent.
18
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Chapter 3. Installing and configuring tape-library and
file-device-sharing environments
The destination for LAN-free data can be tape media or sequential-access disk
media. Configuration requirements vary depending upon the type of environment.
Before beginning this procedure:
v Make sure that you understand the overall installation and configuration
process, which takes place on different systems at different times.
v Be sure that you have the information recorded in the configuration-information
work sheets.
The major installation and configuration steps are:
1. “Establishing network connections”
2. Installing software on client systems:
“Installing software on Sun Solaris client systems” on page 20
3. “Defining the storage agent and configuring devices on the server” on page 24
4. “Defining paths from the storage agent to drives” on page 27
5. “(z/OS data-manager server) Formatting volumes for LAN-free data
movement” on page 29
6. “Verifying the LAN-free configuration” on page 29
7. “Determining whether the data movement was LAN-free” on page 30
Related tasks
“Setting up LAN-free data movement using the Administration Center wizard” on
page 44
To set up LAN-free data movement on the server in tape-library and
file-device-sharing environments, you can use the Enable LAN-free Data
Movement wizard in the Administration Center.
Related reference
“Obtaining system configuration information for clients and servers” on page 13
To be more efficient, obtain client- and server-system information before installing
and configuring the storage agent.
Establishing network connections
Tivoli Storage Manager for Storage Area Networks requires specific levels and
models of hardware and software. You must ensure that your system meets these
requirements.
To establish network connections:
1. Attach the server system and the client systems to the LAN and to the SAN
along with appropriate storage devices.
2. Optional: If you are planning to use a storage agent with disk media, install
IBM General Parallel File System, Tivoli SANergy, or IBM TotalStorage SAN
File System on the applicable systems. Tivoli SANergy is included with the
storage agent media.
© Copyright IBM Corp. 2000, 2009
19
Restriction: Use of the Tivoli SANergy components that are included with the
IBM Tivoli Storage Manager the storage agent media is limited. You can use
Tivoli SANergy components only for LAN-free backup and restore-to-disk
operations in conjunction with your licensed use of the IBM Tivoli Storage
Manager for Storage Area Networks product.
For details about TivoliSANergy, see the IBM Tivoli SANergy Administrator’s
Guide. For details levels and models of hardware and software, see
http://www.ibm.com/software/sysmgmt/products/support/
IBMTivoliStorageManager.html.
Related concepts
“File device sharing using Tivoli SANergy” on page 9
When Tivoli Storage Manager servers share access to disk storage, the environment
contains a shared FILE device class and utilizes file-sharing software such as Tivoli
SANergy.
Installing software on Sun Solaris client systems
The backup-archive client or the Tivoli Data Protection client software, the Tivoli
Storage Manager API, and the storage agent are installed on client systems.
Perform the following tasks to install the software:
1. “Installing or upgrading the client and API”
2. “Installing and configuring the storage agent” on page 22
Related concepts
“Communications between the client, storage agent, and Tivoli Storage Manager
server” on page 4
Configuration tasks link the storage agent, the client, and the Tivoli Storage
Manager server.
Installing or upgrading the client and API
The client and API software must be at the appropriate level. Software
configuration is required to enable communications.
Before beginning this procedure:
v Verify that the client system meets the prerequisites for client software.
v Be sure you have the information recorded in the configuration-information
work sheets.
Additional information is available from the following sources:
v For details about the client-system prerequisites and about the files and file
options described in this procedure, see the Backup-Archive Clients Installation and
User’s Guide.
v For details about client software and the API, see the Web site at
http://www.ibm.com/software/sysmgmt/products/support/
IBMTivoliStorageManager.html.
v For details about storage agent and backup-archive client compatibility, see the
Web site at http://www.ibm.com/support/entdocview.wss?rs=663
&context=SSGSG7&q=5.1+os%2F390+supported+windows+clients+and+tsm
&uid=swg21053218.
To install or upgrade the client and API software:
20
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
1. If the client software and the API are not already installed, install them now. To
ensure software compatibility, check the Web site for Tivoli Storage Manager
storage agent and backup-archive client compatibility. You can download the
latest software levels from the Tivoli Storage Manager product support Web
site.
Remember: If you are using the storage agent to support multiple clients,
install or upgrade the client and API software on each supported client.
2. Using the information that you collected in the configuration-information work
sheets, modify the dsm.sys client options file:
a. Locate the options file and open it. The file can be located in one of several
places, such as the installation directory, or in a location pointed to by an
environment variable.
b. Specify a value for the SERVERNAME option to identify the stanza. For
example: servername server_c.
c. Specify the communications method to be used between the client and
server.
Table 11. Communications methods
To use this communication
method...
Install this software...
To connect to these Tivoli
Storage Manager servers...
TCP/IP
TCP/IP (Standard with
Solaris)
AIX, HP-UX, Linux, Solaris,
Windows, z/OS
Shared memory
TCP/IP (Standard with
Solaris)
Solaris
For example:
commmethod tcpip
tcpserveraddress server_c.example.com
tcpport 1502
The example uses a TCPPORT of 1502. However, the default TCPPORT is
1500.
Keep the file open for the next step.
3. Add the following options to the same dsm.sys stanza edited in step 2c. These
options specify that the client will use SAN-attached devices, when the path is
available, during backup, restore, archive, and retrieve processing.
enablelanfree yes
lanfreecommmethod tcpip
lanfreetcpserveraddress test.example.com
lanfreetcpport 1500
or
enablelanfree yes
lanfreecommmethod sharedmem
lanfreeshmport 1510
4. Edit the dsm.opt file to specify the SERVERNAME option that identifies the
stanza that you edited in step 2b.
servername server_c
Remember: The SERVERNAME option in dsm.sys must match the
SERVERNAME option in dsm.opt. However, it is unrelated to and does not
need to match the SERVERNAME option that is defined for the storage agent
in dsmsta.opt. For a description of the SERVERNAME option in dsm.sys and
dsm.opt, see the Backup-Archive Clients Installation and User’s Guide.
Chapter 3. Installing and configuring tape-library and file-device-sharing environments
21
Related reference
“Client-system and server-system configuration work sheets” on page 14
Work sheets help organize the information that you need to configure the storage
agent for LAN-free data movement.
Installing and configuring the storage agent
The storage agent must be installed on a client system that has connections to
storage resources on the SAN.
Before beginning this procedure:
v Verify that your system meets the system requirements.
v Be sure that you have the information recorded in the configuration-information
work sheets.
v Make sure to stop all existing Tivoli Storage Manager products prior to installing
the storage agent. Installation will stop when an active Tivoli Storage Manager
process is detected. If this occurs, close all active Tivoli Storage Manager
products and retry installing the storage agent.
The storage agent honors the Tivoli Storage Manager server environment variables
DSMSERV_CONFIG.
To reduce workload and processing time and to optimize LAN-free performance,
do not install the storage agent and the Tivoli Storage Manager server on the same
system.
1. Log in as the root user.
2. Load the storage agent CD into the selected drive.
3. For a list of packages that you can install, enter the following command:
/usr/sbin/pkgadd -d /cdrom/cdrom0
In this example the CD-ROM name is /cdrom/cdrom0; the name of your
CD-ROM may be different.
Select the appropriate package:
TIVsmSsta
The storage agent application
TIVsmSdev
The device driver package for non-IBM devices
To load the selected package, use the PKGADD command. The installation
program automatically installs the storage agent based on the level of Sun
Solaris on the installation system.
Loading the storage agent files can take several minutes. It can also take a few
minutes for the installation to begin after the server package has been selected.
4. Enter y when the system issues the following message: This package contains
scripts which will be executed with super-user (root) permission during
the process of installing the package. Do you want to continue with the
installation of this package?
5. To eject the CD after the installation is complete, enter the following commands
from a root user command prompt:
cd /
eject cdrom
22
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
6. Ensure that the DEVCONFIG option is specified in the dsmsta.opt file. For
example, for a device configuration file named devconfig.out located in
/opt/tivoli/tsm/StorageAgent/bin, edit the dsmsta.opt file and enter the
following line:
devconfig devconfig.out
7. Use the information that you collected in the configuration-information work
sheets to issue the DSMSTA SETSTORAGESERVER command. For example:
dsmsta setstorageserver myname=storagnt mypassword=fun4me
myhladdress=agent.example.com
servername=tsmsrver serverpassword=not4u
hladdress=tsmsrver.example.com lladdress=1502
The hladdress must match the TCPServeraddress located in the dsm.sys file on
the Tivoli Storage Manager client. When configuring the storage agent using
the DSMSTA SETSTORAGESERVER command, use addresses that correspond
to the communications method used by the backup-archive client. The
backup-archive client supports either IPv4 (COMMMETHOD TCPIP) or IPv6
(COMMMETHOD V6TCPIP), but not both at the same time.
The command generates the following lines in the device configuration file for
the storage agent:
set staname storagnt
set stapassword xxxxxxx
set stahladdress agent.example.com
define server tsmsrver serverpassword=xxxxxxxxxxx
hladdress=tsmsrver.example.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
The default installation directory is /opt/tivoli/tsm/StorageAgent/bin.
Related reference
“System requirements” on page 12
Tivoli Storage Manager for Storage Area Networks requires specific levels of
hardware and software.
“Client-system and server-system configuration work sheets” on page 14
Work sheets help organize the information that you need to configure the storage
agent for LAN-free data movement.
“The storage agent options file” on page 47
The storage agent options file contains the name of the server with which the
storage agent communicates, along with other options. Normally, you do not need
to make any changes to the options file unless your Tivoli Storage Manager server
changes.
“The device configuration file for the storage agent” on page 50
The device configuration file for the storage agent includes information about the
storage agent and about the Tivoli Storage Manager server with which the storage
agent communicates and that is managing the SAN-attached libraries and drives
that the storage agent uses.
“DSMSTA SETSTORAGESERVER” on page 45
Use the DSMSTA SETSTORAGESERVER command to initialize the storage agent
and add communication information to the device configuration file and the
storage agent options file dsmsta.opt.
Chapter 3. Installing and configuring tape-library and file-device-sharing environments
23
Defining the storage agent and configuring devices on the server
To set up LAN-free communications on the Tivoli Storage Manager server, you
must set up server-to-server communication, define storage agents to the server,
configure SAN drives, set the LAN-free destination storage pool, and confirm node
registration and configuration.
Before beginning this procedure, be sure that you have the information recorded in
the configuration-information work sheets.
Perform these tasks to define the storage agent and configure devices on the
server:
1. “Setting up server-to-server communication”
2. “Defining storage agents to the Tivoli Storage Manager server” on page 25
3. “Configuring SAN drives” on page 25
4. “Setting the LAN-free destination” on page 26
5. “Confirming client node registration and configuration” on page 26
Related concepts
“Communications between the client, storage agent, and Tivoli Storage Manager
server” on page 4
Configuration tasks link the storage agent, the client, and the Tivoli Storage
Manager server.
Related reference
“Obtaining system configuration information for clients and servers” on page 13
To be more efficient, obtain client- and server-system information before installing
and configuring the storage agent.
Setting up server-to-server communication
Server-to-server communication is required for Tivoli Storage Manager servers and
storage agents to share library devices on a SAN.
To set up server-to-server communication, issue the following commands on the
Tivoli Storage Manager server. Replace the example values with values from the
configuration-information work sheet.
set
set
set
set
servername tsmsrver
serverpassword not4u
serverhladdress tsmsrver.example.com
serverlladdress 1502
These commands establish the server’s name, password, TCP/IP address, and port.
Verify that the password has been set for the server by issuing the QUERY STATUS
command from a Tivoli Storage Manager administrative command line. The value
of the Server Password Set field in the command output must equal YES.
24
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Defining storage agents to the Tivoli Storage Manager server
For each client the will use LAN-free data transfer, you must define the client’s
storage agent to the server as if the storage agent is another server.
To define the storage agent, issue the DEFINE SERVER command from the Tivoli
Storage Manager server (library manager or library client) that will manage the
client’s data. Use the same name and password that you specified for the storage
agent when you installed it on the client system.
define server storagnt serverpassword=fun4me
hladdress=agent.tucson.ibm.com lladdress=1500
If the library to be used for LAN-free data movement is a Tivoli Storage Manager
shared library and the data manager server is a library client, then you must
define the storage agent to the library manager as well as the library client. The
storage agent needs to be able to contact the library manager directly when
making mount requests. If the storage agent is only defined to the library client, it
will attempt to use information from the library client to define itself to the library
manager. If the storage agent is unable to define itself to the library manager, then
you must define the storage agent manually using the DEFINE SERVER command
issued from the library manager.
To verify that the storage agent is defined to the library manager, issue the
following command from the library manager server:
query server server_name format=detailed
Important: If the library manager server is different than the library client server
that hosts the storage agent, define the storage agent as a server on both the
library manager server and the library client server.
Configuring SAN drives
Drive-configuration requirements vary depending on whether you are using tape
devices or disk devices.
Configuring tape drives
Configuration requirements vary depending on whether you are connecting the
storage agent to a library manager or to a library client.
v To connect the storage agent to a library manager:
1. Define a shared ACSLS, SCSI, or 3494 library using the SHARED=YES
option.
2. Define paths to the library using the DEFINE PATH command on the server.
3. Define drives that are associated with the library.
4. Define paths to the drives using the DEFINE PATH command on the server.
5. Define the device class.
6. Define the storage pool.
When using a shared ACSLS library, the library manager must be a Tivoli
Storage Manager server on AIX, HP-UX, Linux, Solaris, or Windows.
v To connect the storage agent to a library client:
1. On the library manager, complete step 1 through step 5.
2. On the library client:
a. Define a shared ACSLS, SCSI, or 3494 library using a library type of
shared (LIBTYPE=SHARED).
b. Define the device class.
Chapter 3. Installing and configuring tape-library and file-device-sharing environments
25
c. Define the storage pool.
Configuring disk drives
A FILE (sequential-access disk) device class is required for disk drives.
To configure disk drives:
1. Configure server-to-server communication.
2. Define a device class of DEVTYPE=FILE and SHARED=YES. Tivoli Storage
Manager automatically defines a new FILE library and also defines drives
corresponding to the mount limit for the FILE device class. The FILE library
name is the same as the device class name. Each drive uses the library name
with a numeric suffix. If the mount limit is changed, the number of drives also
changes.
Each session gets exclusive access to a file volume. To optimize performance,
match the mount limit to the number of volumes.
Setting the LAN-free destination
The destination for data must be a LAN-free capable storage pool
To set a LAN-free destination:
1. Define a copy group with its destination being the LAN-free capable storage
pool that you created when you configured the SAN drives. For example:
define copygroup sandirect sandirectpolicy sandirectdefmft
type=backup destination=storage_pool_name
Note: If you are using a hierarchical storage management (HSM) client
configured for LAN-free data movement, set the management class (not the
copy group) to a LAN-free capable storage pool.
2. Activate the policy set. For example:
activate policyset sandirect sandirectpolicy
For details about changing policy for clients that can use SAN drives, see the
Administrator’s Guide. For details about commands, see the Administrator’s Reference.
Remember: If you decide not to use the default management class for the SAN
drives, you need to create a new management class. Clients that use SAN drives
need an include statement to bind their files to the new management class. For
details about the include-exclude list, see the Backup-Archive Clients Installation and
User’s Guide.
Confirming client node registration and configuration
Client nodes must be registered and configured for LAN-free backups.
To verify that node settings are correct, issue the following command:
query node node_name format=detailed
If node settings are not correct, issue the UPDATE NODE command to adjust the
settings. If the node was not registered and configured for LAN-free backups,
register the node with the REGISTER NODE command.
To improve performance of your LAN and SAN resources for LAN-free data
movement, you can control the path that data transfers take for each LAN-free
26
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
capable client. Use the REGISTER NODE and UPDATE NODE commands to
specify whether data read/write operations use the LAN path only, the LAN-free
path only, or either path.
If the node belongs to a multi-threaded client and there are drives available, the
MAXNUMMP parameter might restrict the number of drives that are available for
the storage agent to use on behalf of the client. Specify the MAXNUMMP
parameter on the REGISTER NODE or UPDATE NODE command.
For more information about commands, see the Administrator’s Reference.
Defining paths from the storage agent to drives
Paths allow a client, by means of a storage agent, access to the library drives that
are available to the Tivoli Storage Manager server. Path-definition requirements
depend on the type of device that you are using.
The result of completing this step is shown in Figure 8.
Tivoli Storage Manager Client Workstation
Storage Agent
device name: /dev/mt1
SAN
Tape Library Drive
Tivoli Storage Manager Server - TSMSRVER
define drive sanlib1 drive1
define path tsmsrver drive1 srctype=server
destype=drive library=sanlib1 device=/dev/mt6
define path storagnt drive1 srctype=server
destype=drive library=sanlib1 device=/dev/mt1
Figure 8. Device information
Before you begin defining paths to your SAN drives, consider the following
guidelines:
v If you have not already done so, obtain the names of your tape or disk devices.
If you are configuring tape devices, review the device names. The name of a
tape device as known to the server will probably not match the name of the
same tape device as known to the storage agent.
v You must define paths on the library manager from the storage agent to each
drive that the storage agent will access. In addition, you must define a path
from the library manager to each drive so that the storage agent can use the
drive.
For information about defining paths, see the following topics:
v “Defining paths for tape devices” on page 28
v “Defining paths for tape devices” on page 28
Chapter 3. Installing and configuring tape-library and file-device-sharing environments
27
Related tasks
“Obtaining device information” on page 17
You use the device information when defining paths for the server that functions
as the library manager. Device information is obtained from the system on which
the storage agent is installed. If you are configuring a FILE Library, you do not
need device information.
Defining paths for tape devices
You must define paths on the Tivoli Storage Manager server using the device
names as identified by the storage agent on each client system.
To define paths, issue the DEFINE PATH command on the Tivoli Storage Manager
server designated as the library manager. For example:
define path storagnt drive1 srctype=server desttype=drive
library=sanlib1 device=/dev/rmt/3st
define path storagnt drive1 srctype=server desttype=drive
library=sanlib1 device=/dev/rmt/4mt
where 3st represents an IBM tape device and 4mt represents a non-IBM tape
device.
Be sure that the device names are what the storage agent identifies on each client
system. For the same tape device, the device name as known to the server will
probably not match the device name as known to the storage agent. Failures can
occur if incorrect device information is provided in the DEFINE PATH command.
For details about this command, see the Administrator’s Reference.
Depending on the operating system of the Tivoli Storage Manager server, there
might not be a quick way to confirm which device names on the storage agent
correspond to device names on the Tivoli Storage Manager server without using a
trial-and-error method.
To confirm device names, work with one online drive at a time, and cycle through
the storage agent device names until you can run a successful backup. The server
cannot validate path information that is provided on the server for use by the
storage agent.
When defining paths on the server, you can specify AUTODETECT=YES to
automatically update the serial number for a drive or library in the database. The
updated serial number is the same serial number that the drive reports to Tivoli
Storage Manager. After completing a backup to verify LAN-free configuration, you
can issue the QUERY DRIVE command to determine the device name from the
storage agent.
For a review of the results of the steps that you have just completed, see:
Figure 8 on page 27
Related tasks
“Verifying the LAN-free configuration” on page 29
To ensure LAN-free data movement, you must verify that the hardware and
software components are configured correctly.
28
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Defining paths for disk devices
You must define paths on the Tivoli Storage Manager server using the disk device
names as seen by the storage agent on each client system.
For example, suppose the directory d:\tsmdata\server1 is exported on the NFS
server running on the Tivoli Storage Manager server. On the storage agent, the
directory is NFS mounted as /tsmdata/server1. Issue the DEFINE PATH command
to create the path for this scenario..
In the following example, disklib1 represents the destination file drive in the disk
library named disklib:
define path storagnt disklib1 srctype=server desttype=drive library=disklib
device=file directory="/tsmdata/server1/fs1,/tsmdata/server1/fs2"
Recommendation: Make each directory correspond to a file system on a separate
physical drive. The server cannot validate PATH information that is provided on
the server for use by the storage agent. Failures can occur if incorrect device
information is provided in the DEFINE PATH command.
If you specify multiple directories for the device class associated with the FILE
library, you must specify the same number of directories for each path to the FILE
library. To keep the device class and path synchronized, do not change or move
existing directories on the server that the storage agent is using. Adding directories
is permitted. Specifying a mismatched number of directories can cause a runtime
failure. For more information, see the Administrator’s Guide.
For details about the DEFINE PATH command, see the Administrator’s Reference.
(z/OS data-manager server) Formatting volumes for LAN-free data
movement
If you are using the z/OS data manager server, LAN-free sessions to
sequential-access storage pools will fail if the pools do not contain any formatted
volumes and do not allow automatic formatting.
Format volumes before using them in sequential-access storage pools that support
LAN-free data movement. For information about how to format volumes, see the
FORMAT LFVOLUME command in the z/OS Administrator’s Reference.
Verifying the LAN-free configuration
To ensure LAN-free data movement, you must verify that the hardware and
software components are configured correctly.
Before beginning this procedure, verify that the server is online and running.
To verify LAN-free configuration:
1. Start the storage agent:
a. Reboot the client system.
b. Change to the storage agent directory and issue the DSMSTA command.
When the storage agent starts, it contacts all available shared libraries,
including those libraries that do not have a defined path defined. As a result, a
delay might occur during startup processing. The storage agent also determines
if the Tivoli Storage Manager server is a library client or library manager. If the
Chapter 3. Installing and configuring tape-library and file-device-sharing environments
29
server is a library client, the storage agent attempts to define itself to the library
manager if it is not known to the library manager.
2. Specify the DISPLAYLFINFO=YES option in your server options file. Doing so
allows the accounting records and summary table entries to report the storage
agent name.
Important: This option might cause existing outboard automation that relies
on the summary table or accounting records to fail to recognize some activities
for a given client. Before setting this option, consider how this outcome might
affect your environment.
3. To determine which destinations for a node are capable of LAN-free data
movement, issue the VALIDATE LANFREE command. The output of this
command also provides explanations about destinations that are not LAN-free
capable. Use this information to correct your configuration before proceeding to
the next step.
4. Run a backup operation from the client.
5. If you receive a message indicating that the backup failed, verify the following:
v The Tivoli Storage Manager server is running. If the Tivoli Storage Manager
server is not running, the storage agent will not start.
v The client, storage agent, and server are communicating with each other as
expected.
v The paths to the drives are correctly defined.
v All drives in a library have defined paths from the server.
If you retry the backup operation after the first failure, the client attempts to
use the LAN connection for data movement. To force LAN-free data movement,
stop and restart the client.
Determining whether the data movement was LAN-free
Messages and backup reports can indicate whether LAN-free operations are
successful. You can also use the QUERY SESSION and QUERY ACTLOG
commands to verify LAN-free operations.
Use one or more of the following methods to determine whether the data
movement was LAN-free:
v When data transfers on a LAN-free path, the following message displays
informing you that the client is starting a session with the storage agent and that
LAN-free data movement occurred:
ANR0415I Session session_number proxied by storage_agent_name for node
your_node_name
v View the backup report issued when backup processing completes. If LAN-free
data movement occurred, the number of LAN-free bytes that are transferred is
greater than zero.
v Verify that the proper sessions have been established and that LAN-free data
movement is occurring:
1. Using a Tivoli Storage Manager administrative command-line client, log in to
the storage agent and the Tivoli Storage Manager server.
2. Issue the QUERY SESSION command for the node that is running the
LAN-free backup. In the command output, look for information about bytes
sent and bytes received. If LAN-free data movement is occurring:
– Querying a session on the storage agent shows bytes received for the node
increasing to the total amount of data being backed up.
30
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
– Querying a session on the Tivoli Storage Manager server shows a very
small number of bytes of metadata received for the same node.
If the node’s session has these characteristics, the data movement is
LAN-free.
Tip: During a failover when the storage agent is sending data directly to the
server by proxy because it cannot store the data directly, the session statistics on
the server show a much higher byte count.
v Issue either of the following QUERY ACTLOG commands on the server to
which the client is connected:
– query actlog search=storage_agent_name msgno=8337
– query actlog search=storage_agent_name
If the query locates entries in the activity log that relate to the storage agent, the
client is using LAN-free data transfer.
Chapter 3. Installing and configuring tape-library and file-device-sharing environments
31
32
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Chapter 4. Installing and configuring external library
environments
An external library is controlled by software acquired from another vendor, such as
Sun StorageTek ACSLS software. To use the drives in the external library, the Tivoli
Storage Manager server (storage agent) acts as a client application to the software.
Before beginning this procedure:
v Make sure that you understand the overall installation and configuration process
because it takes place on different systems at different times.
v Be sure that you have the information recorded in the configuration-information
work sheets.
v Obtain an external library manager capable of exploiting the external library
interface, for example, IBM Integrated Removable Media Manager. For details
about interfaces, see the Administrator’s Guide.
v You can use the Sun StorageTek LibraryStation to manage the environment
instead of ACSLS. However, if you are using a z/OS data manager server, Sun
StorageTek LibraryStation is required.
The major installation and configuration steps are:
1. “Establishing network connections”
2. Installing software on client systems:
“Installing software on UNIX and Linux client systems” on page 34
3. “Defining the storage agent and configuring devices on the server” on page 37
4. “Verifying the LAN-free configuration” on page 41
5. “Determining whether the data movement was LAN-free” on page 41
Related concepts
“External Libraries” on page 10
If Tivoli Storage Manager native library (SCSI, 3494, and ACSLS) support cannot be
used, the alternative is to configure external library support.
Related reference
“Obtaining system configuration information for clients and servers” on page 13
To be more efficient, obtain client- and server-system information before installing
and configuring the storage agent.
Establishing network connections
Tivoli Storage Manager for Storage Area Networks requires specific levels and
models of hardware and software. You must ensure that your system meets these
requirements.
To establish network connections, attach the server system and the client systems
to the LAN and to the SAN along with appropriate storage devices. For details
levels and models of hardware and software, see http://www.ibm.com/software/
sysmgmt/products/support/IBMTivoliStorageManager.html.
© Copyright IBM Corp. 2000, 2009
33
Installing software on UNIX and Linux client systems
The backup-archive client or the Tivoli Data Protection client software, the Tivoli
Storage Manager API, and the storage agent are installed on client systems.
Perform the following tasks to install the software:
1. “Installing or upgrading the client and API”
2. Installing and configuring the storage agent:
“Installing and configuring the storage agent” on page 35
Related concepts
“Communications between the client, storage agent, and Tivoli Storage Manager
server” on page 4
Configuration tasks link the storage agent, the client, and the Tivoli Storage
Manager server.
Installing or upgrading the client and API
The client and API software must be at the appropriate level. Software
configuration is required to enable communications.
Before beginning this procedure:
v Verify that the client system meets the prerequisites for client software.
v Be sure you have the information recorded in the configuration-information
work sheets.
Additional information is available from the following sources:
v For details about the client-system prerequisites and about the files and file
options described in this procedure, see the Backup-Archive Clients Installation and
User’s Guide.
v For details about client software and the API, see the Web site at
http://www.ibm.com/software/sysmgmt/products/support/
IBMTivoliStorageManager.html.
v For details about storage agent and backup-archive client compatibility, see the
Web site at http://www.ibm.com/support/entdocview.wss?rs=663
&context=SSGSG7&q=5.1+os%2F390+supported+windows+clients+and+tsm
&uid=swg21053218.
To install or upgrade the client and API software:
1. If the client software and the API are not already installed, install them now. To
ensure software compatibility, check the Web site for Tivoli Storage Manager
storage agent and backup-archive client compatibility. You can download the
latest software levels from the Tivoli Storage Manager product support Web
site.
Remember: If you are using the storage agent to support multiple clients,
install or upgrade the client and API software on each supported client.
2. Modify the dsm.sys client options file:
a. Locate the options file and open it. The file can be in one of several places,
such as the installation directory, or in a location pointed to by an
environment variable.
b. Specify a value for the SERVERNAME option to identify the stanza. For
example: servername server_c.
34
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
c. Specify the communications method between the Tivoli Storage Manager
client and server. For example:
commmethod tcpip
tcpserveraddress server_c.example.com
tcpport 1502
The example uses a TCPPORT of 1502. However, the default TCPPORT is
1500.
Keep the file open for the next step.
d. Edit the dsm.opt file to specify the SERVERNAME option that identifies the
stanza that you edited in 2b on page 34. For example: servername server_c.
Remember: The SERVERNAME option in dsm.sys must match the
SERVERNAME option in dsm.opt. However, it is unrelated to and does not
need to match the SERVERNAME option that is defined for the storage
agent in dsmsta.opt. For a description of the SERVERNAME option in
dsm.sys and dsm.opt, see the Backup-Archive Clients Installation and User’s
Guide.
e. Add options to specify that the client will use SAN-attached devices when a
LAN-free path is available during backup, restore, archive, and retrieve
processing.
Add the options to the same dsm.sys stanza that was edited in step 2b on
page 34.
enablelanfree yes
lanfreecommmethod tcpip
lanfreetcpport 1500
or
lanfreecommmethod sharedmem
lanfreeshmport 1510
Related reference
“Obtaining system configuration information for clients and servers” on page 13
To be more efficient, obtain client- and server-system information before installing
and configuring the storage agent.
Installing and configuring the storage agent
The storage agent must be installed on a client system that has connections to
storage resources on the SAN.
Before beginning this procedure:
v Verify that your system meets the hardware and software requirements.
v Be sure that you have the information recorded in the configuration-information
work sheets.
To reduce workload and processing time and to optimize LAN-free performance,
do not install the storage agent and the Tivoli Storage Manager server on the same
system.
To install and configure the storage agent:
1. Log in as the root user.
2. Load the storage agent CD into the selected drive.
3. For a list of packages that you can install, enter the following command:
/usr/sbin/pkgadd -d /cdrom/cdrom0
Chapter 4. Installing and configuring external library environments
35
In this example the CD-ROM name is /cdrom/cdrom0; the name of your
CD-ROM may be different.
Select the appropriate package:
TIVsmSsta
The storage agent application
TIVsmSdev
The device driver package for non-IBM devices.
To load the selected package, use the PKGADD command. The installation
program automatically installs the storage agent based on the level of Sun
Solaris on the installation system.
Loading the storage agent files can take several minutes. It can also take a few
minutes for the installation to begin after the server package has been selected.
4. Enter y when the system issues the following message:
This package contains scripts which will be executed with super-user
(root) permission during the process of installing the package. Do you
want to continue with the installation of this package?
5. To eject the CD after the installation is complete, enter the following commands
from a root user command prompt:
cd /
eject cdrom
6. Ensure that the Tivoli Storage Manager server is running. Then, Use the
information that you collected in the configuration-information worksheets to
issue the DSMSTA SETSTORAGESERVER command. For example:
dsmsta setstorageserver myname=storagnt mypassword=fun4me
myhladdress=agent.example.com
servername=tsmsrver serverpassword=not4u
hladdress=tsmsrver.example.com lladdress=1502
When configuring the storage agent using the DSMSTA SETSTORAGESERVER
command, use addresses that correspond to the communications method used
by the backup-archive client. The backup-archive client supports either IPv4
(COMMMETHOD TCPIP) or IPv6 (COMMMETHOD V6TCPIP), but not both
at the same time. The command generates the following lines in the device
configuration file for the storage agent:
set staname storagnt
set stapassword xxxxxxx
set stahladdress agent.example.com
define server tsmsrver serverpassword=xxxxxxxxxxx
hladdress=tsmsrver.example.com lladdress=1502
The passwords (shown here as xxxxxxxx) are encrypted in the file. Save the file
to the same directory as the executable and close it.
The command also generates the following line in the dsmsta.opt file:
servername tsmsrver
The default installation directory for the storage agent is /opt/tivoli/tsm/
StorageAgent/bin.
36
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Related reference
“Obtaining system configuration information for clients and servers” on page 13
To be more efficient, obtain client- and server-system information before installing
and configuring the storage agent.
“The storage agent options file” on page 47
The storage agent options file contains the name of the server with which the
storage agent communicates, along with other options. Normally, you do not need
to make any changes to the options file unless your Tivoli Storage Manager server
changes.
“The device configuration file for the storage agent” on page 50
The device configuration file for the storage agent includes information about the
storage agent and about the Tivoli Storage Manager server with which the storage
agent communicates and that is managing the SAN-attached libraries and drives
that the storage agent uses.
Defining the storage agent and configuring devices on the server
To set up LAN-free communications on the Tivoli Storage Manager server, you
need to set up server-to-server communication, define the client’s storage agent to
the server, and configure the paths to the library.
Before beginning this procedure, be sure that you have the information recorded in
the configuration-information work sheets.
Perform these tasks to define the storage agent and configure devices on the
server:
1.
2.
3.
4.
“Setting up server-to-server communication”
“Installing an external media manager” on page 38
“Defining storage agents to the Tivoli Storage Manager server” on page 38
“Configuring a path to the library manager” on page 38
5. “Defining paths for ACSLS” on page 39
6. “Setting the LAN-free destination” on page 40
7. “Confirming client node registration and configuration” on page 40
Related concepts
“Communications between the client, storage agent, and Tivoli Storage Manager
server” on page 4
Configuration tasks link the storage agent, the client, and the Tivoli Storage
Manager server.
Setting up server-to-server communication
Server-to-server communication is required for Tivoli Storage Manager servers and
storage agents to share library devices on a SAN
To set up server-to-server communication, issue the following commands on the
Tivoli Storage Manager server. Replace the values in the example with values from
the configuration-information work sheet.
set
set
set
set
set
servername tsmsrver
serverpassword not4u
serverhladdress tsmsrver.example.com
serverlladdress 1502
crossdefine on
Chapter 4. Installing and configuring external library environments
37
These commands establish the server’s name, password, TCP/IP address, and port.
They also allow other servers to define a connection on this server.
Verify that the password has been set for the server by issuing the QUERY STATUS
command from a Tivoli Storage Manager administrative command line. The value
of the Server Password Set field in the command output must be YES.
For details about server-to-server communication, see the Administrator’s Guide.
Installing an external media manager
If you are using an ACSLS-managed external library, install middleware (for
example, IBM Integrated Removable Media Manager) that enables an external
library. For installation information, see the product’s documentation.
Defining storage agents to the Tivoli Storage Manager server
For each client the will use LAN-free data transfer, define a storage agent to the
server as if the storage agent is another server.
To define the storage agent, issue the DEFINE SERVER command from the Tivoli
Storage Manager server that will manage the client’s data. Use the same name and
password that you specified for the storage agent when you installed it on the
client system, for example,
define server storagnt serverpassword=fun4me
hladdress=agent.tucson.ibm.com lladdress=1500 validateprotocol=all
The VALIDATEPROTOCOL parameter in the example is optional. This parameter
specifies whether a cyclic redundancy check will be performed to validate data on
all metadata transferred between the storage agent and the Tivoli Storage Manager
server.
For details about data validation, see the Administrator’s Guide. For details about
the DEFINE SERVER command, see the Administrator’s Reference.
You must also define the storage agent to the library manager. The storage agent
needs to be able to contact the library manager directly when making mount
requests. If the storage agent is only defined to the library client, it will attempt to
use information from the client to define itself to the library manager. If the storage
agent is unable to define itself to the library manager, then you must define the
storage agent manually using the DEFINE SERVER command issued from the
library manager, for example,
define server storagnt serverpassword=fun4me
hladdress=agent.tucson.ibm.com lladdress=1500
Configuring a path to the library manager
Configure a path to the library manager.
The procedure for configuring a path to the library manager depends on whether
you are using a shared ACSLS library manager or an ACSLS-managed external
library.
v If you are using a shared ACSLS library manager, configure a path to the library
manager:
1. Define a library type of ACSLS. For example:
define library libmgr1 libtype=ACSLS shared=YES
primarymanager=tsmsrvr
2. Define a path from the server to the library manager. For example:
38
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
define path tsmsrver libmgr1 srctype=server desttype=library
3. Define a device class with a device type of SERVER. For example:
define devclass device_class_name library=libmgr1
devtype=server servername=tsmsrvr
4. Define the storage pool. For example:
define stgpool pool_name device_class_name pooltype=primary
v If you are using an ACSLS-managed external library, configure a path to the
external library manager.
1. Define a library type of EXTERNAL. For example:
define library stk-lib libtype=external
If a library name remains constant but the library type changes from
EXTERNAL to shared ACSLS, stop and restart the storage agent to register
this change.
2. Define a path from the server to the external media manager. For example:
define path tsmsrver stk-lib srctype=server desttype=library
externalmanager=path_name
In the example, the path provided for the external manager depends on the
operating system on which Tivoli Storage Manager server runs.
3. Define a device class with a device type of ECARTRIDGE. For example:
define devclass device_class_name library=library_name
devtype=ecartridge format=drive
If you are using Sun StorageTek 9840B tape devices with the z/OS data
manager server, the value of the FORMAT parameter of the device class
must match the device type of the tape drive (9840B).
4. Define the storage pool. For example:
define stgpool pool_name device_class_name pooltype=primary
Defining paths for ACSLS
If you are using a shared ACSLS library manager, you must define a path from the
storage agent to the library manager. If you are using an ACSLS-managed external
library, you must define a path from the storage agent to the external manager.
v To define a path for a shared ACSLS library manager, use the DEFINE PATH
command. For example:
define path storagnt libmgr1 srctype=server desttype=library
v To define a path for an ACSLS-managed external library, use the DEFINE PATH
command and define a path to the external media manager. For example:
define path storagnt stk-lib srctype=server desttype=library
externalmediamanager=path_name
For details about the DEFINE PATH command, see the Administrator’s Reference.
Chapter 4. Installing and configuring external library environments
39
Setting the LAN-free destination
The destination for data must be a LAN-free capable storage pool.
To set a LAN-free destination:
1. Define a copy group with its destination being the LAN-free capable storage
pool (You created this storage pool as part of the procedure of configuring a
path to the library manager.) For example,
define copygroup sandirect sandirectpolicy sandirectdefmft
type=backup destination=storage_pool_name
2. Activate the policy set, for example,
activate policyset sandirect sandirectpolicy
For details about changing policy for clients that can use SAN drives, see the
Administrator’s Guide. For details about the commands, see the Administrator’s
Reference.
Remember:
v If you decide not to use the default management class for the SAN drives, create
a new management class. Clients that use the SAN drives need an include
statement to bind their files to this new management class. For details about the
include-exclude list, see the Backup-Archive Clients Installation and User’s Guide.
v With a hierarchical storage management (HSM) client configured for LAN-free
data movement, the management class (not the copy group) is set to a LAN-free
capable storage pool.
Related tasks
“Configuring a path to the library manager” on page 38
Configure a path to the library manager.
Confirming client node registration and configuration
Client nodes must be registered and configured for LAN-free backups.
To verify that node settings are correct, issue the following command:
query node node_name format=detailed
If node settings are not correct, issue the UPDATE NODE command to adjust
settings for the node. If the node has not been registered and configured for
LAN-free backups, register the node with the REGISTER NODE command.
To help tune the use of your LAN and SAN resources for LAN-free data
movement, you can control the path that data transfers take for clients that have
LAN-free data movement capability. For each client, you can select whether data
read/write operations use the LAN path, the LAN-free path, or either path. You
can specify these settings with the REGISTER NODE and UPDATE NODE
commands.
If the node belongs to a multi-threaded client and there are drives available, the
MAXNUMMP parameter might restrict the number of drives that are available for
the storage agent to use on behalf of the client. Specify the MAXNUMMP
parameter on the REGISTER NODE or UPDATE NODE command.
For details about commands, see the Administrator’s Reference.
40
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Verifying the LAN-free configuration
To ensure LAN-free data movement, you must verify that the hardware and
software components are configured correctly.
Verifying the LAN-free configuration
To verify the LAN-free configuration:
1. Start the storage agent:
a. Restart the client system.
b. Change to the storage agent directory and issue the DSMSTA command.
2. Run a backup operation from the client.
3. Log in to the Tivoli Storage Manager server and storage agent using a Tivoli
Storage Manager administrative command-line client.
4. To verify that the backup is LAN-free and the proper sessions have been
established, issue the QUERY SESSION command. In the command output,
look for information about bytes sent and bytes received. If LAN-free data
movement is occurring:
v Querying a session on the storage agent shows bytes received for the node
increasing to the total amount of data being backed up.
v Querying a session on the Tivoli Storage Manager server shows a very small
number of bytes (metadata) received for the same node.
If the node’s session has these characteristics, and you receive a message stating
that the backup was successful, you configured your system correctly.
There are several ways to use the QUERY SESSION command. If the process is
running in the foreground, you can issue the command on the storage agent
console. Alternatively, you can use a command-line client to connect to the
storage agent on the administration port of the storage agent. Use the same
administrator ID and password for this command as you use on the server.
5. If you receive a message saying that the backup has failed, ensure the
following:
v The Tivoli Storage Manager server is running. If the Tivoli Storage Manager
server is not running, the storage agent will not start.
v The client, storage agent, and server are communicating with each other as
expected.
v The mount and message is displayed on the storage agent console.
If you retry the backup operation after the first failure, the client attempts to
use the LAN connection for data movement. To force LAN-free data movement,
stop and restart the client.
Determining whether the data movement was LAN-free
Messages and backup reports can indicate whether LAN-free operations are
successful. You can also use the QUERY SESSION and QUERY ACTLOG
commands to verify LAN-free operations.
Chapter 4. Installing and configuring external library environments
41
Determining whether the data movement was LAN-free
To determine whether data movement is LAN-free, use one or both of the
following methods:
v Monitor the QUERY SESSION output against the node that is running the
LAN-free backup. Verify that the proper sessions have been established:
1. Log in to the Tivoli Storage Manager server and storage agent using a Tivoli
Storage Manager administrative command-line client.
2. To verify that the backup is LAN-free and the proper sessions have been
established, issue the QUERY SESSION command. In the command output,
look for information about bytes sent and bytes received. If LAN-free data
movement is occurring:
– Querying a session on the storage agent shows bytes received for the node
increasing to the total amount of data being backed up.
– Querying a session on the Tivoli Storage Manager server shows a very
small number of bytes (metadata) received for the same node.
If the node’s session shows these characteristics, the data movement is LAN-free.
Remember: During a failover where the storage agent is sending data directly
to the server by proxy because it cannot store the data directly, the QUERY
SESSION statistics on the server show a much higher byte count.
v Issue either of the following QUERY ACTLOG commands on the server to
which the client is connected:
query actlog search=storage_agent_name msgno=8337
query actlog search=storage_agent_name
If the query locates entries in the activity log that relate to the storage agent, the
client is using LAN-free data transfer.
42
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Appendix A. Administration and configuration information
You can start and stop the storage agent manually or automatically. You can also
add communication information to the device configuration file and the storage
agent options file.
Starting and stopping the storage agent
You can configure the storage agent to start automatically when the system
restarts. You can also start and stop the storage agent manually.
Automating the storage agent startup
When the storage agent is installed, an entry is made to the inittab that enables the
storage agent to start automatically. You can use scripts, located in the storage
agent installation directory, to modify the inittab.
v addtoinit (or addtoinit console)
Adds an entry to the inittab that redirects output to /dev/console and enables
automatic startup. For example:
aa:234:once:/opt/tivoli/tsm/StorageAgent/bin/dsmsta.rc >/dev/console
2<>/dev/console
v addtoinit null
Adds an entry to the inittab that redirects output to /dev/null and enables
text-based login to the console. For example:
aa:234:once:/opt/tivoli/tsm/StorageAgent/bin/dsmsta.rc >/dev/null
v addtoinit saved
Restores the inittab entry from storage_agent _home_directory/oldinit to
/etc/inittab. If more than one entry exists in the /etc/inittab file, addtoinit
saved restores the first entry only.
v removefrominit
Removes any entry that refers to storage_agent_home_directory/dsmsta.rc and
records these entries in a file called storage_agent_home_directory/oldinit. If more
than one entry exists in the /etc/inittab file, removefrominit stores all entries in
the oldinit file.
Manually starting and stopping the storage agent
You can start and stop the storage agent from the storage agent directory. You can
also use an administrative client to issue commands supported by the storage
agent.
To start the storage agent:
1. Restart the client system.
2. From the operating system command line, change to the storage agent directory
(the default is /opt/tivoli/tsm/StorageAgent/bin) and issue the DSMSTA
command.
To stop the storage agent, issue the halt command.
In most cases it is not necessary to halt and restart a LAN-free storage agent to
pick up changes from the data manager server. However, restarting the storage
© Copyright IBM Corp. 2000, 2009
43
agent might be necessary if an attempt was made to change storage pool, library,
device class, or drive information while LAN-free data movement was in process.
The effects on LAN-free storage pools resulting from an attempted change are not
critical enough to create serious problems. The storage agent keeps a list of storage
pools, libraries, and device classes in memory to determine potential LAN-free
destinations. Target volume selection occurs on the data manager server.
Certain storage pool attributes can result in failed requests rather than the LAN
failover by the storage agent. If the storage agent accurately identifies a LAN-free
destination, the LAN-free operation will probably be successful. However, if the
storage agent inaccurately identifies a LAN-free destination and the server is
unable to process the request, the operation has advanced beyond the point when
LAN failover occurs, and the storage agent request does not succeed. If this occurs,
stop and restart the storage agent, and then retry the operation.
Setting up LAN-free data movement using the Administration Center
wizard
To set up LAN-free data movement on the server in tape-library and
file-device-sharing environments, you can use the Enable LAN-free Data
Movement wizard in the Administration Center.
1. Install or upgrade the client and API software:
v “Installing or upgrading the client and API” on page 20
2. Specify the DEVCONFIG option in the storage agent options file and issue the
DSMSTA SETSTORAGESERVER command to initialize the storage agent and to
update the device configuration file and the storage agent options file:
v See steps 6 and 7 in “Installing and configuring the storage agent” on page
22.
3. “(z/OS data-manager server) Formatting volumes for LAN-free data
movement” on page 29
4. “Verifying the LAN-free configuration” on page 29
5. “Determining whether the data movement was LAN-free” on page 30
Configuring multiple clients to use the same storage agent
You can configure two or more clients to use the same storage agent.
To configure clients:
v If the clients reside on the same system as the storage agent, set the appropriate
options and values in the client’s dsm.sys file.
v If the clients do not reside on the same system as the storage agent, set the
following options with the appropriate values:
– LANFREECOMMMETHOD TCPIP
– LANFREETCPSERVERADDRESS
Specify the TCP/IP address of the system where the storage agent is installed.
– LANFREETCPPORT
Specify the same TCP/IP port address as specified by the TCPPORT option in
the storage agent options file dsmsta.opt.
44
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
DSMSTA SETSTORAGESERVER
Use the DSMSTA SETSTORAGESERVER command to initialize the storage agent
and add communication information to the device configuration file and the
storage agent options file dsmsta.opt.
Use this utility on the client system where the storage agent has been installed.
This utility does not remove any previous entries in the files. It appends
information to the existing files. The option DEVCONFIG, which sets a name for
the device configuration file, must be in the dsmsta.opt file for the command to
work. See “Examples” on page 46.
When configuring the storage agent using the DSMSTA SETSTORAGESERVER
command, use addresses that correspond to the communications method used by
the backup-archive client. The backup-archive client supports either IPv4
(COMMMETHOD TCPIP) or IPv6 (COMMMETHOD V6TCPIP), but not both at
the same time.
Syntax
DSMSTA SETSTORAGESERVER MYName =
MYPAssword =
MYHLAddress =
storage_agent_password
storage_agent_hladdress SERVERName =
SERVERPAssword =
LLAddress =
storage_agent_name
server_password HLAddress =
server_name
server_tcpip_address
server_tcpip_port
Parameters
All parameters are required. Allowed abbreviations for the options are shown in
uppercase letters.
MYName
Specifies the name of the storage agent. This name appears in the SET
STANAME command that is inserted into the device configuration file.
You must use the same name when you define the storage agent as a server to
the Tivoli Storage Manager server.
MYPAssword
Specifies the password of the storage agent. This value is encrypted and used
in the SET STAPASSWORD command that is inserted into the device
configuration file.
You must use the same password when you define the storage agent as a
server to the Tivoli Storage Manager server.
MYHLAddress
Specifies the TCP/IP address of the storage agent. This value is used internally
in the SET STAHLADDRESS command that is inserted into the device
configuration file.
Appendix A. Administration and configuration information
45
SERVERName
Specifies the name of the Tivoli Storage Manager server. This name appears in
theDEFINE SERVER command that is inserted into the device configuration
file.
SERVERPAssword
Specifies the password of the server. This value is encrypted and appears in
the SERVERPASSWORD parameter of the DEFINE SERVER command that is
inserted into the device configuration file.
HLAddress
Specifies the TCP/IP address of the server. This value is used in the
HLADDRESS parameter of the DEFINE SERVER command.
LLAddress
Specifies the TCP/IP port on which to access the server. This value is used in
the LLADDRESS parameter of the DEFINE SERVER command.
Examples
Issue the DSMSTA SETSTORAGESERVER command with the following
information:
v Storage agent
Name: storagnt
Password: fun4me
TCP/IP address: agent.example.com
v Tivoli Storage Manager server
Name: tsmsrver
Password: not4u
TCP/IP address: tsmsrver.example.com
TCP/IP port: 1502
The command is:
dsmsta setstorageserver myname=storagnt mypassword=fun4me
myhladdress=agent.example.com
servername=tsmsrver serverpassword=not4u
hladdress=tsmsrver.example.com lladdress=1502
The command generates the following lines in the device configuration file for the
storage agent:
set staname storagnt
set stapassword xxxxx
set stahladdress agent.example.com
define server tsmsrver serverpassword=xxxxxxxx
hladdress=tsmsrver.example.com lladdress=1502
The passwords (shown as xxxxxxxx) are encrypted in the file.
The command also generates the following line in the dsmsta.opt file for the
storage agent:
servername tsmsrver
46
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Related tasks
“Installing and configuring the storage agent” on page 22
The storage agent must be installed on a client system that has connections to
storage resources on the SAN.
The storage agent options file
The storage agent options file contains the name of the server with which the
storage agent communicates, along with other options. Normally, you do not need
to make any changes to the options file unless your Tivoli Storage Manager server
changes.
The options file for the storage agent is named dsmsta.opt. The dsmsta.opt file is
located where the storage agent program was installed. The default path is:
/opt/tivoli/tsm/StorageAgent/bin
For detailed information about these options, see the Administrator’s Reference.
For detailed information about the COMMMETHOD and
LANFREECOMMMETHOD options, see the Backup-Archive Clients Installation and
User’s Guide.
Required options
Note: Uppercase letters indicate allowed abbreviations.
DEVCONFig file_name
The name of the device configuration file for the storage agent. A typical
name for the file is devconfig.
SERVERName server_name
The name of the Tivoli Storage Manager server with which the storage
agent communicates. The DSMSTA SETSTORAGESERVER command
inserts this option.
TCPPort number
Specifies the port number on which the server TCP/IP communication
driver is to wait for requests for client sessions.
Using different port numbers for the options TCPPORT and
TCPADMINPORT enables you to create one set of firewall rules for client
sessions and another set for other session types (administrative sessions,
server-to-server sessions, SNMP subagent sessions, storage agent sessions,
library client sessions, managed server sessions, and event server sessions).
If the two port numbers are different, separate threads will be used to
service client sessions and the other session types. If you allow the two
options to use the same port number (by default or by explicitly setting
them to the same port number), a single server thread will be used to
service all session requests.
Additional options
ADMINONClientport
Specifies whether or not the TCPPORT can be used by administrative
sessions. You can specify one of the following values:
v YES (default)
Appendix A. Administration and configuration information
47
If the option is set to YES, or if the TCPPORT and TCPADMINPORT are
the same value (the default), then the administrative sessions can use the
TCPPORT.
v NO
If the option is set to NO, and if the TCPADMINPORT value is different
than the TCPPORT value, then administrative sessions cannot use
TCPPORT.
COMMTimeout seconds
Specifies the maximum number of seconds that the server waits for an
expected client message during an operation that causes a database update.
The default value is 60. The minimum value is 1. If the length of time
exceeds this time-out, the server ends the session with the client. You may
want to increase the time-out value to prevent clients from timing out.
Clients may time out if there is a heavy network load in your environment
or when they are backing up large files.
IDLETimeout minutes
Specifies the maximum number of minutes that a client session can be idle
before the server cancels the session. The default value is 15 minutes. The
minimum value is 1 minute. You may want to increase the time-out value
to prevent clients from timing out if there is a heavy network load in your
environment. Note, however, that a large number of idle sessions could
prevent other users from connecting to the server.
MAXSessions number_of_sessions
Specifies the maximum number of simultaneous client sessions that can
connect with the server. The default value is 25 client sessions. The
minimum value is 2 client sessions. The maximum value is limited only by
available virtual memory size or communication resources.
MSGSTACKTRACE on|off
Specifies that a list of functions will be shown on the server console, and
will also be directed to the activity log after specific messages have been
issued. The output will help the Tivoli Storage Manager service team to
diagnose specific problems quicker. It is recommended that this option be
set to ON.
RESOURCETimeout minutes
Specifies the maximum number of minutes that a storage agent waits for a
resource on the server. The default value is 60 minutes. The minimum
value is 1 minute.
For database resources and sessions on the storage agent, the Tivoli Storage
Manager resource monitor picks the shortest time-out value to start a
recovery process.
In contrast, in the case of library sharing, the resource monitor picks the
longest time for both the library manager and library client to recover. For
more efficient management of shared library resources, consider setting
resource time-outs at the same limit for all participants in a shared
configuration. In any case of error recovery, Tivoli Storage Manager always
defers to the longest timeout limit.
You should also specify this option in the server options file. The server
uses this option to monitor some of the storage agent sessions and
resources and will cancel sessions based on the value you specify.
48
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Important: If this option is specified in the server options file, that value
will override the value specified in the storage agent’s options file.
SANDISCOVERY
Specifies whether the Tivoli Storage Manager SAN discovery function is
enabled. When set to ON, the storage agent will perform SAN discovery in
the following instances:
v During storage agent initialization
v When the device path has been changed and there is a conflict between
the device serial number and the device path provided by the server
Using SAN discovery, the storage agent can automatically correct the
device’s special file name if it has been changed. If the HBA used by the
storage agent does not support SAN device mapping, you should set the
SANDISCOVERY option to OFF.
For information about Tivoli Storage Manager supported HBAs for SAN
device mapping, see the Tivoli Storage Manager product support site at
http://www.ibm.com/software/sysmgmt/products/support/
IBMTivoliStorageManager.html.
The storage agent does not require persistent binding with the SAN
discovery function enabled.
STAMaxpooledsessions number
Specifies the number of individual sessions that are allowed to start and
stop between the storage agent and the Tivoli Storage Manager server. The
range of values is 0 - 150, with a default of 25. Each session is governed by
the IDLETIMEOUT option and is stopped when the timeout value is
exceeded. If the storage agent needs more sessions than specified,
additional sessions are allowed. Although the default value is typically
sufficient, setting this option with a low number can adversely affect
performance. Be aware that if the storage agent has multiple client
sessions, increasing the value of this option will help support these
sessions.
TCPADMINPORT number
Specifies the port number on which the server TCP/IP communication
driver is to wait for requests for sessions other than client sessions. This
includes administrative sessions, server-to-server sessions, SNMP subagent
sessions, storage agent sessions, library client sessions, managed server
sessions, and event server sessions. The default is the value of TCPPORT.
Using different port numbers for the options TCPPORT and
TCPADMINPORT enables you to create one set of firewall rules for client
sessions and another set for the other session types listed above. By using
the SESSIONINITIATION parameter of REGISTER NODE and UPDATE
NODE, you can close the port specified by TCPPORT at the firewall, and
specify nodes whose scheduled sessions will be started from the server. If
the two port numbers are different, separate threads will be used to service
client sessions and the session types. If you allow the two options to use
the same port number (by default or by explicitly setting them to the same
port number), a single server thread will be used to service all session
requests.
Client sessions that attempt to use the port specified by TCPADMINPORT
will be terminated (if TCPPORT and TCPADMINPORT specify different
Appendix A. Administration and configuration information
49
ports). Administrative sessions are allowed on either port, (unless the
ADMINONCLIENTPORT option is set to NO) but by default will use the
port specified by TCPADMINPORT.
THROUGHPUTDatathreshold kilobytes_per_second
Specifies the throughput that client sessions must achieve to prevent
cancellation after THROUGHPUTTIMETHRESHOL minutes have elapsed.
The default value of 0 prevents examining client sessions for insufficient
throughput. Throughput is computed by adding send and receive byte
counts and dividing by the length of the session. The length does not
include time spent waiting for media mounts and starts at the time a client
sends data to the server for storage. The minimum value is 0; the
maximum is 99999999.
THROUGHPUTTimethreshold minutes
Specifies the threshold for examining client sessions and cancelling them if
the data throughput threshold is not met (see
THROUGHPUTDATATHRESHOLD). This threshold does not include time
spent waiting for media mounts. The time threshold starts when a client
begins sending data to the server for storage (as opposed to setup or
session housekeeping data). The default value of 200 prevents examining
client sessions for low throughput. The minimum value is 0; the maximum
is 99999999.
USELARGEBUFFERS yes|no
Specifies that large buffers are used for client-server communications. The
default of YES specifies that large buffers are used; NO specifies that they
are not used.
The device configuration file for the storage agent
The device configuration file for the storage agent includes information about the
storage agent and about the Tivoli Storage Manager server with which the storage
agent communicates and that is managing the SAN-attached libraries and drives
that the storage agent uses.
The file is typically named devconfig and is located with the storage agent
program:
/opt/tivoli/tsm/StorageAgent/bin
The DSMSTA SETSTORAGESERVER command normally generates the contents of
the file, and you can also use the command to add information to the file.
Typical contents of the device configuration file are as follows:
set staname storagnt
set stapassword fun4me
set stahladdress agent.example.com
define server tsmsrver serverpassword=not4u
hladdress=tsmsrver.example.com lladdress=1502
In this example, storagnt is the name of the storage agent and tsmsrver is the name
of the Tivoli Storage Manager server.
Properties
SET STANAME
Sets the name of the storage agent. The name must be the same as the
name that was used to define the storage agent as a server to the Tivoli
Storage Manager server.
50
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
SET STAPASSWORD
Sets the password of the storage agent. The password must be the same as
the password that was used when defining the storage agent as a server to
the Tivoli Storage Manager server. The password is encrypted.
SET STAHLADDRESS
Sets the TCP/IP address of the storage agent.
DEFINE SERVER
Define the Tivoli Storage Manager server with which the storage agent
communicates.
Appendix A. Administration and configuration information
51
52
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Appendix B. ACSLS legacy data migration and coexistence
If ACSLS shared-library support is not possible in your configuration, data
migration is required.
If your environment consists of Tivoli Storage Manager storage pools associated
with an ACSLS library type and an ECARTRIDGE device type, the library can be
updated with the SHARED=YES option to enable LAN-free data movement.
However, if your environment consists of Tivoli Storage Manager storage pools
associated with an ACSLS library type and a GENERICTAPE device type, data
migration is required rather than coexistence because Tivoli Storage Manager
ACSLS shared library support cannot co-exist with external library support.
Data migration of ACSLS to external library support is necessary only when Tivoli
Storage Manager ACSLS shared library support is not possible in your
configuration. The only situation where ACSLS shared library support is not
possible is when your environment does not contain a Tivoli Storage Manager
server installed on AIX, Solaris, or Windows to serve as the library manager.
Migrate the existing data from existing (old) storage pools to new storage pools
associated with the appropriate policy, device class, and library definitions.
Migration of data also allows the entire environment to be LAN-free, providing
better performance and better utilization of tape drives and media.
Figure 9 displays the normal migration path from an old storage pool containing
the data associated with the ACSLS library type to a new storage pool associated
with an EXTERNAL library type and an ECARTRIDGE device class.
Migration
Old Storage
Pool
Device Class
device type = generictape
New Storage
Pool
Device Class
device type = ecartridge
library type = EXTERNAL
library type = ACSLS
Figure 9. Legacy ACSLS data migration
Two methods to migrate data are:
© Copyright IBM Corp. 2000, 2009
53
v Use the IBM Tivoli Storage Manager server MOVE DATA command. This
method allows the legacy ACSLS data to move to a new storage pool without
moving any expired files in the aggregates. For more information, see the
Administrator’s Guide.
v Use the IBM Tivoli Storage Manager server storage pool reclamation function.
This method works by reclaiming the active files from the legacy ACSLS storage
pools. Reclamation processing, however, is very resource intensive and should
be performed during periods of little activity on the server. For more
information, see the Administrator’s Guide.
For detailed information about how to migrate from an external library
environment to a shared ACSLS library environment, see the Administrator’s Guide.
Related concepts
“External Libraries” on page 10
If Tivoli Storage Manager native library (SCSI, 3494, and ACSLS) support cannot be
used, the alternative is to configure external library support.
54
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Appendix C. Accessibility features for Tivoli Storage Manager
Accessibility features help a user who has a physical disability, such as restricted
mobility or limited vision, to use software products successfully. The major
accessibility features of Tivoli Storage Manager are described in this topic.
Accessibility features
The following list includes the major accessibility features in Tivoli Storage
Manager:
v Keyboard-only operation
v Interfaces that are commonly used by screen readers
v Keys that are discernible by touch but do not activate just by touching them
v Industry-standard devices for ports and connectors
v The attachment of alternative input and output devices
v User documentation provided in HTML and PDF format. Descriptive text is
provided for all documentation images.
The Tivoli Storage Manager Information Center, and its related publications, are
accessibility-enabled.
Keyboard navigation
Tivoli Storage Manager follows Sun Solaris operating-system conventions for
keyboard navigation and access.
Vendor software
Tivoli Storage Manager includes certain vendor software that is not covered under
the IBM license agreement. IBM makes no representation about the accessibility
features of these products. Contact the vendor for the accessibility information
about its products.
Related accessibility information
You can view the publications for Tivoli Storage Manager in Adobe® Portable
Document Format (PDF) using the Adobe Acrobat Reader. You can access these or
any of the other documentation PDFs at the IBM Publications Center at
http://www.ibm.com/shop/publications/order/.
IBM and accessibility
For more information about the commitment that IBM has to accessibility, see the
IBM Human Ability and Accessibility Center at http://www.ibm.com/able.
© Copyright IBM Corp. 2000, 2009
55
56
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user’s responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte character set (DBCS) information,
contact the IBM Intellectual Property Department in your country or send
inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
© Copyright IBM Corp. 2000, 2009
57
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758
U.S.A.
Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement, or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
If you are viewing this information in softcopy, the photographs and color
illustrations may not appear.
58
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corporation in the United States, other countries,
or both. If these and other IBM trademarked terms are marked on their first
occurrence in this information with a trademark symbol (® or ™), these symbols
indicate U.S. registered or common law trademarks owned by IBM at the time this
information was published. Such trademarks may also be registered or common
law trademarks in other countries. A current list of IBM trademarks is available on
the Web at ″Copyright and trademark information″ at http://www.ibm.com/legal/
copytrade.shtml.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
Linux is a registered trademark of Linus Torvalds in the United States, other
countries, or both.
Red Hat, the Red Hat ″Shadow Man″ logo, and all Red Hat-based trademarks and
logos are trademarks or registered trademarks of Red Hat, Inc., in the United
States and other countries.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Other company, product, or service names may be trademarks or service marks of
others.
Notices
59
60
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Glossary
A glossary is available with terms and definitions for the IBM Tivoli Storage
Manager server and related products.
The glossary is located in the Tivoli Storage Manager Version 6.1 information
center: http://publib.boulder.ibm.com/infocenter/tsminfo/v6
© Copyright IBM Corp. 2000, 2009
61
62
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
Index
A
F
accessibility features 55
ACSLS support
data migration and coexistence issues 53
installing external library environments
(ACSLS-managed) 33
overview and planning 10
ACSLS-managed library sharing 10
administration and configuration 43
automating storage agent startup 43
FILE library
concurrent access to volumes 12
configuration considerations 9
disk devices 24
fixes, obtaining ix
G
GSKit 12
gsksa.rte fileset
12
C
client node information, recommendations for gathering
client work sheets for configuration information 14
concurrent access to FILE volumes 12
configuration information work sheets 14, 15
conventions
typographic xi
customer support
contact ix
E
education
see Tivoli technical training viii
enablelanfree option 20, 34
encryption
3592 generation 2 12
IBM LTO generation 4 12
encryption, 3592 generation 2 12
environments, LAN-free 6
external library support 10, 53
© Copyright IBM Corp. 2000, 2009
H
how to information:
determine LAN-free data movement 30, 41
set up environment variables 20, 34
I
IBM Software Support
submitting a problem xi
IBM Support Assistant viii
installation and configuration
external library environments (ACSLS-managed) 33
planning for 5
tape-library and file-device sharing environments 19
Internet, search for problem resolution viii
Internet, searching for problem resolution ix
D
data movement, SAN
prerequisites 12
tasks 19, 33
device configuration file 50
disk device
file-sharing software 19
server install 24
disk-storage sharing 9
drive encryption
3592 generation 2 12
IBM LTO generation 4 12
drive encryption, 3592 generation 2 12
dsm.opt file 20, 34
dsm.sys options file 20
DSMSTA SETSTORAGESERVER
communication information to the storage agent
examples of use 46
using when installing the storage agent 22, 35
dsmsta.opt 22, 35, 47
18
K
knowledge bases, searching
viii
L
45
LAN-free data movement
data backup scenario 3
description of 1
enabling, dsm.opt 20, 34
guidelines for determining 30, 41
LAN-free environments, types of 6
library client 6
library manager 6
limit the SAN drives 24, 37
M
multi-session no-query restore
4
N
network requirements
no-query restore 4
19, 33
63
O
storage agent (continued)
installing 22, 35
options file 47
overview 1
planning configurations 5
policy considerations 24, 37
SANergy Metadata Controller 9
starting 29
usage requirements 12
verify configuration 29
verify LAN-free configuration 41
support information vii
system requirements 12
obtaining device information 17
option, enablelanfree 20, 34
options file
client 20, 34
options
ADMINONCLIENTPORT 47
COMMTIMEOUT 48
DEVCONFIG 47
IDLETIMEOUT 48
MAXSESSIONS 48
MSGSTACKTRACE 48
RESOURCETIMEOUT 48
SANDISCOVERY 49
SERVERNAME 47
STAMAXPOOLEDSESSIONS 49
TCPADMINPORT 49
TCPPORT 47
THROUGHPUTDATATHRESHOLD 50
THROUGHPUTTIMETHRESHOLD 50
USELARGEBUFFERS 50
storage agent 22, 35, 47
overview of storage agent 1
T
tape device information, obtaining
Tivoli Storage Manager API
install 20, 34
upgrade 20, 34
Tivoli technical training viii
training, Tivoli technical viii
typographic conventions xi
17
P
V
path
disk devices 29
tape devices 28
planning for installation and configuration 5
policy for storage agent 24, 37
problem determination
describing problem for IBM Software Support x
determining business impact for IBM Software Support
submitting a problem to IBM Software xi
product requirements 12
publications
download v
order v
related software vii
search v
Tivoli Storage Manager v
z/OS vii
volumes, formatting for z/OS LAN-free data movement
Z
z/OS data manager server, formatting LAN-free volumes
z/OS data manager server, formatting volumes for 29
x
S
SAN data movement
prerequisites 12
tasks 19, 33
SAN-attached device sharing, Tivoli Storage Manager support
of 1
SCSI and 349X library sharing 6
server work sheets for configuration information 15
Software Support
contact ix
describing problem for IBM Software Support x
determining business impact for IBM Software Support x
starting the storage agent 43
stopping the storage agent 43
storage agent
automating startup 43
component configuration 12
configuring device access 27
description 1
device configuration file 50
FILE library 9
64
29
IBM Tivoli Storage Manager for SAN for Sun Solaris: Storage Agent User’s Guide
29
Program Number: 5608-E12, 5608-E01, 5608-E02, 5608-E07, 5608-E03
Printed in USA
SC23-9800-00
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising