Tivoli Storage Manager for Windows: 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 Figure 4 for an example of a Storage Agent in an ACSLS-managed
|library environment. See the StorageTek ACSLS and the Gresham EDT
|documentation for installation instructions.
|
|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.
|Figure 7 shows the results of completing Step 2. Client System and Step 3. Server.
- |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.
|Do the following on the client system:
|
- |Install or upgrade to the latest level of the client software and the TSM
|API software (version 4.2 or higher).
- |Install the storage agent software.
- |Install Gresham EDT or any other third-party software that provides
|external library enablement. For installation information, see the
|Gresham documentation.
|
|
- |Check that the client system meets the prerequisites for client
|software. See the applicable documentation. Install the client
|software if it is not already installed on the system, or upgrade the software
|to the latest level as necessary. You can ensure this by checking http://www.tivoli.com/support/storage_mgr/tivolimain.html.
|If there is a more recent package, you will want to download and
|install. See 3 for the install instructions.
- |Modify the TSM client options file (dsm.opt).
|For information about the dsm.opt file, see Tivoli Storage
|Manager Installing the Clients.
|
-
|
|
|
|
|Specify that you want the client to use SAN-attached devices during backup,
|restore, archive, and retrieve processing, if the path to the SAN devices is
|available. Activate the following option in the dsm.opt
|file:
|enablelanfree yes
|
|LANFREECommethod TCPIP
|LANFREETCPPORT 1501
and
|LANFREECommethod SharedMem
|LANFREESHMPORT 1511
|
- |
|
|
|Update the API software to the latest level by following the procedure
|described below or install the latest client.
- |Note:
- Ensure that the client is already installed.
|
|
- |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.
|
|
|
- |Note:
- It is recommended that the Storage Agent not be installed on the same machine
|as the Tivoli Storage Manager Server.
|
|
|On the same system as the client, install the storage agent.
|
- |Gather the following information:
|
- |Storage agent: Name and password for the storage
|agent. The name and password must be the same as the name and password
|that is used to define the storage agent as a server to the TSM server.
|For example:
|
- |Storage Agent Name: IRIS
- |Storage Agent Password: jonquil
- |Storage Agent TCP/IP address:
|arbor.tucson.tivoli.com
|
- |TSM server: Information about the TSM server with which
|the storage agent will communicate. This is the same TSM server with
|which the client communicates. For example:
|
- |TSM Server Name: GARDEN
- |TSM Password: botanical
- |TSM TCP/IP address: garden.tucson.tivoli.com
- |TSM TCP/IP port: 1500
- |Tape library name: stk-lib
|
|
- |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 a device configuration file exists and that the matching
|DEVCONFIG option is in the dsmsta.opt file. For example, for a
|device configuration file named dvcfgfil located
|c:\program files\tivoli\tsm\storageagent, edit the
|dsmsta.opt file and enter the following line:
|DEVCONFIG devcfgfil
- |Use the information that you collected in step 1 to issue the DSMSTA SETSTORAGESERVER command. For
|example:
|
|dsmsta setstorageserver myname=iris mypassword=jonquil
|myhladdress=arbor.tucson.tivoli.com
|servername=garden serverpassword=botanical
|hladdress=garden.tucson.tivoli.com lladdress=1500
|
|See Set Installation Data for the Storage Agent: DSMSTA SETSTORAGESERVER for the details on the command parameters.
|The command generates the following lines in the device configuration file
|for the storage agent:
|+--------------------------------------------------------------------------------+
||SET STANAME iris |
||SET STAPASSWORD xxxxxxx |
||SET STAHLADDRESS arbor.tucson.tivoli.com |
||DEFINE SERVER garden serverpassword=xxxxxxxxxxx |
|| HLADDRESS=garden.tucson.tivoli.com LLADDRESS=1500 |
|| |
|+--------------------------------------------------------------------------------+
|The passwords (shown here as xxxxxxxx) are encrypted in the
|file.
|The command also generates the following line in the dsmsta.opt
|file:
|+--------------------------------------------------------------------------------+
||SERVERNAME garden |
|+--------------------------------------------------------------------------------+
|
|
|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 and add library definition information to the device
|configuration file. For example:
|Using the editor of your choice open the device configuration file and add
|the library named stk-lib, set the libtype to external with lanfree and
|obeymountretention equalling yes. 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. With the open device configuration
|file add the following entry to the bottom of the file:
|+--------------------------------------------------------------------------------+
||DEFINE LIBRARY stk-lib libtype=external lanfree=yes obeymountretention=yes |
|| EXTERNALMANAGER="c:\program files\GES\EDT\bin\elm.exe" |
|| |
|+--------------------------------------------------------------------------------+
|The resulting device configuration file would appear as:
|+--------------------------------------------------------------------------------+
||SET STANAME iris |
||SET STAPASSWORD xxxxxxx |
||SET STAHLADDRESS arbor.tucson.tivoli.com |
||DEFINE SERVER garden serverpassword=xxxxxxxxxxx |
|| HLADDRESS=garden.tucson.tivoli.com LLADDRESS=1500 |
||DEFINE LIBRARY stk-lib libtype=external lanfree=yes obeymountretention=yes |
|| EXTERNALMANAGER="c:\program files\GES\EDT\bin\elm.exe" |
|| |
|+--------------------------------------------------------------------------------+
|Save and close the file. For additional information about the
|DEFINE LIBRARY command, see the Tivoli Storage Manager Administrator's
|Reference.
|
|The following is an overview of the steps that you need to do on the TSM
|server. For details, see Administrator's Guide.
|On the server, do the following:
|
- |Install Gresham EDT or any other third-party software that provides
|external library enablement. For installation information, see the
|Gresham documentation.
- |Configure the SAN drives. This involves the following steps:
|Tape Device
|
- |Define a library type of EXTERNAL. For example:
|define library stk-lib libtype=external lanfree=yes obeymountretention=yes
| 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 LIBRARY command, see the Tivoli Storage Manager Administrator's
|Reference.
- |Define a device class with a device type of ECARTRIDGE
- |Define the storage pool
|
- |For each client for which you want to enable SAN data transfer, define the
|client's storage agent as if it was 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 server (library manager or library client) that will manage the
|client's data. For example:
|define server iris serverpassword=jonquil
|hladdress=sanclient.tucson.tivoli.com lladdress=1500
- |Modify policy for the client so that the storage agent acting on behalf of
|the client 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 on the SAN for
|which you have mapped drives for the client. See
|Administrator's Guide for details on changing policy for
|clients that can use SAN drives. 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 and mapped for the client.
- |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 update the include-exclude list
|to specify the new management class. See Tivoli Storage Manager
|Installing the Clients 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 Reference for details on the
|commands.
|To review the expected results of the steps that you have just completed,
|see Figure 5.
|
|In step 4 you will enable and start the device driver in order to support
|the tape device. In contrast to other configurations documented in this
|publication External library support does not require TSM drive
|mapping. Instead the Gresham middleware product provides the drive
|mapping.
|
|
|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 SANCLIENT. |
|+--------------------------------------------------------------------------------+
|Or
|+--------------------------------------------------------------------------------+
||TSM Optical support is enabled on SANCLIENT. |
|+--------------------------------------------------------------------------------+
- |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.
|
|Do the following:
|
- |Start the Storage Agent
- |Verify the 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. If you receive a message
|saying 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 ]