Tivoli Header
Managed System for SAN Storage Agent User's Guide
If you will be using a Tivoli storage agent with ACSLS-managed libraries,
you must have the ACSLS software and the third-party external library software
(such as, Gresham EDT-DistribuTAPE) installed and configured. See the
StorageTek ACSLS and the Gresham EDT documentation for installation
instructions. See Figure 4 for an example of a storage agent in an ACSLS-managed
library environment. Complete the following steps to configure your
storage agent external library environment:
The server system and the client systems must be attached to the SAN along
with appropriate storage devices. The server system and the client
systems must also be connected by means of a LAN.
The Managed System for SAN feature requires specific levels and models of
hardware and software. Ensure that your system configuration meets the
hardware and software requirements for the SAN setup. See the Web site,
http://www.tivoli.com/support/storage_mgr/san/overview.html,
for details.
For a pictorial representation of what you will accomplish during the next
two steps, see Figure 7.
The procedures in this section describe installation and
configuration of TSM client, API, storage agent, and Gresham EDT
software.
- Note:
- Gresham EDT or any other middleware that provides external library enablement
is allowed. For installation information, see the Gresham or other
middleware products documentation.
- 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 client 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.
- 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:
- Storage Agent Name: storagnt
- Storage Agent Password: fun4me
- Storage Agent 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:
- TSM Server Name: tsmsrver
- TSM Password: not4u
- TSM TCP/IP address: tsmsrver.tucson.ibm.com
- TSM TCP/IP port: 1502
- Tape library name: stk-lib
Notes:
- 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, but needs
to be started and set 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.
- Start this step only after the dsmsta command issued in the previous step
has completed successfully. Use the library information that you
collected in step 1 to add library definition information to the device
configuration file. For example:
Incorporate the following library definition information:
- Add the library named stk-lib
- Set the libtype to external
- Set lanfree to YES
- Set obeymountretention to YES
Using the editor of your choice, open device configuration file and add
the following entry to the bottom of the file:
+--------------------------------------------------------------------------------+
|DEFINE LIBRARY stk-lib libtype=external lanfree=yes obeymountretention=yes |
| |
+--------------------------------------------------------------------------------+
The resulting device configuration file would appear as:
+--------------------------------------------------------------------------------+
|SET STANAME storagnt |
|SET STAPASSWORD xxxxxxx |
|SET STAHLADDRESS agent.tucson.ibm.com |
|DEFINE SERVER tsmsrver serverpassword=xxxxxxxxxxx |
| HLADDRESS=tsmsrver.tucson.ibm.com LLADDRESS=1502 |
|DEFINE LIBRARY stk-lib libtype=external lanfree=yes obeymountretention=yes |
| |
+--------------------------------------------------------------------------------+
Save and close the file. For additional information about the
DEFINE LIBRARY command, see the Tivoli Storage Manager Administrator's
Reference.
- Define a path from the storage agent to the external manager.
Gresham EDT-DistribuTape is the external library manager interfacing with the
ACSLS library software. The EDT executable is located in its default
path c:\program files\GES\EDT\bin\elm.exe. For
example:
define path storagnt stk-lib srctype=server desttype=library
externalmanager=c:\program files\GES\EDT\bin\elm.exe
For additional information about the DEFINE PATH command, see the Tivoli
Storage Manager Administrator's Reference.
The following provides the steps that you need to perform on the TSM
server. If further explanation is required, see
Administrator's Guide. On the server, perform the
following:
- Install Gresham EDT or any other third-party software that provides
external library enablement. For installation information, see the
Gresham documentation.
- 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 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:
- Define a library type of EXTERNAL. For example:
define library stk-lib libtype=external lanfree=yes obeymountretention=yes
- Define a path from the server to the external manager.
Gresham EDT-DistribuTape is the external library manager interfacing with the
ACSLS library software, the EDT executable is located in its default path
c:\program files\GES\EDT\bin\elm.exe. For example:
define path tsmsrver stk-lib srctype=server desttype=library
externalmanager=c:\program files\GES\EDT\bin\elm.exe
In the previous example the path provided for the external manager is
dependent upon the operating system where the TSM server resides. For
example, an AIX TSM server external manager path is /usr/lpp/dtelm/bin/elm in
contrast to a TSM Sun server external manager path of /opt/OMIdtelm/bin/elm or
a TSM Windows server external manager path of c:\program
files\GES\EDT\bin\elm.exe. For additional information about the
DEFINE PATH command, see theAdministrator's
Reference.
- Define a path from the storage agent to the external manager.
The DEFINE PATH command must be issued from the TSM server. Gresham
EDT-DistribuTape is the external library manager interfacing with the ACSLS
library software. The EDT executable is located in its default path
/opt/OMIdtelm/bin/elm. For example:
define path storagnt stk-lib srctype=server desttype=library
externalmanager=/opt/OMIdtelm/bin/elm
For additional information about the DEFINE PATH command, see the Tivoli
Storage Manager Administrator's Reference.
- Define a device class with a device type of ECARTRIDGE
- Define the storage pool
- Modify policy for the client so the storage agent, acting on behalf
of the client, is associated with a storage pool that users the drives on the
SAN. The client must use a management class that has copy groups with a
destination storage pool.
The destination storage pool must be associated with the library.
The library must be the one that you have defined paths to its drives for the
client. For example, do the following:
- 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 external
library, you will need to create a new management class. Clients that
want to use the SAN attached library need to use an include statement to bind
their files to this new management class. See Backup-Archive
Installation and 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 additional command information,
see Administrator's Reference.
The following figure displays the results of completing the previous
two steps.
- Note:
- This figure does not include all the required options. Steps 2 and 3
provide more details.
Figure 7. Communications information. Results of Steps 2 and 3. The passwords are shown as "xxxxxxx" because they are encrypted in the file.

In step 4 you will enable and start the device driver in order to support
the tape device.
The TSM device driver is installed but not enabled or started on the client
system when the storage agent is installed. Do the following to enable
the device driver:
- Enable the device driver by entering the following command from a command
prompt:
tsmscsi /enable
- Note:
- If you have not added the storage agent path to the search path, you must
first change to the directory where the storage agent program resides.
By default, the path is c:\program
files\tivoli\tsm\storageagent.
You will receive a message similar to the following:
+--------------------------------------------------------------------------------+
|TSM Windows 2000 / Optical support is enabled on DATAOWNER. |
+--------------------------------------------------------------------------------+
Or
+--------------------------------------------------------------------------------+
|TSM Optical support is enabled on DATAOWNER. |
+--------------------------------------------------------------------------------+
- Note:
- The message says that optical support is enabled, however the Managed System
for SAN feature does not support the use of optical devices on the SAN.
- Start the device driver by rebooting the client system. The device
driver should automatically start at reboot.
During this step you will start the storage agent and verify the
LAN-free configuration.
Start the storage agent as follows:
- Reboot the client system.
- Open the TSM Console and click the storage agent icon.
- Click the Start icon.
To verify that you have configured your system correctly for LAN-free data
movement, perform the following procedure:
- Run a backup operation from the client. Verify that the backup is
LAN-free by using a TSM Administrative Command Line client to login to the TSM
server and storage agent to verify the proper sessions have been
established. When LAN-free data movement is occurring, a QUERY SESSION
on the storage agent should show bytes received (displayed as Bytes Recvd) for
the node increasing to the total amount of data being backed up. The
QUERY SESSION on the TSM server should show a very small amount of bytes
received (metadata) for the same node. If the node's session
exhibits this behavior, and you receive a message stating that the backup has
been successful, you have configured your system correctly.
- Ensure the following if you receive a message saying that the backup has
failed.
- Note:
- If you retry the backup operation after the first failure, the client
attempts to use the LAN connection for data movement. The client will
continue to use the LAN until the client is stopped and restarted.
- The TSM server is running. If the TSM server is not running, the
storage agent will not start.
- The client, storage agent, and server are communicating with each other as
expected.
- The device driver on the storage agent is running.
- The mount and message is displayed on the storage agent console.
Use the following guidelines to help determine whether the data movement is
using the LAN-free environment:
On this Operating System
| Do this:
|
Windows 2000
| Click Settings> Network and Dial-up Connections
> Local Area Connection Status.
|
Windows NT
| Go to an MS-DOS command line and enter:
netstat -e
|
- Note:
- The output from the netstat -e command matches the Bytes Sent and
Received output displayed on Windows 2000.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]