HP Archive Backup System for OpenVMS Guide to Operations

HP Archive Backup System for OpenVMS Guide to Operations HP Archive Backup System for OpenVMS Guide to Operations

h71000.www7.hp.com
from h71000.www7.hp.com More from this publisher
06.11.2014 Views

System Backup to Tape for Oracle Databases 9.12 Support for Oracle RDB database RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.RESTOREBACKUPPIECE RMAN> Example 9–25 Volume Offsite Error in Trace File SBT-00000889 11/13/01 16:28:02 Fatal catalog access error SBT-00000889 11/13/01 16:28:02 Extended Status: Piece 6sd8vntq_1_1 cannot be restored because volume AHI164 is offsite 9.12Support for Oracle RDB database This section describes the System Backup to Tape (SBT) for Oracle RDB databases feature of Archive Backup System (ABS). ABS V4.3 will support Oracle Rdb RMAN Media Management API V2.0 for Oracle Rdb RMU commands. The System Backup to Tape feature of ABS can be used to backup and restore Oracle RDB Database. Oracle Media Management V2.0 API for Oracle RDB RMU is an enhancement provided in Oracle RDB RMU Release 7.1.2. The Oracle RDB Release 7.1.2 should be installed for the same. Rdb V7.1 SQL/Services is required to be installed for RMU parallel backup operations. This section does not cover all aspects of configuring ABS /MDMS. This section only covers what you need to do to use SBT in the ABS/MDMS domain. Before configuring and using SBT, you must configure the following MDMS objects: • Media • Location • Domain • Node • Jukebox • Tape drives • Pool • Tape volumes If you have been using ABS/MDMS you will already have your domain configured. If this is your first installation of ABS/MDMS, be sure to configure the above objects before proceeding with this section. For backing up to and restoring data using ABS SBT, RMU commands accept the /LIBRARIAN qualifier. To use the LIBRARIAN qualifier the logical RMU$LIBRARIAN_PATH should be defined. For a parallel RMU backup RMU$LIBRARIAN_PATH should be defined as a system logical so that the multiple processes created by a parallel backup can all translate the logical. $DEFINE/PROCESS RMU$LIBRARIAN_PATH librarian_shareable_image.exe $DEFINE/SYSTEM/EXEC RMU$LIBRARIAN_PATH librarian_shareable_image.exe For configuring SBT, we define the VMS logical RMU$LIBRARIAN_PATH to point to the 32 bit SBT shareable image (MDMS$SBTSHR_NMA32.EXE) which is copied to SYS$COM- MON:[SYSEXE] . MDMS should be restarted for the image to take affect. These logicals need to be defined before the RMU backup or restore command is executed. The image is provided with the ABS kit. $DEFINE/SYSTEM RMU$LIBRARIAN_PATH SYS$COMMON:[SYSEXE]MDMS$SBTSHR_NMA32.EXE 9-24 System Backup to Tape for Oracle Databases

System Backup to Tape for Oracle Databases 9.12 Support for Oracle RDB database Install the file as a shared known image. This associates a known image with the latest version of the image file $INSTALL REPLACE /OPEN/HEAD/SHARE SYS$COMMON:[SYSEXE]MDMS$SBTSHR_NMA32.EXE The default catalog and archive used by SBT for backup/restore are ORACLE_DB and ORACLE_DB_ARCHIVE. You should create one oracle_db type catalog and an archive. Use the following command to create a oracle_db type catalog: $ MDMS CREATE CATALOG ORACLE_DB /TYPE=ORACLE_DB Use the following command to create the default archive: $ MDMS CREATE ARCHIVE ORACLE_DB_ARCHIVE - /ARCHIVE_TYPE=TAPE - /CATALOG=(NAME=ORACLE_DB) - /MAXIMUM_SAVES=36 - /MEDIA_TYPE=DLT_III - /POOL=DB_BACKUP_POOL - /RETENTION_DAYS=35 9.12.1 RMU Commands that accept /LIBRARIAN Qualifier RMU/BACKUP command accepts the /LIBRARIAN qualifier to backup data using ABS SBT. $RMU/BACKUP/LIBRARIAN=(trace=disk:[directory]tracefile.trace)/LOG DATABASE FILENAME.RBF RMU/RESTORE command accept the /LIBRARIAN qualifier for retrieving data using ABS SBT. $RMU/RESTORE/LIBRARIAN=(trace=disk:[directory]tracefile.trace)/LOG FILE- NAME.RBF FILENAME.RBF is the backup filename. The backup filename excluding the extension must be the same name previously used for an RMU backup using SBT. The RMU command used with the /LIBRARIAN qualifier cannot specify a list of tape or disk devices. It accepts a backup file ("rbf file") name. Any disk or device specification or file extension specified with the backup file name is ignored for the backup file name specified to the archive. For example, "device:[directory]FILENAME.RBF" is specified as "FILENAME" when the backup file data is stored in or retrieved from the archive. SBT writes trace data to the tracefile, if specified. The archive application is a "black box" to RMU and the backup file name is the identifier of the stream of data stored in the archive. The MDMS utility used with the ARCHIVE BACKUP SYSTEM is used to associate devices with the stream of data sent to or retrieved from the archive by RMU. Since SBT is a black box to RMU that can store data to tape or disk, device specific qualifiers such as /REWIND, /DENSITY or /LABEL cannot be used with this interface. $RMU/BACKUP/LIBRARIAN=(WRITER_THREADS=2, trace=disk:[directory]tracefile.trace)/LOG DATABASE FILENAM.RBF Each writer thread for a backup operation or reader thread for a restore operation manages its own stream of data. Therefore, each thread uses a unique backup file name generated from the backup file name specified on the command line. A number is incremented and added to the end of each backup file name specified to the archive (except for the first) representing a unique data stream. This number is the equivalent of the volume number associated with non SBT RMU backups and restores. System Backup to Tape for Oracle Databases 9–25

<strong>System</strong> <strong>Backup</strong> <strong>to</strong> Tape <strong>for</strong> Oracle Databases<br />

9.12 Support <strong>for</strong> Oracle RDB database<br />

Install the file as a shared known image. This associates a known image with the latest version of<br />

the image file<br />

$INSTALL REPLACE /OPEN/HEAD/SHARE<br />

SYS$COMMON:[SYSEXE]MDMS$SBTSHR_NMA32.EXE<br />

The default catalog and archive used by SBT <strong>for</strong> backup/res<strong>to</strong>re are ORACLE_DB and<br />

ORACLE_DB_ARCHIVE. You should create one oracle_db type catalog and an archive.<br />

Use the following command <strong>to</strong> create a oracle_db type catalog:<br />

$ MDMS CREATE CATALOG ORACLE_DB /TYPE=ORACLE_DB<br />

Use the following command <strong>to</strong> create the default archive:<br />

$ MDMS CREATE ARCHIVE ORACLE_DB_ARCHIVE -<br />

/ARCHIVE_TYPE=TAPE -<br />

/CATALOG=(NAME=ORACLE_DB) -<br />

/MAXIMUM_SAVES=36 -<br />

/MEDIA_TYPE=DLT_III -<br />

/POOL=DB_BACKUP_POOL -<br />

/RETENTION_DAYS=35<br />

9.12.1 RMU Commands that accept /LIBRARIAN Qualifier<br />

RMU/BACKUP command accepts the /LIBRARIAN qualifier <strong>to</strong> backup data using ABS SBT.<br />

$RMU/BACKUP/LIBRARIAN=(trace=disk:[direc<strong>to</strong>ry]tracefile.trace)/LOG DATABASE<br />

FILENAME.RBF<br />

RMU/RESTORE command accept the /LIBRARIAN qualifier <strong>for</strong> retrieving data using ABS<br />

SBT.<br />

$RMU/RESTORE/LIBRARIAN=(trace=disk:[direc<strong>to</strong>ry]tracefile.trace)/LOG FILE-<br />

NAME.RBF<br />

FILENAME.RBF is the backup filename. The backup filename excluding the extension must be<br />

the same name previously used <strong>for</strong> an RMU backup using SBT.<br />

The RMU command used with the /LIBRARIAN qualifier cannot specify a list of tape or disk<br />

devices. It accepts a backup file ("rbf file") name. Any disk or device specification or file extension<br />

specified with the backup file name is ignored <strong>for</strong> the backup file name specified <strong>to</strong> the<br />

archive. For example, "device:[direc<strong>to</strong>ry]FILENAME.RBF" is specified as "FILENAME" when<br />

the backup file data is s<strong>to</strong>red in or retrieved from the archive. SBT writes trace data <strong>to</strong> the tracefile,<br />

if specified.<br />

The archive application is a "black box" <strong>to</strong> RMU and the backup file name is the identifier of the<br />

stream of data s<strong>to</strong>red in the archive. The MDMS utility used with the ARCHIVE BACKUP<br />

SYSTEM is used <strong>to</strong> associate devices with the stream of data sent <strong>to</strong> or retrieved from the<br />

archive by RMU. Since SBT is a black box <strong>to</strong> RMU that can s<strong>to</strong>re data <strong>to</strong> tape or disk, device<br />

specific qualifiers such as /REWIND, /DENSITY or /LABEL cannot be used with this interface.<br />

$RMU/BACKUP/LIBRARIAN=(WRITER_THREADS=2, trace=disk:[direc<strong>to</strong>ry]tracefile.trace)/LOG<br />

DATABASE FILENAM.RBF<br />

Each writer thread <strong>for</strong> a backup operation or reader thread <strong>for</strong> a res<strong>to</strong>re operation manages its<br />

own stream of data. There<strong>for</strong>e, each thread uses a unique backup file name generated from the<br />

backup file name specified on the command line. A number is incremented and added <strong>to</strong> the end<br />

of each backup file name specified <strong>to</strong> the archive (except <strong>for</strong> the first) representing a unique data<br />

stream. This number is the equivalent of the volume number associated with non SBT RMU<br />

backups and res<strong>to</strong>res.<br />

<strong>System</strong> <strong>Backup</strong> <strong>to</strong> Tape <strong>for</strong> Oracle Databases 9–25

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!