06.11.2014 Views

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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

9.5 Testing the Configuration of SBT<br />

sbtremove2(remove_after) successful, remove "testfile"<br />

sbtend successful<br />

*** The SBT API test was successful ***<br />

The following describes the commands in the above example:<br />

1. Define the sbttest symbol. By default the sbttest command is pointing <strong>to</strong> Oracle's<br />

ORA_RDBMS:SBTTEST.EXE. However, this executable will not work with SBT.<br />

2. Define the MDMS$SBT_ARCHIVE logical. This logical points <strong>to</strong> the archive that you created<br />

in Section 9.4.2. In this case, we would not have <strong>to</strong> define this logical because it is the<br />

default. If you did not create an ORACLE_DB_ARCHIVE archive, you would have specified<br />

the archive here.<br />

3. Define the MDMS$SBT_CATALOG logical. This logical points <strong>to</strong> the catalog that you created<br />

in Section 9.4.1. In this case, we would not have <strong>to</strong> define this logical because it is the<br />

default. If you did not create the default catalog, ORACLE_DB, you would have <strong>to</strong> specify<br />

it here.<br />

4. Run sbttest using the sbttest command. The parameter TESTFILE is a made up name that<br />

gets put in the catalog during the backup and then is used <strong>for</strong> the res<strong>to</strong>re. The data s<strong>to</strong>red and<br />

retrieved is 100 blocks of 16384 characters per block. By specifying the -TRACE flag the<br />

file SBTTEST.TRC is written (see the following text).<br />

5. Vendor description string shows that you are using the<br />

SYS$SHARE:MDMS$SBTSHR_MA64.EXE shareable image.<br />

The -TRACE flag generates the SBTTEST.TRC trace file. The trace file should look like the following<br />

example:<br />

SBT-00001DB2 12/14/01 10:12:30 Using archive ORACLE_DB_ARCHIVE<br />

SBT-00001DB2 12/14/01 10:12:31 Starting backup of testfile <strong>for</strong> DB: sbtdb<br />

SBT-00001DB2 12/14/01 10:12:31 Using catalog ORACLE_DB<br />

SBT-00001DB2 12/14/01 10:12:31 Attempting <strong>to</strong> allocate volume set BEB026<br />

SBT-00001DB2 12/14/01 10:12:33 Allocated drive: TLZ88D Device: MOE$MKC200:<br />

SBT-00001DB2 12/14/01 10:12:33 Drive is in jukebox TLZ88J<br />

SBT-00001DB2 12/14/01 10:12:37 Loading/mounting volume BEB026 on drive TLZ88D<br />

SBT-00001DB2 12/14/01 10:12:37 Loading volume BEB026 on drive TLZ88D<br />

SBT-00001DB2 12/14/01 10:12:45 Mounting volume BEB026 on device MOE$MKC200:<br />

SBT-00001DB2 12/14/01 10:12:53 Skipping 9 tapemarks <strong>to</strong> end of tape<br />

SBT-00001DB2 12/14/01 10:13:02 Ready <strong>to</strong> write <strong>to</strong> saveset 2001121410125267.<br />

on volume BEB026<br />

SBT-00001DB2 12/14/01 10:13:07 Using catalog ORACLE_DB<br />

SBT-00001DB2 12/14/01 10:13:07 Finished writing saveset 2001121410125267.<br />

on volume BEB026<br />

SBT-00001DB2 12/14/01 10:13:09 Starting res<strong>to</strong>re of testfile<br />

SBT-00001DB2 12/14/01 10:13:09 Using catalog ORACLE_DB<br />

SBT-00001DB2 12/14/01 10:13:10 Dismounting volume set member: BEB026 RVN 1<br />

SBT-00001DB2 12/14/01 10:13:10 Deallocating drive TLZ88D<br />

SBT-00001DB2 12/14/01 10:13:11 Allocated drive: TLZ88D Device: MOE$MKC200:<br />

SBT-00001DB2 12/14/01 10:13:11 Drive is in jukebox TLZ88J<br />

SBT-00001DB2 12/14/01 10:13:20 Loading/mounting volume BEB026 on drive TLZ88D<br />

SBT-00001DB2 12/14/01 10:13:20 Loading volume BEB026 on drive TLZ88D<br />

SBT-00001DB2 12/14/01 10:13:29 Mounting volume BEB026 on device _RDEVA0:<br />

SBT-00001DB2 12/14/01 10:13:37 Skipping 9 tapemarks <strong>to</strong> beginning of saveset<br />

SBT-00001DB2 12/14/01 10:13:44 Ready <strong>to</strong> read from saveset 2001121410125267.<br />

on volume BEB026<br />

SBT-00001DB2 12/14/01 10:13:47 Finished res<strong>to</strong>ring saveset 2001121410125267.<br />

from volume BEB026<br />

SBT-00001DB2 12/14/01 10:13:49 Dismounting volume set member: BEB026 RVN 1<br />

SBT-00001DB2 12/14/01 10:13:49 Deallocating drive TLZ88D<br />

You are now ready <strong>to</strong> start using Oracle's Recovery Manager <strong>to</strong> backup your Oracle database <strong>to</strong><br />

tape. The following section describes what Oracle's Recovery Manager commands allow you <strong>to</strong><br />

control how you do backups using SBT.<br />

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

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

Saved successfully!

Ooh no, something went wrong!