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 AIX. The devices must be powered on for AIX recognize them.
To identify and work with removable media devices, TSM needs the device's special file name. When a device configures successfully, a logical file name is returned in the form of opx, mtx, or lbx, where x is a numerical value that indicates the instance of a device for a particular class.
During configuration, a device special file name is created as one of the
following. In this table, x denotes any integer of
0-9:
Special File Name | Description |
---|---|
/dev/mtx | Used by all tape drives that are not supported by IBM hardware device drivers |
/dev/lbx | Used by most TSM-supported SCSI libraries |
/dev/ropx | Used by all TSM-supported optical drives |
/dev/rmtx | Used by the GENERICTAPE device type |
/dev/smcx | Used by 3570 and 3575 libraries, and used to define the Automatic Cartridge Facility feature of the IBM 3590 B11 as a library |
/dev/lmcpx | Used by 349X automatic tape libraries |
The following are examples of special file names:
Table 3. Examples of Device Special File Names
If the logical file name is: | The device special file name is: |
---|---|
mt3 | /dev/mt3 |
lb0 | /dev/lb0 |
1op | /dev/r1op |
rmt1 | Drive: /dev/rmt1
Medium changer: /dev/rmt1.smc (3590 B11 ACF, 3570, and 3575) |
rmt2 | /dev/rmt2 |
lmcp0 | /dev/lmcp0 |
Note: | You must know the device special file name when you use the DEFINE DRIVE or DEFINE LIBRARY commands. The special file name is the value that you specify with the DEVICE= parameter. You can use the SMIT tool to get the device special file. |
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:
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/mtx. The device name for the library controller has the form /dev/lbx. 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. |
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, you receive a message from the system:
+--------------------------------------------------------------------------------+ |rmtx Available | +--------------------------------------------------------------------------------+
where x is a number. Note the value of x, which is assigned automatically by the system. Use this information to complete the Device Name field on the worksheet.
For example, if the message is rmt0 Available, the special file name for the device is /dev/rmt0. Enter /dev/rmt0 in the Device Name field for the drive on the worksheet. Always use the /dev/ prefix with the name provided by the system.
+--------------------------------------------------------------------------------+ |rmtx Available | +--------------------------------------------------------------------------------+
Note the value of x, which is assigned automatically by the system. The special file name for the drive is /dev/rmtx. The special file name for the media changer device (what TSM considers a library) is /dev/smcx (smc stands for SCSI media changer).
For example, if the message is rmt0, enter /dev/rmt0 in the Device Name field for the drive. Enter /dev/smc in the Device Name field on the worksheet for the library's robotics. Always use the /dev/ prefix with the name provided by the system.
Note: | For multidrive devices (for example, IBM 3570 Model B12 or B22, or IBM 3575), you need only one smcx. Although you will receive a .smc for each rmt device in the library, you need only one smc for the TSM library on the worksheet. |
For an IBM 3494 or 3495 Tape Library Dataserver, refer to either the IBM SCSI Tape Drive, Medium Changer, and Library Device Drivers or the IBM AIX Parallel and ESCON Channel Tape Attachment/6000 Installation and User's Guide.
After completing the procedure in the manual, you will receive a message (logical filename) of the form:
+--------------------------------------------------------------------------------+ |lmcpx Available | +--------------------------------------------------------------------------------+
where x is a number assigned automatically by the system. Use this information to complete the Device Name field on your worksheet.
For example, if the message is lmcp0 Available, enter /dev/lmcp0 on the worksheet in the Device Name field for the library. Always use the /dev/ prefix with the name provided by the system.
Note: | Use the procedure in this section to configure autochangers and robot device drivers excluding IBM 3494 and IBM 3495. |
The term Robot is defined as a device that performs programmed operations or that operates by remote control.
Run the SMIT program to configure the device driver for each autochanger or robot:
For example, a connection address of 40 has a SCSI ID=4 and a LUN=0. If you are using AIX Version 4.1, then a connection address of 4,1 has a SCSI ID=4 and LUN=1. You need a comma (,) between the SCSI ID and the LUN.
You will receive a message (logical filename) of the form lbX Available. Note the value of X, which is a number assigned automatically by the system. Use this information to complete the Device Name field on your worksheet.
For example, if the message is lb0 Available, the Device Name field is /dev/lb0 on the worksheet. Always use the /dev/ prefix with the name provided by SMIT.
Tape drives cannot be shared when TSM is started. They can only be shared when the drive is not defined to TSM, or TSM is not started.
Note: | The mksysb command does not work if both TSM and AIX are sharing the same drive or drives. |
To use the operating system's native tape device driver in conjunction with a SCSI drive, the device must be configured to AIX first and then configured to TSM. These steps cannot be done in reverse order. Configure the device to AIX through the following choices from SMIT:
+--------------------------------------------------------------------------------+ | Select Devices | | Select Tape Drive | | Select Add A Tape Drive | +--------------------------------------------------------------------------------+
To define the devices to TSM, go to Configuring a Device Driver for a Tape or an Optical Drive.
Notes:
Run the SMIT program to configure the device driver for each drive (including drives in libraries) as follows:
For example, a connection address of 40 has a SCSI ID=4 and LUN=0. If you are using AIX Version 4.1, then a connection address of 4,1 has a SCSI ID=4 and LUN=1. You need a comma (,) between the SCSI ID and the LUN.
The message you receive next depends on whether you are configuring the device driver for a tape or an optical device:
For example, if the message is mt0 Available, the Device Name field is /dev/mt0 on the worksheet. Always use the /dev/ prefix with the name provided by SMIT.
For example, if the message is op0 Available, the Device Name field is /dev/rop0 on the worksheet. Always use the /dev/r prefix with the name provided by SMIT.
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 drive1 device=/dev/mt1 define drive manuallib drive2 device=/dev/mt2 |
![]() |
|
![]() |
define devclass tapeclass devtype=8mm - format=8500 library=manuallib |
![]() |
|
![]() |
define stgpool tapepool tapeclass maxscratch=20 |
![]() |
|
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 DRIVE5 and DRIVE6, 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/lb3 define drive autolib drive5 device=/dev/mt5 element=82 define drive autolib drive6 device=/dev/mt6 element=83 |
![]() |
|
![]() | 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 |
![]() |
|
![]() |
define stgpool autopool autoclass maxscratch=20 |
![]() |
|
Before continuing, you can view the results of your definitions. If
necessary, you can update these definitions by using update commands.
![]() |
|
![]() |
|
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 |
![]() |
|
![]() |
define volume tapepool dsm001 |
![]() |
|
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 |
![]() |
|
![]() |
define volume autopool dsm001 |
![]() |
|
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 |
![]() |
|
To verify that the tape devices is 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 |
![]() | 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. |