Before you can use tape 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:
After you have physically attached a devices to the server, you must configure the appropriate device driver (add it to the kernel). The following sections discuss how this is done for drives in a manual library and for the drives and controller in an automated library.
For procedures to configure device drivers, see the documentation for the operating system.
The drivers are started when you start HP-UX. The devices must be powered on for HP-UX recognize them.
To identify and work with removable media devices, TSM needs each device's name, the special file name.
For tape drives supported by the standard HP-UX device drivers, after you configure the device drivers, the operating system automatically assigns the special file names during system start-up. 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 to TSM based on the format and density that you want TSM 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 use the best recording format and density available on the drive.
To see these file names, you can use the HP-UX System Administration Manager (SAM), or use the ioscan command. For example, to see the device special files available for tape drives, enter the command:
+--------------------------------------------------------------------------------+ |> /usr/sbin/ioscan -fn -C tape | +--------------------------------------------------------------------------------+
Also useful is the lssf command to get more information about a specific device special file name. See the documentation for the operating system.
For an automated tape library, the special file names for the drives in the library are created and used as described above. For the library itself, you create the special file name when you set up the SCSI pass-through driver. For example, you might create the special file /dev/tsm/library for the library. Use this special file name as the device name when defining the library to TSM.
For details about special file names, see the documentation for the operating system.
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: | Each tape autochanger that you attach for TSM use must be on its own SCSI adapter card. |
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:
Record the special file names for the library and its drives on the device worksheet. The names are needed to define the library and drives to TSM.
You created the special file names for the library and drives when you configured the SCSI pass-through driver for them. If you do not remember the names, you can use SAM or the ioscan command. See Determining Device Names for Tivoli Storage Manager.
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 more information about SCSI pass-through drivers, see scsi_pt, scsi_ctl, and autochanger in the HP-UX documentation.
For the autochanger, use the following device file names:
+--------------------------------------------------------------------------------+ |/dev/rmt/xxxx : tape drive 1 | |/dev/rmt/xxxx : tape drive 2 (if the autochanger has | | multiple tape drives) | |/dev/xxxx/xxxx : library device name | | (put the file in the /dev directory) | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ |diskinfo /dev/rmt/xxxx | +--------------------------------------------------------------------------------+
If the tape drive is not supported, you will receive an I/O error message. If the tape drive is supported, you will receive the following information about the tape drive:
+--------------------------------------------------------------------------------+ |SCSI description of /dev/rmt/xxxxx: | | vendor: HP | | product id: HPxxxxxxx | | type: sequential access | | size: 0 Kbytes | |bytes per sector: 0 | +--------------------------------------------------------------------------------+
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.
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 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/1m define drive manuallib drive02 device=/dev/rmt/2m |
![]() |
|
![]() |
define devclass tapeclass devtype=generictape - 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 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/tsm/library define drive autolib drive05 device=/dev/rmt/5m element=82 define drive autolib drive06 device=/dev/rmt/6m 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=generictape - 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. |