Tivoli Header
Administrator's Guide
For the following example, two 3490E drives are attached to OS/390 and z/OS
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.
- Classify drives according to type and format by defining TSM device
classes. For example, if you want to use the 3490C recording format,
use the following command:
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.
- Check the server option DELETIONEXIT if necessary. For information
on the deletion exit, see Setting Up Tape Installation-Wide Exits. For information on server options, see
Administrator's Reference.
- Set up the storage pool to use the devices in the device class you just
defined. For example:
define stgpool tap3490_pool tap3490_class maxscratch=20
Key choices:
- If you specify zero (0) for the maximum number of scratch volumes, you
must explicitly define each volume to be used in the storage pool. If
you allow scratch volumes by specifying a number greater than zero, TSM can
choose from the scratch volumes available, without action on your part.
- Collocation is turned off by default. Collocation is a process by
which the server attempts to keep all files belonging to a client node or a
client file space on a minimal number of volumes. Once clients begin
storing data in a storage pool with collocation off, you cannot easily change
the data in the storage pool so that it is collocated. To understand
the advantages and disadvantages of collocation, see Keeping a Client's Files Together: Collocation and How Collocation Affects Reclamation.
See Defining or Updating Primary Storage Pools.
Do one or both of the following to update TSM policy:
- Have clients back up data directly to tape.
- Have clients back up data to disk storage. Then let TSM migrate the
data to tape when the amount of disk storage used reaches the migration
threshold.
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 the default copy group so that the destination for backups is the
new tape storage pool. For example:
update copygroup standard standard standard standard -
type=backup destination=tap3490_pool
See Defining and Updating a Backup Copy Group.
- 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 this modified policy:
activate policyset standard
See Activating a Policy Set.
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.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]