BACKUP DB (Back up the database)
Use this command to back up a Tivoli Storage Manager
database to
sequential access volumes.
To determine how much additional storage space a backup
will require,
use the QUERY DB command. That command displays the
database pages, in
megabytes, that have changed since the last backup.
Privilege class
To issue this command, you must have system privilege or
unrestricted
storage privilege.
Syntax
>>-BAckup DB--DEVclass--=--device_class_name-------------------->
.-Type--=--Incremental-----.
>--+--------------------------+--------------------------------->
'-Type--=--+-Incremental-+-'
+-Full--------+
'-DBSnapshot--'
>--+-------------------------------------+---------------------->
| .-,-----------. |
| V |
|
'-VOLumenames--=--+---volume_name-+-+-'
'-FILE: file_name-'
.-Scratch--=--Yes-----. .-Wait--=--No------.
>--+---------------------+--+------------------+---------------><
'-Scratch--=--+-Yes-+-'
'-Wait--=--+-No--+-'
'-No--' '-Yes-'
Parameters
DEVclass (Required)
Specifies the name of the sequential access
device class to use for
the backup.
Note:
1. You
cannot use a device class with a device type of NAS or
CENTERA.
2. A
restore database operation will fail 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
INCREMENTAL. Possible values are:
Incremental
Specifies
that you want to run an incremental backup of the Tivoli
Storage
Manager database. The maximum number of incremental
backups you
can run between full backups is 32.
Full
Specifies
that you want to run a full backup of the Tivoli Storage
Manager
database.
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 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 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 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 named
TAPEVOL.DATA that contains these lines:
DB0001
DB0002
DB0003
You can then
specify the volumes for the command as follows:
VOLUMENAMES=FILE:TAPEVOL.DATA
Scratch
Specifies whether
scratch volumes can be used for the backup. This
parameter is
optional. The default is YES. Possible values are:
Yes
Specifies
that scratch volumes can be used.
If you
specify SCRATCH=YES and the VOLUMENAMES parameter, Tivoli
Storage
Manager will only use 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 will fail 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. Possible values are:
No
Specifies
that the server processes this command in the
background.
You can continue with other tasks while the command is
being
processed. Messages 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
may 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 continuing
with other
tasks. The server then displays the output messages to
the
administrative client when the command completes.
Note: You
cannot specify Wait=Yes from the server console.
Examples
Task
Run an incremental backup of the database using a scratch
volume. Assume
a device class of FILE for the backup.
Command backup db
devclass=file type=incremental
No comments:
Post a Comment