HP Archive Backup System for OpenVMS Guide to Operations

System Backup to Tape for Oracle Databases
9.12 Support for Oracle RDB database
to SBT to be used for diagnostic purposes. If the backup is a parallel operation a PLAN file is
created and executed as part of the existing RMU/BACKUP/PARALLEL and
RMU/BACKUP/PLAN command syntax. The following is an example of a parallel backup and
non parallel restore (the restore is always non parallel and executes in a single process) using the
/LIBRARIAN qualifier.
$RMU/BACKUP/PARALLEL=EXECUTOR=2/LIBRARIAN=WRITER_THREADS=1-
/LIST_PLAN=FILENAME.PLAN/NOEXECUTE/LOG DATABASE FILENAM.RBF
$RMU/BACKUP/PLAN FILENAME.PLAN
$RMU/RESTORE/LIBRARIAN=(READER_THREADS=2)/LOG FILENAME
In this example the first backup command creates the PLAN file for a parallel backup but does
not execute it. The second backup command executes the parallel backup using the PLAN file.
Note that 2 worker processes will be used and each process will use the 1 writer threads specified
with the /LIBRARIAN qualifier. Each writer thread in each process will write one stream of
backup data using SBT. Therefore 2 streams will be written to the LIBRARIAN archive. The
streams will be given the names
FILENAME
FILENAME02
To retrieve the same 2 data streams which represent the backed up Rdb database on the non parallel
restore a READER_THREADS=2 parameter can be specified with the /LIBRARIAN qualifier
to use 2 threads to execute the restore, or if a READER_THREADS value specified is less
than 2 (1 is the default), RMU will determine the number of data streams actually stored by querying
the SBT distribute the data streams among the requested reader threads. If a
READER_THREADS value is specified that is greater than "2" RMU will set it to "2" so that
the restore does not attempt to retrieve data streams which do not exist.
Since all data stream names representing the database are generated based on the backup file
name specified for the RMU backup command used with the /LIBRARIAN qualifier, the user
must use a different backup file name to store the next backup of the database using SBT.
The user can incorporate the date or some other unique identifier in the backup file name to
make it unique if he wants to avoid deleting a previous backup to SBT, which used the same
backup file name.
Note
Deleting the previous backup is not recommended, as entire backup will be lost.
9.12.2.1 PARAMETERS Passed for the PLAN file
WRITER_THREADS=#
Use # writer threads to write # backup data streams using SBT. The database storage areas will
be partitioned among the database streams. The streams will be named BACKUP_FILENAME,
BACKUP_FILENAME02, BACKUP_FILENAME03, up to BACKUP_FILENAME#.
BACKUP_FILENAME is the backup file name specified in the RMU command excluding any
specified VMS file extension. This parameter can only be specified for parallel and non parallel
database backups. The default is 1 writer thread.
READER_THREADS=#
Use # reader threads to read all the backup data streams from SBT created for the backup filename.
The streams will be named BACKUP_FILENAME, BACKUP_FILENAME02,
BACKUP_FILENAME03, etc. BACKUP_FILENAME is the backup file name specified in the
9-28 System Backup to Tape for Oracle Databases