![]() |
![]() |
To use a device, you must install the appropriate device driver. Tivoli Storage Manager provides its own device driver for non-IBM devices. The IBM device driver Atdd is supported for IBM devices. These device drivers are available on the ftp site ftp://ftp.software.ibm.com/storage/devdrvr/. Tivoli Storage Manager also supports third party vendor device drivers if the devices are associated with the GENERICTAPE device class and the hardware vendor also supports that device driver. Using a device class other than GENERICTAPE with a third party vendor device driver is not recommended.
Attention: Tracing and error reporting is better with the tsmscsi device driver or the HP-UX device driver (atdd) than with the standard HP-UX device driver. The tsmscsi device driver also makes available additional device classes that you can use instead of the GENERICTAPE device class. These new device classes let you specify format types for tapes, allow greater control of SCSI devices by the server, and enable new server functions.
Table 7 and Table 8 list the device drivers needed for Tivoli
Storage Manager drives and libraries.
Table 7. Device Drivers for Tape and Optical Drives
Device | Device Type | Library | Device Driver |
---|---|---|---|
4mm drive | 4MM | External, Manual, SCSI | Tivoli Storage Manager device driver (tsmscsi) |
8mm drive | 8MM | External, Manual, SCSI | |
DLT drive | DLT | External, Manual, SCSI | |
DTF drive | DTF | External, Manual, SCSI | |
QIC drive | QIC | External, Manual, SCSI | |
STK SD3, 9490, 9840, 9940 drive | ECARTRIDGE | External, Manual, SCSI | |
Optical drive | OPTICAL | External, Manual, SCSI | |
WORM drive | WORM | External, Manual, SCSI | |
IBM 3570 drive | 3570 | External, Manual, SCSI | atdd
The device driver must be at the following or later levels:
|
IBM 3590, 3590E drive | 3590 | External, Manual, SCSI, 349x | |
IBM LTO 3580 drive | LTO | External, Manual, SCSI |
Table 8. Device Drivers for Libraries
Device | Library Type | Device Driver |
---|---|---|
IBM MP 3570, 3575 Library | SCSI | atdd |
IBM LTO 3581, 3583, 3584 Library | SCSI | |
IBM 3494, 3495 Library | 349X | lmcpd |
Non-IBM SCSI libraries | SCSI | Tivoli Storage Manager device driver (tsmscsi) |
For certain devices and most autochangers, you must first install the tsmscsi device driver. See the Tivoli Storage Manager for HP-UX Quick Start for the procedure.
If you have migrated from a previous version of Tivoli Storage Manager, you must replace the standard HP-UX device driver (for example, stape) for libraries with the tsmscsi or the atdd device driver. However, for the tape drives in those libraries and for stand-alone tape drives, the tsmscsi device driver is not always required. You can continue to use the SCSI passthrough device driver and the GENERICTAPE device class.
Attention: Tracing and error reporting is better with the tsmscsi device driver than with the standard HP-UX device driver. In addition, the new device classes allow you to specify format types for tapes, allow greater control of SCSI devices by the server, and enable new server functions.
For drives that are currently claimed by the standard HP-UX device driver and associated with the GENERICTAPE device class, you can choose one of the following options:
query volume * stgpool=8mmpool query volume * stgpool=dltpool
update volume * wherestgpool=8mmpool access=readonly
update path server1 8mmdrv01 srctype=server desttype=drive library=8mmlib device=/dev/rmt/tsmmt1
The previous device special file names are no longer associated with the devices.
update devclass 8mmclass devtype=8mm format=8200
Attention: You can specify the DEVTYPE parameter on the UPDATE DEVCLASS only when changing a device class from GENERICTAPE and only one time. You cannot issue the command to revert to the previous device class. The only way you can revert to the previous device class is if you back up the database before performing the update and later restore the database to that point in time. All transactions that occur after the backup are lost.
update path server1 8mmdrv01 sourcetype=server desttype=drive library=8mmlib device=/dev/rmt/tsmmt11 update path server1 8mmlib srctype=server desttype=library device=/dev/rmt/tsmlb1
The previous device special file names are no longer associated with the devices.
define devclass 8mmclass2 library=8mmlib devtype=8mm format=8200 define stgpool 8mmpool2 8mmclass
update stgpool 8mmpool nextstgpool=8mmpool2 highmig=0 lowmig=0 reclaim=50 reclaimstgpool=8mmpool2
update devclass 8mmclass mountlimit=drives
Follow this procedure to claim the devices and create the device names of each device to be used by the tsmscsi device driver.
ioscan -fknHere is an example of the output:
Class I H/W Path Driver S/W State H/W Type Description ==================================================================================== autoch 3 8/12.8.0.0.0.0.1 spt CLAIMED DEVICE IBM 7337 tape 0 8/12.8.0.0.0.0.2 tape2 CLAIMED DEVICE QUANTUM LT7000
tsmddcfg 8/12.8.0.0.0.0.1 tsmddcfg 8/12.8.0.0.0.0.2The tsmscsi device driver recognizes the device type and assigns a special file name automatically during the configuration process. A message appears when the script has completed for each device, showing you the special file name assigned to the device:
Driver tsmtape is now assigned to device at 0/0/2/1.0.0 Special-file /dev/rmt/tsmmt0 created for use as DEVICE= value in TSM "Define" commands Special-file /dev/rmt/tsmtrc created to use with tsmscsi device driver tracing
If you do not see the message, you can enter the ioscan -fkn command again to see the new device special file name. Also, the files are stored in the /dev/rmt directory by the following names: tsmlbx, tsmmtx, tsmopx.
The format of the device special file name will be one of the following:
where x is a number.
To install the device drivers for IBM 3490, 3570, 358X, and 3590 devices, see
For an IBM 349X Tape Library Dataserver, refer to IBM SCSI Tape Drive, Medium Changer, and Library Device Drivers: Installation and User's Guide (GC35-0154) to install the driver. The driver is the IBM Tape Library Driver, which consists of the lmcpd (a daemon) and other components.
To determine the name to use to define the path for the library, check what you entered in the /etc/ibmatl.conf file for the library's symbolic name. Use this information to complete the Device Name field on your worksheet. For example, if the symbolic name for the library in the /etc/ibmatl.conf file is 3494a, enter that name on the worksheet in the Device Name field for the library.
The drives that are in the library are set up separately. See .
To work with removable media devices, Tivoli Storage Manager needs the device's special file name. You specify the device special file name when you issue the DEFINE PATH commands for drives and libraries.
To see these file names, you can use the ioscan command. For example, to see the device special files available for drives and autochangers, enter the command:
> ioscan -fkn
For tape devices supported by the standard HP-UX device drivers and IBM device drivers, after you configure the device drivers the operating system automatically assigns the special file names during system start-up. If the special file names do not appear in SAM or when you run ioscan, run the mksf command to make the special file names. See system documentation for details.
A single drive can have multiple special file names, depending on the format and recording density that the drive supports. Select the device name to use in defining the drive based on the format and density that you want Tivoli Storage Manager to use. For example, one device may have all of the following special file names:
The different names represent different recording formats, densities, and operating characteristics such as data compression. For example, you might choose the name /dev/rmt/c1t0d0BEST to have Tivoli Storage Manager use the best recording format and density available on the drive.
For details about special file names, see the documentation for the operating system.