Tivoli Storage Manager for Windows: Managed System for SAN Storage Agent User's Guide


Configuring Devices for the Storage Agent to Access

Figure 6

shows the results of completing Step 4. Client System and Step 5. Server.

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



Device information

Step 4. Client System

Note:
|If you are configuring a FILE Library, go to Step 5. |

Perform the following:

  1. Start the Device Driver.
  2. Obtain Tape Device Information. You will need this information for the drives in order to complete the task in Step 5. Server.

Start the Device Driver

Note:
|For IBM LTO Ultrium tape devices install and start the |most current IBM LTO Ultrium device drivers. ADSMSCSI is not required |for LTO devices, skip the following and go to Obtain Tape Device Information. |

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:

  1. 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.
  2. Start the device driver by rebooting the client system. The device driver should automatically start at reboot.

Obtain Tape Device Information

You need to obtain the device name information for the drive mapping commands. This information allows the storage agent to use the SAN devices through the drive mapping on the TSM server. Enter the following command at an MS-DOS command prompt (The TSM device driver, ADSMSCSI, must be running when you issue the command.):

tsmdlst

Results appear in the following format:

+--------------------------------------------------------------------------------+
|Computer Name:      SANCLIENT                                                   |
|TSM Device Driver:  Running                                                     |
|                                                                                |
|TSM Device Name  ID   LUN  Bus  Port   TSM Device Type  Device Identifier       |
|--------------------------------------------------------------------------------|
|mt8.2.0.1        8    0    0    1      3570             IBM     03570B12        |
|lb8.3.0.1        8    1    0    1      LIBRARY          IBM     03570B12        |
|mt8.4.0.1        9    0    0    1      3570             IBM     03570B12        |
|f:\              0    0    0    0      REMOVABLEFILE     n/a                    |
+--------------------------------------------------------------------------------+

You will need the information in the column labeled TSM Device Name to issue the drive mapping commands for these devices on the server (Step 5. Server).

Step 5. Server

The following provides information to help you define drive mappings on the TSM server. Drive mapping allows a client, by means of a storage agent, access to drives in a library. The requirements are different depending on the device you are using.

Consider the following guidelines before you begin mapping your SAN drives:

Tape Devices

Map the drives on the server using the device names as seen by the storage agent on each client system. See Obtain Tape Device Information.

Note:
The DEFINE DRIVEMAPPING command must be issued from the server (library manager or library client) that will manage the client's data.

For example, you would issue the following:

define drivemapping iris sangroup drivea device=mt8.2.0.1
define drivemapping iris sangroup driveb device=mt8.4.0.1

See the Administrator's Reference for your system platform for additional details on the commands.

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

Disk Devices

Map the drives on the server using the device names as seen by the storage agent on each client system. For example, on the server side, the directory, d:\tsmdata\server1, is exported on the NFS server running on the TSM Server machine. On the storage agent, the directory is NFS mounted as /tsmdata/server1. Because the two directory names do not match, a drive mapping needs to be created for each file drive in the library. Below is the command to issue to create the mapping for this scenario.

define drivemapping sa1 file1 file11 device=file online=yes dir="/tsmdata/server1"

See the Administrator's Reference for your system platform and additional details on the commands.


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