This diagram shows the onbar -v syntax.
Verifying Backups with archecker: |-- -v----------------------------------------------------------> >--+-----------+--+-------------------+--+-----------------+--+------------------+--| '- -t--time-' | (1) | | (1) | +- -f--filename----+ '- -q--session------' '- -L--level------' | .--------------. | | V | | +---dbspace_list-+-+ | (2) | '- -w--------------'
Element | Purpose | Key Considerations |
---|---|---|
-v | Verifies a backup
If verification is successful, you can restore the storage spaces safely. |
Specify onbar -v to verify
the backup. You can perform a point-in-time verification. You cannot verify
the logical logs. You must specify the -b or -v parameter
first.
You can verify a whole-system or physical-only backup (IDS). |
dbspace_list | Names a list of storage spaces to be backed up or verified | If you enter more than one storage-space name, use
a space to separate the names.
On XPS, if you enter a dbslice name, it verifies all the dbspaces in that dbslice. |
-f filename | Verifies the storage spaces that are listed in
the text file whose pathname filename provides
Use this option to avoid entering a long list of storage spaces every time that you verify them. |
You can use any valid UNIX or Windows pathname
and filename. For the format of this file, see Figure 10.
The file can list multiple storage spaces per line. |
-L level | Specifies the level of backup to verify (XPS):
|
The archecker utility fully
verifies level-0 backups on all database servers and performs limited verification
of level-1 and level-2 backups.
If you do not specify a level, archecker verifies the level-0 backup. |
-q session | Assigns a name to the verify session (XPS) | DBSERVERNAMErandom_number is
the default session name. The session name must be unique and can
be up to 126 characters.
This name appears in the onstat utility so that you can follow the progress of the verify session. |
-t time | Specifies the date and time to which dbspaces are verified | How you enter the time depends on your current GLS locale
convention. If the GL_DATETIME environment
variable is set, you must specify the date and time according to
that variable. If the GLS locale
is not set, use ANSI-style date format:
YYYY-MM-DD HH:MM:SS. |
-w | Verifies a whole-system backup | Available on IDS only. |