Tivoli Header

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.

Step 4. Client System

Note:
If you are configuring a FILE Library, skip this step and proceed to Step 5.

Perform the following:

Obtain Tape Device Information

Obtaining tape device information in a Sun environment is different depending on whether your environment supports IBM devices or non-IBM devices as follows:

IBM Tape Devices

After installing device drivers for your IBM tape drives, a set of special file name available for each device. To see the special file names, use the command

+--------------------------------------------------------------------------------+
|ls /dev/rmt/*st                                                                 |
+--------------------------------------------------------------------------------+

The name typically has the form:

+--------------------------------------------------------------------------------+
|/dev/rmt/xst                                                                    |
+--------------------------------------------------------------------------------+

where x is a number.

Non-IBM Tape Devices

To use the TSM device drivers, you must do the following:

  1. Verify that the device is connected to your system, and is powered on and active
  2. Ensure the TSM 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 you want the device driver to probe for supported tape drives.
  4. Configure the drives by entering 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 appear in the /dev/rmt directory. Their names have the form /dev/rmt/xmt, where x is a number. To determine the relationship between a physical device and the special file that was created for it, issue the following command:

    +--------------------------------------------------------------------------------+
    |> ls  /dev/rmt/*mt                                                              |
    +--------------------------------------------------------------------------------+

    The name typically has the form:

    +--------------------------------------------------------------------------------+
    |/dev/rmt/xmt                                                                    |
    +--------------------------------------------------------------------------------+

    where x is a number.

Step 5. Server

The following provides information to help you define paths from the storage agent to the drives that are available to the TSM server. Paths allow 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 defining paths to your SAN drives:

Tape Devices

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

Important: Be sure that the device names are what is seen by the storage agent on each client system.

Note:
The DEFINE PATH 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 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.

See the Administrator's Reference for your system platform for additional details on the DEFINE PATH command.

Depending on the operating system of the TSM server, there may not be a quick way to confirm which device names on the storage agent correspond to device names on the TSM server without using a trial and error method. To confirm device names, you should work with one online drive at a time, and cycle through the storage agent device names until a successful backup can be run.

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

Disk Devices

Define paths 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 path needs to be created for each file drive in the library. The following is the command issued to create the path for this scenario. In this example, file3 represents the destination file drive in the disk library with a name of disklib.

define path storagnt file3 srctype=server desttype=drive library=disklib device=file
 directory="/tsmdata/server1"

For command information, see the Administrator's Reference.

The following figure displays the results of completing steps three, four and five.

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

Device information


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