You can use existing device classes for database backups
or you can define new ones. You can also specify device classes for
incremental backups that are different from the device classes for
full backups. For example, you might want to write full backups to
tape and incremental backups to disk.
About this task
Reserve the device class that you want to use for backups
so that the server does not attempt to back up the database if a device
is not available. If a database backup shares a device class with
a lower priority operation, such as reclamation, and all the devices
are in use, the lower priority operation is automatically canceled.
The canceled operation frees a device for the database backup.
Restriction: Tivoli® Storage
Manager does not support database backup (loading and unloading) to
a Centera device.
Procedure
To specify the device class to be used for database backups,
issue the SET DBRECOVERY command. For
example, to specify a device class named DBBACK, issue the following
command:
set dbrecovery dbback
Tips: - When you issue the SET DBRECOVERY command,
you can also specify the number of number of concurrent data streams
to use for the backup. Use the NUMSTREAMS parameter.
- To change the device class, reissue the SET DBRECOVERY command.
- If you issue the BACKUP DB command with the TYPE=FULL parameter,
and the device class is not the one that is specified in the SET
DBRECOVERY command, a warning message is issued. However,
the backup operation continues and is not affected.
- Device class definitions are saved in the device configuration
files.