Use this command to back up a Tivoli® Storage
Manager database
to sequential access volumes.
Attention: To restore a database, the server must use information
from the volume history file and the device configuration file. You
must make and save copies of the volume history file and the device
configuration file. These files cannot be recreated.
To
determine how much extra storage space a backup requires, issue the QUERY
DB command.
Restriction: You cannot restore
a server database from a different
Tivoli Storage
Manager server when
both of the following conditions are true:
- The database backup is stored on virtual volumes
- The connection to the Tivoli Storage
Manager server is
protected by SSL (Secure Sockets Layer)
After the database backup is complete,
the
Tivoli Storage
Manager server
backs up information, depending on the options that are specified
in the server options file. The following information is backed up:
is
- Sequential volume history information to all files that the VOLUMEHISTORY option
specifies
- Information about device configuration to all files that the DEVCONFIG option
specifies
Privilege class
To issue this command, you
must have system privilege or unrestricted storage privilege.
Syntax
>>-BAckup DB--DEVclass--=--device_class_name-------------------->
.-Type--=--Full------------.
>--+--------------------------+--------------------------------->
'-Type--=--+-Incremental-+-'
+-Full--------+
'-DBSnapshot--'
>--+---------------------------------------+-------------------->
| .-,-----------. |
| V | |
'-VOLumenames--=--+---volume_name-+---+-'
'-FILE:-- file_name-'
.-NUMStreams--=--1------. .-Scratch--=--Yes-----.
>--+-----------------------+--+---------------------+----------->
'-NUMStreams--=--number-' '-Scratch--=--+-Yes-+-'
'-No--'
.-Wait--=--No------. .-DEDUPDEVice--=--No------.
>--+------------------+--+-------------------------+-----------><
'-Wait--=--+-No--+-' '-DEDUPDEVice--=--+-No--+-'
'-Yes-' '-Yes-'
Parameters
- DEVclass (Required)
- Specifies the name of the sequential access device class to use
for the backup. If you issue the BACKUP DB command,
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.
If the SET
DBRECOVERY command is not issued to set a device class,
the BACKUP DB command fails.
Restriction: - You cannot use a device class with a device type of NAS or CENTERA.
- A restore database operation fails if the source for the restore
is a FILE library. A FILE library is created if the FILE device class
specifies SHARED=YES.
If all drives for this device class are busy when the
backup runs, Tivoli Storage
Manager cancels
lower priority operations, such as reclamation, to make a drive available
for the backup.
- Type
- Specifies the type of backup to run. This parameter
is optional. The default is FULL. The following values are possible:
- Full
- Specifies that you want to run a full backup of the Tivoli Storage
Manager database.
- Incremental
- Specifies that you want to run an incremental backup of the Tivoli Storage
Manager database.
An incremental (or cumulative) backup image contains a copy of all
database data that is changed since the last successful full backup
operation.
- DBSnapshot
- Specifies that you want to run a full snapshot database backup.
The entire contents of a database are copied and a new snapshot database
backup is created without interrupting the existing full and incremental
backup series for the database.
- VOLumenames
Specifies the volumes that are used to back up the database.
This parameter is optional. However, if you specify SCRATCH=NO, you
must specify a list of volumes.
- volume_name
- Specifies the volumes that are used to back up the database. Specify
multiple volumes by separating the names with commas and no intervening
spaces.
- FILE:filename
- Specifies the name of a file that contains a list of volumes that
are used to back up the database. Each volume name must be on a separate
line. Blank lines and comment lines, which begin with an asterisk,
are ignored.
For example, to use volumes DB0001, DB0002, and DB0003,
create a file that contains these lines:
DB0001
DB0002
DB0003
Name the file appropriately. For example:
You can then specify the volumes for the command as follows:
VOLUMENAMES=FILE:TAPEVOL
VOLUMENAMES=FILE:TAPEVOL.DATA
- NUMStreams
- Specifies the number of parallel data movement streams to use
when you back up the database. The minimum value is 1, and the maximum
value is 4. Increasing the value causes a corresponding increase in
the number of database backup sessions to be used and the number of
drives to be used for the device class. If you specify a NUMSTREAMS value
in the BACKUP DB command, it overrides any value
that is set in the SET DBRECOVERY command. Otherwise,
the value that is set in the SET DBRECOVERY command
is used. The NUMSTREAMS value is used for all
types of database backups.
- If a value is specified that is greater than the number of drives
available for the device class, only the number of available drives
are used. The available drives are those defined to the device class
by the MOUNTLIMIT parameter or by the number of online drives for
the specified device class. The session is displayed in the QUERY
SESSION output.
- If you increase the number of streams, more volumes are used
from the corresponding device class for this operation. Using more
volumes might improve the speed of the database backups, but at the
cost of more volumes that are not fully used.
- Scratch
- Specifies whether scratch volumes can be used for the backup.
This parameter is optional. The default is YES. The following values
are possible:
- Yes
- Specifies that scratch volumes can be used.
If you specify
SCRATCH=YES and the VOLUMENAMES parameter, Tivoli Storage
Manager only uses
scratch volumes if space is unavailable on the specified volumes.
If
you do not include a list of volumes by using the VOLUMENAMES parameter,
you must either specify SCRATCH=YES or use the default.
- No
- Specifies that scratch volumes cannot be used.
If you specify
volumes by using the VOLUMENAMES parameter and SCRATCH=NO, the backup
fails if there is not enough space available to store the backup data
on the specified volumes.
- Wait
- Specifies whether to wait for the server to complete processing
this command in the foreground. The default is NO. The following values
are possible:
- No
- Specifies that the server processes this command in the background.
You can continue with other tasks while the command is being processed.
Messages
that are created from the background process are displayed either
in the activity log or the server console, depending on where messages
are logged.
To cancel a background process, use the CANCEL
PROCESS command. If a BACKUP DB background
process is canceled, some of the database might have already been
backed up before the cancellation.
- Yes
- Specifies that the server processes this command in the foreground.
Wait for the command to complete before you continue with other tasks.
The server then displays the output messages to the administrative
client when the command completes.
Restriction: You cannot
specify WAIT=YES from the server console.
- DEDUPDEVice
- Specifies that a target storage device supports data deduplication.
When set to YES, the format for backup images is optimized for data
deduplication devices, making backup operations more efficient. The
following values are possible:
- No
- Specifies that a target storage device does not support data deduplication.
NO is the default.
Ensure that this parameter is set to NO for
the following devices:
- SCSI libraries
- All devices that are defined with a FILE device class
- Virtual tape libraries (VTL) that do not support the data deduplication
function
- Yes
Specifies that a target device supports data deduplication
and that you want to optimize backups for this function. You can set
this parameter to YES if you are using VTLs that support data deduplication.
Example: Run an incremental backup by using a scratch
volume
Run an incremental backup of the database by using a
scratch volume. Use a device class of FILE for the backup.
backup db devclass=file type=incremental
Related commands
Table 1. Commands related to BACKUP DBCommand |
Description |
BACKUP DEVCONFIG |
Backs up Tivoli Storage Manager device information to a file. |
BACKUP VOLHISTORY |
Records volume history information in external
files. |
CANCEL PROCESS |
Cancels a background server process. |
DELETE VOLHISTORY |
Removes sequential volume history information
from the volume history file. |
EXPIRE INVENTORY |
Manually starts inventory expiration processing. |
MOVE DRMEDIA |
Moves DRM media on-site and off-site. |
PREPARE |
Creates a recovery plan file. |
QUERY DB |
Displays allocation information about the database. |
QUERY PROCESS |
Displays information about background processes. |
QUERY VOLHISTORY |
Displays sequential volume history information
that has been collected by the server. |
SET DBRECOVERY |
Specifies the device class to be used for automatic
backups. |
SET DRMDBBACKUPEXPIREDAYS |
Specifies criteria for database backup series
expiration. |