HP Archive Backup System for OpenVMS Guide to Operations

System Backup to Tape for Oracle Databases
9.5 Testing the Configuration of SBT
7. Maximum Saves: this attribute specifies how many backups can use the volume sets in this
archive at a time. This works great for ABS saves, however, there is a difference when used
with SBT. We suggest that you set it at 36 which is the maximum. You should control the
number of backups using Oracle's Recovery Manager and not this attribute. See Section
9.10.1 for restrictions in using this attribute.
8. Media Type: this is the media type that SBT uses to allocate tape volumes and tape drives.
You must have a media type.
9. Pool: this is the pool that SBT uses to allocate tape volumes along with location and media
type. If you do not need a pool to specify the volumes you want to allocate, specify
/NOPOOL.
10. Retention Days: this specifies the number of days that the volume will be retained before
being scratched. If you want different retention days for different backups, you can use a
different archive with a different retention days specified.
Now that you have created a catalog and archive, you are ready to test that everything is configured
correctly. The next section shows how to test the configuration.
9.5 Testing the Configuration of SBT
Now that you have linked SBT with the Oracle server or defined ABS_SBT logical for Oracle
9.2.0.2 and created a catalog and archive, you are ready to test the SBT configuration. Supplied
with SBT is a test program, SYS$SYSTEM:MDMS$SBTTEST_MA64.EXE, that allows you to
test the SBT interface with ABS/MDMS. This test program is applicable to Oracle 9.2.0.2 also.
If you have been using ABS/MDMS you may want to skip this section. It just gives you confidence
that ABS/MDMS is setup correctly.
Using sbttest is described in the Oracle documentation. However, their executable will not work
with the SYS$SHARE:MDMS$SBTSHR_MA64.EXE. Oracle supplied the sbttest code and I
compiled and linked it to work with SYS$SHARE:MDMS$SBTSHR_MA64.EXE and supplied
it for your use as SYS$SYSTEM:MDMS$SBTTEST_MA64.EXE.
You must have a catalog and archive defined to use sbttest. In Section 9.4 you created a catalog
and archive. You will use these for the test. The following commands show how to use sbttest:
$ SBTTEST :== $SYS$SYSTEM:MDMS$SBTTEST_MA64.EXE 1
$ DEFINE MDMS$SBT_ARCHIVE ORACLE_DB_ARCHIVE 2
$ DEFINE MDMS$SBT_CATALOG ORACLE_DB 3
$ SBTTEST TESTFILE -TRACE SBTTEST.TRC 4
MM software supports SBT API version 2.0
MM software is version 4.0.0.0
sbtinit, vendor description string="System Backup to Tape V4.0 (436)" 5
sbtinit successful
sbtinit2 successful
sbtbackup successful
sbtwrite2 successful, wrote 100 blocks
sbtinfo2, SBTBFINFO_NAME=testfile
sbtinfo2, SBTBFINFO_METHOD=stream
sbtinfo2, SBTBFINFO_COMMENT=Onsite: Description for AIF078
sbtinfo2, SBTBFINFO_CRETIME=Fri Dec 7 05:11:07 2001
sbtinfo2, SBTBFINFO_EXPTIME=Sat Dec 7 05:11:07 2002
sbtinfo2, SBTBFINFO_SHARE=single user
sbtinfo2, SBTBFINFO_ORDER=sequential access
sbtinfo2, SBTBFINFO_LABEL=AIF078
sbtinfo2 successful
sbtrestore successful
file was created by this program; seed=1007752246,
blk_size=16384, blk_count=100
sbtread2 successful, read 100 buffers
sbtclose2 successful
9-10 System Backup to Tape for Oracle Databases