Before you can use tape and optical devices with TSM, you must do the following:
To perform these tasks you can use the administrative client command line or web interface.
This section describes the following tasks:
If you want to use a tape management system with TSM see the Administrator's Guide for details.
The examples in this section set up the following configuration:
![]() | If TSM will use a tape library controlled by the Storage Tek Automated Cartridge System Library Software, you must set the CSI_HOSTNAME in the /opt/tivoli/tsm/devices/bin/rc.acs_ssi file. Define the environment variable ACSLS_SERVER_HOSTNAME in the /etc/environment or /etc/profile. You do not need to reset the variable at the next product update. |
For TSM to use a device, you must physically attach the devices to the server and install the appropriate device driver on your system. The following sections discuss how this is done for drives in a manual library and for the drives and controller in automated libraries.
The drivers are started when you start Sun Solaris. The devices must be powered on for Sun Solaris recognize them.
To identify and work with removable media devices, TSM needs the device's
special file name. or devices other than the IBM 3494, the name is the
special file name. For a 3494, the device name is the symbolic name you
entered in the configuration file for the library. For devices other
than the 3494, one or more device special file names are created during
configuration. The following table shows the form of the names.
In this table, x denotes a number (0-7).
Special File Name. | Description |
---|---|
/dev/rmt/xmt | Used for tape drives that are supported by the TSM device driver |
/dev/rmt/xlb | Used for SCSI-attached libraries that are supported by the TSM device driver |
/dev/rmt/xop | Used for optical drives that are supported by the TSM device driver |
/dev/rmt/xst | Used for IBM 3490, 3570, and 3590 tape drives, which are supported by the IBMtape device driver |
/dev/rmt/xsmc | Used for the medium changer (the robotics) of an IBM 3570 or an IBM 3590 B11 with Automatic Cartridge Facility (ACF) feature, which are supported by the IBMtape device driver |
The special file is a symbolic link into the /devices tree of the file system. The symbolic link destination has the form:
+--------------------------------------------------------------------------------+ |/devices/.../mt@x,0:mt | +--------------------------------------------------------------------------------+
where x is the SCSI ID of the device. The following table contains examples of special file names.
Note: | This naming convention will be slightly different for Sun Solaris 2.6. |
Table 2. Examples of Device Special File Names
If the logical file name is: | The device special file name is: |
---|---|
3mt | /dev/rmt/3mt |
0lb | /dev/rmt/0lb |
1op | /dev/rmt/1op |
2st | Drive: /dev/rmt/2st
Medium changer: /dev/rmt.2smc (3570 or 3590 B11 with ACF) |
Ensure that your devices are physically attached to your system according to the manufacturer's instructions.
Here is an overview of the procedure for attaching a drive in a manual library to the server system:
Note: | Each device connected in a chain to a single SCSI bus must be set to a unique SCSI ID. If each device does not have a unique SCSI ID, you may have serious system problems. |
Attention:
Here is an overview of the procedure for attaching an automated library to the server system:
Note: | In some automated libraries, the drives and the autochanger share a single SCSI ID, but have different LUNs. For these libraries, only a single SCSI ID is required. Check the documentation for your device. |
Note: | Each device connected in a chain to a single SCSI bus must be set to a unique SCSI ID. If each device does not have a unique SCSI ID, you may have serious system problems. |
Attention:
The device name for each drive has the form /dev/rmt/xmt. The device name for the library controller has the form /dev/rmt/xlb. In both cases, x is the number assigned when the drive and library was set up with its device driver.
Keep the Worksheets: | The information you record on the worksheets can help you when you need to perform operations such as adding volumes to an autochanger. Keep them for future reference. |
For TSM to access a SCSI library, the device must be set for the appropriate mode. The mode that TSM requires is usually called random mode; however, terminology may vary from one device to another. Two examples follow:
Refer to the documentation for your device to determine how to set it to a mode appropriate for TSM.
This section describes how to install the available device drivers.
For IBM 3490, 3570, and 3590 devices, see IBM SCSI Device Drivers: Installation and User's Guide for how to install the device drivers.
After completing the procedure in the manual, a set of special file names are available for each device. To see the special file names, use the command
+--------------------------------------------------------------------------------+ |ls -la /dev/rmt | +--------------------------------------------------------------------------------+
The output shows that the special files are really symbolic links into the /devices tree of the file system.
+--------------------------------------------------------------------------------+ |/dev/rmt/xst | +--------------------------------------------------------------------------------+
where x is a number. The name may have additional characters (n, b, c) at the end to indicate different operating characteristics.
Enter the device name that you select in the Device Name field for the drive on the worksheet.
The name for the drive typically has the form:
+--------------------------------------------------------------------------------+ |/dev/rmt/xst | +--------------------------------------------------------------------------------+
where x is a number.
The name for the medium changer has the form:
+--------------------------------------------------------------------------------+ |/dev/rmt/xsmc | +--------------------------------------------------------------------------------+
where x is a number. The smc stands for SCSI medium changer. Enter this name in the Device Name field for the library's medium changer (robotics). For example:
+--------------------------------------------------------------------------------+ |/dev/rmt/0smc | +--------------------------------------------------------------------------------+
For an IBM 3494 Tape Library Dataserver, use the information in IBM SCSI Device Drivers: Installation and User's Guide to install the driver. The driver is the IBM Tape Library Driver for Sun Solaris, which consists of the lmcpd (a daemon) and other components.
To determine the name to use to define the library to TSM, 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 Installing Device Drivers for IBM 3490, 3570, and 3590 Tape Drives.
To use the TSM device drivers, you must do the following:
If you are configuring a tape library, you must set up the device drivers for both the drives in the library and the library itself (that is, the robotics).
To install the Tivoli Storage Manager device driver for tape drives, perform the following steps:
+--------------------------------------------------------------------------------+ |> /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 -l /dev/rmt/*mt | +--------------------------------------------------------------------------------+
The output shows that the special file is really a symbolic link into the /devices tree of the file system. The symbolic link destination has the form /devices/.../mt@x,0:mt, where x is the SCSI ID of the device. This information lets you know which of the /dev/rmt/xmt special file names to provide to the server when you issue a DEFINE DRIVE command.
To install the Tivoli Storage Manager device driver for tape libraries, perform the following steps:
+--------------------------------------------------------------------------------+ |> /usr/sbin/add_drv -m '* 0666 bin bin' /usr/kernel/drv/lb | +--------------------------------------------------------------------------------+
The device special files for libraries appear in the /dev/rmt directory. Their names have the form /dev/rmt/xlb, 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 -l /dev/rmt/*lb | +--------------------------------------------------------------------------------+
The output shows that the special file is really a symbolic link into the /devices tree of the file system. The symbolic link destination has the form /devices/.../lb@x,y:lb, where x is the SCSI ID of the device and where y is the LUN (logical unit number) of the device. This information lets you know which of the /dev/rmt/xlb special file names to provide to the server when you issue a DEFINE LIBRARY command.
To use the TSM device drivers, you must first edit configuration files that reside in the /usr/kernel/drv directory, and then issue the add_drv (add drive) command. The devices should already be connected to the system and powered on.
If you are configuring a tape library, you must set up the device drivers for both the drives in the library and the library itself (that is, the robotics) for TSM to use.
To install the Tivoli Storage Manager device driver for optical drives, perform the following steps:
+--------------------------------------------------------------------------------+ |/usr/sbin/add_drv -m '* 0666 bin bin' /usr/kernel/drv/op | +--------------------------------------------------------------------------------+
The device special files for the optical drives appear in the /dev/rmt directory. Their names have the form /dev/rmt/xop, 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 -l /dev/rmt/*op | +--------------------------------------------------------------------------------+
The output shows that the special file is really a symbolic link into the /devices tree of the file system. The symbolic link destination has the form /devices/.../op@x,0:op, where x is the SCSI ID of the device. This information lets you know which of the /dev/rmt/xop special file names to provide to the server when you issue a DEFINE DRIVE command.
To install the Tivoli Storage Manager device driver for a library, perform the following steps:
+--------------------------------------------------------------------------------+ |> /usr/sbin/add_drv -m '* 0666 bin bin' /usr/kernel/drv/lb | +--------------------------------------------------------------------------------+
The device special files for libraries appear in the /dev/rmt directory. Their names have the form /dev/rmt/xlb, 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 -l /dev/rmt/*lb | grep lb@ | +--------------------------------------------------------------------------------+
The output shows that the special file is really a symbolic link into the /devices tree of the file system. The symbolic link destination has the form /devices/.../lb@x,y:lb, where x is the SCSI ID of the device and where y is the LUN (logical unit number) of the device. This information lets you know which of the /dev/rmt/xlb special file names to provide to the server when you issue a DEFINE LIBRARY command.
In the following example, two stand-alone 8mm drives are added to Tivoli Storage Manager. Because an operator must mount tapes for these drives, you must define them as part of a manual library to TSM. You can use this example as a guide when configuring other manual tape and optical devices. This example presents the procedure with a minimum of customization. If you want to do more, see the references in the steps for more details.
The commands, in the order entered, for defining a manual tape library
are:
DEFINE LIBRARY
DEFINE DRIVE
DEFINE DEVCLASS
DEFINE STGPOOL
+--------------------------------------------------------------------------------+ |define library manuallib libtype=manual | |define drive manuallib drive01 device=/dev/rmt/1mt | |define drive manuallib drive02 device=/dev/rmt/2mt | +--------------------------------------------------------------------------------+
OR
+--------------------------------------------------------------------------------+ |define devclass tapeclass devtype=8mm - | | format=8500 library=manuallib | +--------------------------------------------------------------------------------+
OR
+--------------------------------------------------------------------------------+ |define stgpool tapepool tapeclass maxscratch=20 | +--------------------------------------------------------------------------------+
OR
For the following example, an Exabyte EXB-210 library containing two drives is added to TSM. You can use this example as a guide when configuring other automated tape devices. This example presents the procedure with a minimum of customization. If you want to do more, see the references in the steps.
The commands, in the order entered, for defining an automated tape library
are:
DEFINE LIBRARY
DEFINE DRIVE
DEFINE DEVCLASS
DEFINE STGPOOL
The library is an Exabyte EXB-210, named AUTOLIB, whose SCSI library mechanism is at SCSI ID 3. The two drives, named DRIVE05 and DRIVE06, are at SCSI IDs 5 and 6. The element addresses for the drives in an EXB-210 are 82 and 83.
+--------------------------------------------------------------------------------+ |define library autolib libtype=scsi device=/dev/rmt/3lb | |define drive autolib drive05 device=/dev/rmt/5mt element=82 | |define drive autolib drive06 device=/dev/rmt/6mt element=83 | +--------------------------------------------------------------------------------+
OR
![]() | Element address
The element address is a number that indicates the physical location of a drive within an automated library. TSM needs the element address to connect the physical location of the drive to the drive's SCSI address. When you define a drive, the element address is required if there is more than one drive in an automated library. |
+--------------------------------------------------------------------------------+ |define devclass autoclass devtype=8mm - | | format=8500 library=autolib | +--------------------------------------------------------------------------------+
OR
+--------------------------------------------------------------------------------+ |define stgpool autopool autoclass maxscratch=20 | +--------------------------------------------------------------------------------+
OR
Before continuing, you can view the results of your definitions. If necessary, you can update these definitions by using update commands.
+--------------------------------------------------------------------------------+ | query library | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ | query drive | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ | query devclass format=detailed | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ | query stgpool | +--------------------------------------------------------------------------------+
All tape volumes must be labeled before TSM can use them. If you want a volume to be used only when it is requested by name, you must also define it to TSM. A defined volume is a private volume and is assigned to a specific storage pool. A volume that is not defined to TSM is a scratch volume. A storage pool can request available scratch volumes up to the number specified for that storage pool.
If you are using only one tape drive, consider labeling several tapes at this time.
+--------------------------------------------------------------------------------+ | | |label libvolume manual dsm001 | +--------------------------------------------------------------------------------+
OR
+--------------------------------------------------------------------------------+ | | |define volume tapepool dsm001 | +--------------------------------------------------------------------------------+
OR
To label tapes with an automated library, remove any tapes that you do not want to use with TSM and load the tapes to be labeled.
+--------------------------------------------------------------------------------+ |label libvolume autolib search=yes labelsource=barcode | | checkin=scratch | +--------------------------------------------------------------------------------+
OR
+--------------------------------------------------------------------------------+ | | |define volume autopool dsm001 | +--------------------------------------------------------------------------------+
OR
You can now configure TSM so that client data can be migrated to tape. To migrate from BACKUPPOOL to AUTOPOOL and from ARCHIVEPOOL to TAPEPOOL do the following:
+--------------------------------------------------------------------------------+ |update stgpool backuppool nextstgpool=autopool | |update stgpool archivepool nextstgpool=tapepool | +--------------------------------------------------------------------------------+OR
To verify that the tape devices are properly set up, migrate data from a disk storage pool. Migration requires tape mounts. The mount messages are directed to the console message queue and to any administrative client that has been started with either the mount mode or console mode option.
Trigger migration from a disk storage pool (BACKUPPOOL, for example) by
setting the high and low migration thresholds to 0:
+--------------------------------------------------------------------------------+ |update stgpool backuppool highmig=0 lowmig=0 | +--------------------------------------------------------------------------------+
After migration occurs, reset the thresholds to their original settings:
+--------------------------------------------------------------------------------+ |update stgpool backuppool highmig=90 lowmig=70 | +--------------------------------------------------------------------------------+OR
To migrate data from a disk storage pool and, after migration occurs, to
reset the thresholds to their original settings, update the storage
pool:
![]() | Controlling when migration occurs
Because migration from a disk to a tape storage pool uses resources such as drives and operators, you may want to control when migration occurs. To do so, leave the high migration threshold set to 100 most of the time, and lower it when you want migration to occur. In the preceding step, you lowered both migration thresholds to 0 to verify that migration occurred. You may not want to empty the disk storage pool by setting the low migration threshold to 0 every time you want migration to occur. Normally, you may want to keep the low threshold at 40%, and vary the high threshold from as high as 90% to as low as 50%. See Administrator's Guide for details. |