Tivoli Header
Managed System for SAN Storage Agent User's Guide
For a pictorial representation of what you will accomplish during the next
two steps, see Figure 5
.
The sections in this step describe installation of TSM client, API,
and storage agent software.
- Check that the client system meets the prerequisites for client
software. See the User's Guide for the client. Install the
client software and API if it is not already installed on the system, or
upgrade the software to the latest level as necessary. The latest
levels can be downloaded from the Tivoli Storage Manager Web site at http://www.tivoli.com/support/storage_mgr/tivolimain.html.
- Modify the TSM options file (dsm.opt).
For information about the dsm.opt file, see Backup-Archive
Installation and User's Guide.
-
Activate the following options in the dsm.opt file. These
options specify that the client will use SAN-attached devices; when the
path is available, during backup, restore, archive, and retrieve
processing.
enablelanfree yes
LANFREECommmethod TCPIP
LANFREETCPPort 1500
or
LANFREECommmethod Namedpipes
LANFREEPort \\hostname\\pipename
-
If your are using a TDP client, configure the API by performing the following
procedure:
- Download the TSM Version 4.2 for the Windows backup-archive client
and the associated BAT file from http://www.tivoli.com/support/storage_mgr/tivolimain.html.
- Run the BAT file to unzip the files, and follow the directions to begin
the installation procedure.
- From the Setup Type window, click Custom.
- From the Select Components window, select Client
Files and click Change.
- Select API Client Runtime Files and deselect the other
components.
- Ensure that the installation directory you specify, is the same directory
where the existing API resides.
On the same system as the client, install the storage agent and perform the
following steps:
- Record the following information. This information is
required throughout the remainder of this procedure.
- Storage agent: Name and password for the storage
agent. Decide on a name and password that will be used to initialize
the storage agent and to define the storage agent as a server to the TSM
server. For example:
- Name: storagnt
- Password: fun4me
- TCP/IP address: agent.tucson.ibm.com
- TSM server: Information about the TSM server that the
storage agent will need in order to communicate with the server. This
is the same TSM server with which the client communicates. For
example:
- Name: tsmsrver
- Password: not4u
- TCP/IP address: tsmsrver.tucson.ibm.com
- TCP/IP port: 1502
Notes:
- You can verify the server information by issuing the QUERY STATUS command
from a TSM administrative command-line.
- The 'Server Password Set' displayed in the QUERY STATUS output
must be equal to YES and for this example the password is set to not4u.
To set the server password issue the SET SERVERPASSWORD command from a TSM
administrative command-line. For example:
set serverpassword not4u
- Insert the Managed System for SAN CD-ROM in the drive of the client
system. Follow instructions on the screen to install the storage
agent. The results of the installation are:
- The software is installed
- The options file for the storage agent (dsmsta.opt) is created in
the path c:\program files\tivoli\tsm\storageagent
- The TSM device driver is installed for use by the storage agent, enable
the device driver to start at boot (see Start the Device Driver for details)
- Ensure that the DEVCONFIG option is specified in the dsmsta.opt
file. For example, for a device configuration file named
devconfig.out located c:\program
files\tivoli\tsm\storageagent, edit the dsmsta.opt file and enter
the following line:
DEVCONFIG devconfig.out
- Use the information that you collected in step 1 to issue the DSMSTA SETSTORAGESERVER
command. For example:
dsmsta setstorageserver myname=storagnt mypassword=fun4me
myhladdress=agent.tucson.ibm.com
servername=TSMSRVER serverpassword=not4u
hladdress=tsmsrver.tucson.ibm.com lladdress=1502
See Set Installation Data for the Storage Agent: DSMSTA SETSTORAGESERVER for details about the command parameters.
The command generates the following lines in the device configuration file
for the storage agent:
+--------------------------------------------------------------------------------+
|SET STANAME storagnt |
|SET STAPASSWORD xxxxxxx |
|SET STAHLADDRESS agent.tucson.ibm.com |
|DEFINE SERVER tsmsrver serverpassword=xxxxxxxxxxx |
| HLADDRESS=tsmsrver.tucson.ibm.com LLADDRESS=1502 |
| |
+--------------------------------------------------------------------------------+
The passwords (shown here as xxxxxxxx) are encrypted in the
file.
The command also generates the following line in the dsmsta.opt
file:
+--------------------------------------------------------------------------------+
|SERVERNAME tsmsrver |
+--------------------------------------------------------------------------------+
See The Storage Agent Options File and The Device Configuration File for the Storage Agent for details on these files.
- Note:
- The TSM server console (Microsoft Management Console, MMC) provides a snapin
that contains a storage agent configuration wizard. This wizard
performs all of the manual steps listed here and allows you to skip to step
4. For additional information, see the TSM server console online
help.
The following provides the steps that you need to perform on the TSM
server. If further explanation is required, see
Administrator's Guide.
- For each client that you want to enable SAN data transfer, define
the client's storage agent to the TSM server as if the storage agent is a
server. You must use the same name and password that you set for the
storage agent when you installed it on the client system. The DEFINE
SERVER command must be issued from the TSM server (library manager or library
client) that will manage the client's data. For example:
define server storagnt serverpassword=fun4me
hladdress=agent.tucson.ibm.com lladdress=1500 validateprotocol=all
- Note:
- The VALIDATEPROTOCOL parameter in the previous example is optional.
This parameter determines whether a cyclic redundancy check should be
performed to validate data on all metadata transferred between the storage
agent and the TSM server. See the Administrator's
Reference for additional information about the DEFINE SERVER
command. See the Administrator's Guide for additional
information about data validation.
- Configure the SAN drives. This involves the following steps:
Tape Device
- Define a shared SCSI or 3494 library
- Define paths to the library using the DEFINE PATH command on the server
- Define drives that are associated with the library
- Define paths to the drives using the DEFINE PATH command on the server
- Define the device class
- Define the storage pool
Disk Device
Configure Enterprise Management and define a device class of DEVTYPE=FILE and
SHARED=YES. TSM automatically defines a new FILE library and also
defines drives corresponding to the mount limit for the FILE device
class. The FILE library name is the same as the device class
name. Each drive uses the library name with a numeric suffix. If
the mount limit is changed, the number of drives also changes.
- Note:
- As each session gets exclusive access to a file volume, the mount limit
should correspond to the number of expected concurrent backups.
- Modify policy for the client so the storage agent, acting on behalf
of the client, is associated with a storage pool that uses the drives on the
SAN. The client must use a management class that has copy groups with a
destination storage pool.
The destination storage pool must be associated with the library.
The library must be the one you have defined paths to the drives for the
client. For example, do the following:
- Create a policy domain for clients that will use the SAN devices for
direct data transfer.
- Create a policy set in that domain.
- In the default management class for that policy set, modify the copy
groups. Set the destination storage pool to the storage pool associated
with the SAN drives that you configured.
- Note:
- If you decide not to use the default management class for the SAN drives, you
will need to create a new management class. Clients that want to use
the SAN drives need to use an include statement to bind their files to this
new management class. See Backup-Archive Installation and
User's Guide for details on the include-exclude list.
- Activate the policy set.
- Register or update the client nodes so that they are in the new policy
domain.
See Administrator's Guide for details on changing policy for
clients that can use SAN drives. For details about the commands, see
Administrator's Reference.
The following figure displays the results of completing the previous
two steps.
- Note:
- This figure does not include all the required options. Steps 2 and 3
provide more details.
Figure 5. Communications information. Results of Steps 2 and 3. The passwords are shown as "xxxxxxx" because they are encrypted in the file.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]