![]() |
![]() |
Figure 6 shows the results of completing Step 4. Client System and Step 5. Server.
Perform the following:
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:
tsmscsi /enable
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. | +--------------------------------------------------------------------------------+
You need to obtain the device name information for the DEFINE PATH commands. This information is used to define paths between the SAN devices and the storage agent and 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: DATAOWNER | |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 DEFINE PATH commands for these devices on the server (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:
When paths are defined for each drive in a library, backup operations wait until the next drive is available for the transfer of data.
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.
For example, you would issue the following:
define path storagnt drive1 srctype=server desttype=drive library=sanlib1 device=mt3.0.1.0
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.
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.