![]() |
![]() |
Before you can use tape and optical devices with Tivoli Storage Manager, 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 Tivoli Storage Manager see the Administrator's Guide for details.
The examples in this section set up the following configuration:
![]() | If Tivoli Storage Manager 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. |
![]() | Here are some concepts that can help you to set up your tape environment (see Administrator's Guide): |
|
To prevent disk storage pools from becoming filled with client data, you can specify that client data be automatically migrated to the tape storage pool. A disk's high migration threshold (default value: 90%) determines when data is migrated. The low migration threshold (default value: 70%) determines when migration stops. Thus data migration from the default backup disk storage pool begins when the pool is 90% full and continues until it is at 70% full or less. Another default is to cache data (leave the data on the storage pool) even
after the data has been migrated. Cached data stays on disk for quick
access until the space is needed for new data.
|
|
A scratch volume is a volume that is available for the server to
use. The volume is labeled, is either blank or contains no valid data,
and is not defined to Tivoli Storage Manager. You must specify the
number of scratch volumes that the server can request for this pool
(MAXSCRATCH parameter).
|
|
Collocation Collocation means that the server tries to keep a client's files on a
minimal number of tape volumes. It is turned off by default.
Once clients begin storing data in a storage pool with collocation off, you
cannot easily change the data in the storage pool so that it is
collocated. To understand the advantages and disadvantages of
collocation, see the Administrator's Guide.
|
For Tivoli Storage Manager 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.
Table 8 and Table 9 list the device drivers needed for Tivoli
Storage Manager drives and libraries.
Table 8. Device Drivers for Tape and Optical Drives
Device | Device Type | Library Type | Device Driver |
---|---|---|---|
4MM drive | 4MM | External, Manual, SCSI | Tivoli Storage Manager device driver |
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, ACSLS | |
Optical drive | OPTICAL | External, Manual, SCSI | |
WORM drive | WORM | External, Manual, SCSI | |
IBM 3570 drive | 3570 | External, Manual, SCSI | IBMtape |
IBM 3480, 3490, 3490E drive | CARTRIDGE | External, Manual, SCSI, ACSLS, 349X | |
IBM 3590, 3590E drive | 3590 | External, Manual, SCSI, ACSLS, 349X | |
IBM LTO 3580 drive | LTO | External, Manual, SCSI |
Table 9. Device Drivers for Automated Libraries
Device | Library Type | Device Driver |
---|---|---|
IBM MP 3570, 3575 Library | SCSI | IBMtape |
IBM LTO 3581, 3583, 3584 Library | SCSI | |
IBM 3494, 3495 Library | 349X | lmcpd |
Non-IBM SCSI libraries | SCSI | Tivoli Storage Manager device driver (tsmscsi) |
All other supported libraries and drives use the Tivoli Storage Manager device driver. See http://www.tivoli.com/support/storage_mgr/tivolimain.html for a list of supported libraries.
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.
For an IBM 349X, the device name is the symbolic name you entered in the configuration file for the library. During configuration of devices other than a 349X, one or more device special file names are created. Table 10 shows the form of the names. In the examples, x denotes a number (0-7).
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.
Description | Device Example | Logical File Name |
---|---|---|
Tape drives that are supported by the Tivoli Storage Manager device driver | /dev/rmt/xmt | xmt |
SCSI-attached libraries that are supported by the Tivoli Storage Manager device driver | /dev/rmt/xlb | xlb |
Optical drives that are supported by the Tivoli Storage Manager device driver | /dev/rmt/xop | xop |
IBM 3490, 3575, 3581, 3583, 3584, and 3590 tape drives, which are supported by the IBMtape device driver | /dev/rmt/xst | xst |
Medium changer of an IBM 3570 or an IBM 3590 B11 with Automatic Cartridge Facility (ACF) feature, which is supported by the IBMtape device driver | /dev/rmt/xsmc | xsmc |
Mount point to use on REMOVABLEFILE device type (CD-ROM) | /dev/cdx | cdx |
Filesystem to use on REMOVABLEFILE device type (zip drive) | /zip | Not applicable |
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:
Attention:
Keep the Worksheets: The information you record on the worksheets can help you when you need to perform operations such as adding volumes. Keep the worksheets for future reference.
Here is an overview of the procedure for attaching an automated library to the server system:
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.
For Tivoli Storage Manager to access a SCSI library, the device must be set for the appropriate mode. The mode that the server 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 the appropriate mode.
This section describes how to install the available device drivers.
For IBM 3490, 3570, 358X, and 3590 devices, see IBM SCSI Tape Drive, Medium Changer, and Library Device Drivers: Installation and User's Guide for instructions for installing 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 on the worksheet that applies to your device (see http://www.tivoli.com/support/storage_mgr/tivolimain.html).
The name for the drive typically has the form:
/dev/rmt/xst
where x is a number. The name may have additional characters (n, b, c) to indicate different operating characteristics. Enter the name that you select for the drive in the Device Name field for the drive. For example, to use the compression capability of the drive, enter:
/dev/rmt/1stc
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 349X 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, 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 Installing Device Drivers for IBM SCSI Tape Drives.
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.
Attention: Tivoli Storage Manager /mt device drivers do not support the Sun Solaris mt command.
To install the Tivoli Storage Manager device drivers for tape drives and libraries , do the following:
Add one stanza (as shown in the example at the top of the file) for each tape drive SCSI target ID, LUN combination that you want the device driver to probe for supported tape drives and for each autochanger device in the system that you want the server to use.
> /usr/sbin/add_drv -m '* 0666 bin bin' /usr/kernel/drv/mt
To add a library, enter the following command:
> /usr/sbin/add_drv -m '* 0666 bin bin' /usr/kernel/drv/lb
> 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 PATH 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 PATH command.
If you are configuring an optical library, you must set up the device drivers for both the drives in the library and the library itself.
To install the Tivoli Storage Manager device driver for optical drives and optical libraries, do the following:
Add one stanza (as shown in the example at the top of the file) for each optical drive and optical library in the system that you want the server to use.
/usr/sbin/add_drv -m '* 0666 bin bin' /usr/kernel/drv/op
To add a library, enter the following command:
> /usr/sbin/add_drv -m '* 0666 bin bin' /usr/kernel/drv/lb
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 PATH 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 PATH command.
In the following example, two stand-alone 8mm drives are added to Tivoli Storage Manager. Tivoli Storage Manager requires that all drives are associated with a library. For standalone drives, you must define a manual library. Unlike other library types, no path is defined for manual libraries. 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 PATH
DEFINE DEVCLASS
DEFINE STGPOOL
+--------------------------------------------------------------------------------+ |define library manuallib libtype=manual | |define drive manuallib drive01 | |define path server1 drive01 srctype=server desttype=drive | |library=manuallib device=/dev/rmt/1mt online=yes | |define drive manuallib drive02 | |define path server1 drive02 srctype=server desttype=drive | |library=manuallib device=/dev/rmt/2mt online=yes | | | +--------------------------------------------------------------------------------+
OR
+--------------------------------------------------------------------------------+ |define devclass tapeclass devtype=8mm format=8500 library=manuallib | +--------------------------------------------------------------------------------+
OR
+--------------------------------------------------------------------------------+ |define stgpool tapepool tapeclass maxscratch=20 | +--------------------------------------------------------------------------------+
OR
The following example shows how to add an Exabyte EXB-210 library containing two drives. 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 PATH
DEFINE DRIVE
DEFINE PATH
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 | |define path server1 autolib srctype=server desttype=library | |device=/dev/rmt/3lb online=yes | |define drive autolib drive05 element=82 | |define path server1 drive05 srctype=server desttype=drive | |library=autolib device=/dev/rmt/5mt online=yes | |define drive autolib drive06 element=83 | |define path server1 drive06 srctype=server desttype=drive | |library=autolib device=/dev/rmt/6mtt online=yes | +--------------------------------------------------------------------------------+
OR
![]() | Element address
The element address is a number that indicates the physical location of a drive within an automated library. Tivoli Storage Manager 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 path | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ | query devclass format=detailed | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ | query stgpool | +--------------------------------------------------------------------------------+
Tape Paths and the tape paths you have defined
Disk Paths and the disk paths you have defined
All tape volumes must be labeled before they can be used. If you want a volume to be used only when it is requested by name, you must also define it to Tivoli Storage Manager. A defined volume is a private volume and is assigned to a specific storage pool. A volume that is not defined 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 Tivoli Storage Manager, 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 the server 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. |