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.
![]() |
Perform the following:
Obtaining tape device information in a Sun environment is different depending on whether your environment supports IBM(R) devices or non-IBM devices as follows:
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.
To use the TSM device drivers, you must do the following:
+--------------------------------------------------------------------------------+ |> /usr/sbin/add_drv -m '* 0666 bin bin' /usr/kernel/drv/mt | +--------------------------------------------------------------------------------+
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.
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:
When drive mappings are defined for each drive in a library, backup operations wait until the next drive is available for the transfer of data.
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.
For example, you would issue the following:
define drivemapping iris sangroup drivea device=/dev/rmt/3st define drivemapping iris sangroup driveb device=/dev/rmt/4mtwhere 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 commands.
For a review of the results of the steps that you have just completed, see Figure 6.
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.