In the following example, two 8mm drives are attached to the server system. The example takes you through the steps necessary to get TSM to use the devices for storing client data.
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.
|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.|
For a tape drive, the device name is a special file name with the form /dev/mtx, where x is the number assigned when the drive was set up with its device driver.
define library manual8mm libtype=manual
define drive manual8mm drive01 device=/dev/mt1
define drive manual8mm drive02 device=/dev/mt2
Both drives belong to the MANUAL8MM library. In this example, the drive known to the device driver by the special file name /dev/mt1 is given the TSM name DRIVE01. The device /dev/mt2 is given the TSM name DRIVE02. You might prefer to have the device driver name and the TSM name match.
See Defining Drives and http://www.tivoli.com/support/storage_mgr/tivolimain.html .
define devclass tape8mm_class devtype=8mm format=8500 library=manual8mm
See Defining and Updating Device Classes for Tape Devices.
See Requesting Information about Libraries, Requesting Information about Drives, and Requesting Information about a Device Class.
define stgpool tape8mm_pool tape8mm_class maxscratch=20
See Defining or Updating Primary Storage Pools.
You can do one of the following to update TSM policy:
The following steps assume that you are modifying the standard, IBM-supplied policy objects, named STANDARD, to allow clients to back up data directly to tape. However, if you want some clients to back up directly to tape and some to disk, keep the standard policy as is. For the clients that need to back up directly to tape, define new policy (policy domain, management class, copy groups) and assign these clients to the new policy domain. For details on the standard policy, see Using the Standard Policy. For how to define new policy, see Creating Your Own Policies.
You can choose to have clients back up directly to the new tape storage pool that you defined.
|Key choice:||If you back up directly to tape, the number of clients that can back up data
at the same time is equal to the number of drives available to the storage
pool (through the mount limit of the device class). If you have only
one drive, only one client at a time can back up data.
Performance of tape drives is often lower when backing up directly to tape than when backing up to disk and then migrating to tape. Backing up data directly to tape usually means more starting and stopping of the tape drive. Backing up to disk and then migrating to tape usually means the tape drive moves more continuously and improves performance.
update copygroup standard standard standard type=backup destination=tape8mm_pool
|Note:||You may want clients in the STANDARD policy domain to be able to choose whether to back up directly to disk or to tape. If so, instead of updating the copy group in the STANDARD management class, you can define a new management class and a new copy group in the STANDARD domain. See Defining and Updating a Backup Copy Group.|
activate policyset standard standard
See Activating a Policy Set.
You can have clients back up data to disk storage. Then let TSM migrate the data to the new tape storage pool when the amount of disk storage used reaches the migration threshold. For example, you can have data migrate from the default disk storage pool, BACKUPPOOL, to the new storage pool, TAPE8MM_POOL, by using the following command:
update stgpool backuppool nextstgpool=tape8mm_pool
If you have not changed the defaults for BACKUPPOOL, TSM will migrate data from this disk pool to the TAPE8MM_POOL when the disk pool is 90% full. See Migration for Disk Storage Pools.
If you updated the default STANDARD policy to use the new storage pool as a destination for backups from clients, the clients must be registered to that policy domain. To register a client named ASTRO to the STANDARD policy domain and assign the client the password CADET, enter this command:
register node astro cadet
You do not need to specify a policy domain because the STANDARD policy domain is the default.
You can change the domain to which a client is assigned by using the UPDATE NODE command.
For information on options when registering clients, see Registering Nodes with the Server.
Ensure that volumes are available to TSM in the library.
label libvolume manual8mm vol001
Keep enough labeled volumes on hand so that you do not run out during an operation such as client backup.