This section shows you how to use tape devices with your TSM system. After adding the tape devices to TSM, you can migrate data from disk storage pools to tape storage pools. 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 following scenario shows how to include two IBM 3490 tape devices into the TSM environment. You must assign a device class for the type of tape devices you have and associate that device class with a storage pool:
![]() |
define devclass tapeclass devtype=cartridge - format=3490e mountlimit=2 |
![]() |
|
![]() |
define stgpool tapepool tapeclass - maxscratch=100 collocate=no |
![]() |
|
All tape volumes must have standard tape labels before TSM can use them. You can use tapes as scratch volumes, up to the number of scratch volumes you specified for the storage pool. Using scratch volumes allows TSM to acquire volumes as needed.
You can also use private volumes in a storage pool. You must define any private volumes to TSM, assigning each to a specific storage pool. However, if a storage pool contains only private volumes and runs out of them, storage operations to that pool stop until more volumes are defined. Prepare tape volumes as follows:
![]() |
define volume tapepool dsm001 |
![]() |
|
Now that TSM can use your tape devices, you can update your disk storage
pools so that client data can be migrated to tape. This section
describes how to change BACKUPPOOL and ARCHIVEPOOL so that data migrates to
TAPEPOOL.
![]() |
update stgpool backuppool nextstgpool=tapepool update stgpool archivepool nextstgpool=tapepool |
![]() |
|
To verify that the tape media have been integrated into
your TSM system, migrate data from a disk storage pool. Migration from
a storage pool 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
To migrate from a disk storage pool to a tape storage pool, devices must be allocated and tapes must be mounted. For these reasons, you may want to ensure that migration occurs at a time that is best for your situation. You can control when migration occurs by leaving the high migration threshold set to 100 most of the time, and lowering 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. |