For the following example, two 3490E drives are attached to MVS and configured to the operating system. The example takes you through the steps necessary to get TSM to use the devices for storing client data.
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.
define devclass tap3490_class devtype=cartridge - format=3490c mountlimit=2
Key choice: | Mount limit (number of drives available in this device class) has a default value of 2. The mount limit should be equal to the number of drives of the same type that are available to TSM. |
define stgpool tap3490_pool tap3490_class maxscratch=20
Key choices:
Do one or both of the following to update TSM policy:
You can choose to have clients back up directly to the new tape storage pool that you defined.
Key choice: | If you back up to tape directly, 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 device class). If you have only one drive, only one client at a time can back up data. |
update copygroup standard standard standard standard - type=backup destination=tap3490_pool
Note: | Instead of updating the default copy group in the STANDARD policy domain, you could define a new management class and a new copy group. |
activate policyset standard
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, by using the following command:
update stgpool backuppool nextstgpool=tap3490_pool
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 to the STANDARD policy domain, enter this command:
register node astro cadet
For information on options when registering clients, see Registering Nodes with the Server.