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
System Backup to Tape for Oracle Databases 9.1 Linking System Backup to Tape with the Oracle Server 1. Linking SBT with the Oracle server 2. Defining the logical MDMS$SBT_TRACE_LEVEL 3. Configuring ABS 4. Testing the configuration of SBT 5. Using SBT with Oracle's Recovery Manager 6. Using the show catalog command 7. Using the MDMS scheduler 8. System Backup to Tape defaults 9. System Backup to Tape logicals names 10. System Backup to Tape Restrictions 11. Troubleshooting tips 9.1 Linking System Backup to Tape with the Oracle Server Note This section is not applicable for Oracle9i Release 2 (9.2.0.2). If you are using Oracle9i Release 2 (9.2.0.2), please skip this section (9.1) and refer to section 9.2 for configuring SBT with Oracle9i Release 2 (9.2.0.2). Before you can use SBT, you must link the SYS$SHARE:MDMS$SBTSHR_MA64.EXE shareable image with the Oracle server. This is a one time procedure. After performing this procedure, you can install a new release of ABS/MDMS and not have to relink the Oracle server to the new release of SBT. Note This linking of SBT to the Oracle server is not the same as described in the Oracle installation guide. The procedure in the Oracle installation guide does not use a shareable image and has you shutdown the database and relink with the vendors product with each new release. With the SBT shareable image and this procedure, you only have to shutdown the database and link one time. This section takes you through the procedure to link the SYS$SHARE:MDMS$SBTSHR_MA64.EXE shareable image with the Oracle server: 1. Testing Oracle's Recovery Manager 2. Authorizing privileges and Granting rights to the Oracle server account 3. Editing Oracle's link option file and command procedures 4. Shutdown the database 5. Relinking the ORA_RDBMS: executables 6. Startup the database 7. Retesting Oracle's Recovery Manager 9-2 System Backup to Tape for Oracle Databases
System Backup to Tape for Oracle Databases 9.1 Linking System Backup to Tape with the Oracle Server 9.1.1 Testing Oracle's Recovery Manager before linking System Backup to Tape Before doing the configuration for SBT, you should make sure that Oracle's Recovery Manager is setup and you are able to access it. If you have been using Oracle's Recovery Manager to write to disk, then you are ready to switch to SBT. If you have not been using Oracle's Recovery Manager, you should try a backup of a tablespace as shown in Example 9–1. Example 9–1 Oracle's Recovery Manager Backup of System Tablespace to Disk RMAN> run 2> { 3> allocate channel d1 type disk; 4> backup tablespace system; 5> release channel d1; 6> } Example 9–1 created the file ORA_DB:02D9MBV4_1_1.;1 on my system. Of course your file name will be different. If everything works then you are ready to link Oracle to SBT. If this step did not work, then your Oracle Recovery Manager is not setup correctly. You need to correct this before proceeding. 9.1.2 Authorizing privileges and granting rights to the Oracle server account Before using SBT, you must authorize the VOLPRO privilege and grant the MDMS_APPLICATION identifier to the Oracle server database administrator account. The VOLPRO privilege allows the Oracle server to mount volumes that belong to ABS. All volumes belong to ABS. The MDMS_APPLICATION allows the Oracle server to use the objects in the MDMS database. The following example shows the commands that modify the privileges and grant the right to an account called ORACLE9I: $ MCR AUTHORIZE UAF> MODIFY ORACLE9I/PRIVILEGES=VOLPRO UAF> GRANT/ID MDMS_APPLICATION ORACLE9I UAF> EXIT $ Note Be sure to logout and log back in so that the privileges and rights take effect. 9.1.3 Editing Oracle's Link Option File and Command Procedures In order to link the SBT shareable image, you must change Oracle's link option file and command procedures. This section covers what you need to do for Oracle8i and Oracle9i. 9.1.3.1 Editing Oracle8i Link Option File and Command Procedures In order to link the SBTshareable image, you must change three of Oracle's files. Before editing these three files, we suggest that you make a copy of the file. In each file, you may need to comment out the line ora_rman_mml_64/lib and/or add the line SYS$SHARE:MDMS$SBTSHR_MA64.EXE/SHARE. The following are the three files and an example of each file with the line to comment out and/or the line to be added commented: • ORA_UTIL:RDBMS_RMAN_NOSHARE.OPT as shown in Example 9–2. • ORA_RDBMS:LORACLE_64.COM as shown in Example 9–3. • ORA_UTIL:LOUTL.COM as shown in Example 9–4 System Backup to Tape for Oracle Databases 9–3
- Page 94 and 95: Media Management 4.11 Volumes • R
- Page 96 and 97: Media Management 4.11 Volumes 4.11.
- Page 99 and 100: 5 Security The security model used
- Page 101 and 102: Security 5.1 MDMS Rights Table 5-1
- Page 103 and 104: Table 5-4 Domain Access Control Opt
- Page 105 and 106: 6 User Interfaces ABS and MDMS supp
- Page 107 and 108: 6.1.3 Logging In User Interfaces 6.
- Page 109 and 110: User Interfaces 6.1 Graphical User
- Page 111 and 112: User Interfaces 6.1 Graphical User
- Page 113 and 114: Figure 6-5 Domain View Showing Expa
- Page 115 and 116: User Interfaces 6.1 Graphical User
- Page 117 and 118: 6.1.13 Viewing MDMS Audit and Event
- Page 119 and 120: 6.2.1 Syntax Overview User Interfac
- Page 121 and 122: User Interfaces 6.3 User Interface
- Page 123 and 124: 7 Preparing For Disaster Recovery I
- Page 125 and 126: 7.1.2 Backup of MDMS$ROOT Preparing
- Page 127 and 128: 7.2 Prolog and Epilog Procedure Pre
- Page 129 and 130: 7.2.1 Restoring The System Disk To
- Page 131 and 132: 8 Remote Devices 8.1 RDF Installati
- Page 133 and 134: Remote Devices 8.4 Monitoring and T
- Page 135 and 136: 8.4.4 Changing Network Parameters f
- Page 137 and 138: • Free Space is 20 Remote Devices
- Page 139 and 140: Remote Devices 8.5 Controlling Acce
- Page 141: Remote Devices 8.7 RDF Error Messag
- Page 146 and 147: System Backup to Tape for Oracle Da
- Page 148 and 149: System Backup to Tape for Oracle Da
- Page 150 and 151: System Backup to Tape for Oracle Da
- Page 152 and 153: System Backup to Tape for Oracle Da
- Page 154 and 155: System Backup to Tape for Oracle Da
- Page 156 and 157: System Backup to Tape for Oracle Da
- Page 158 and 159: System Backup to Tape for Oracle Da
- Page 160 and 161: System Backup to Tape for Oracle Da
- Page 162 and 163: System Backup to Tape for Oracle Da
- Page 164 and 165: System Backup to Tape for Oracle Da
- Page 166 and 167: System Backup to Tape for Oracle Da
- Page 168 and 169: System Backup to Tape for Oracle Da
- Page 170 and 171: System Backup to Tape for Oracle Da
- Page 172 and 173: System Backup to Tape for Oracle Da
- Page 174 and 175: Virtual Library System (VLS) 10.3 Q
- Page 176 and 177: Architecture 11.1 The Server Proces
- Page 178 and 179: Architecture 11.2 Scheduler Interfa
- Page 180 and 181: Architecture 11.3 Catalogs Example
- Page 182 and 183: Architecture 11.4 Coordinator 11.4.
- Page 184 and 185: Troubleshooting 12.2 Media Manageme
- Page 186 and 187: Troubleshooting 12.2 Media Manageme
- Page 188 and 189: Troubleshooting 12.4 ABS Catalogs 1
- Page 190 and 191: Troubleshooting 12.5 Windows and Un
- Page 192 and 193: Troubleshooting 12.6 RDF (Remote De
<strong>System</strong> <strong>Backup</strong> <strong>to</strong> Tape <strong>for</strong> Oracle Databases<br />
9.1 Linking <strong>System</strong> <strong>Backup</strong> <strong>to</strong> Tape with the Oracle Server<br />
9.1.1 Testing Oracle's Recovery Manager be<strong>for</strong>e linking <strong>System</strong> <strong>Backup</strong> <strong>to</strong> Tape<br />
Be<strong>for</strong>e doing the configuration <strong>for</strong> SBT, you should make sure that Oracle's Recovery Manager<br />
is setup and you are able <strong>to</strong> access it. If you have been using Oracle's Recovery Manager <strong>to</strong> write<br />
<strong>to</strong> disk, then you are ready <strong>to</strong> switch <strong>to</strong> SBT. If you have not been using Oracle's Recovery Manager,<br />
you should try a backup of a tablespace as shown in Example 9–1.<br />
Example 9–1 Oracle's Recovery Manager <strong>Backup</strong> of <strong>System</strong> Tablespace <strong>to</strong> Disk<br />
RMAN> run<br />
2> {<br />
3> allocate channel d1 type disk;<br />
4> backup tablespace system;<br />
5> release channel d1;<br />
6> }<br />
Example 9–1 created the file ORA_DB:02D9MBV4_1_1.;1 on my system. Of course your file<br />
name will be different. If everything works then you are ready <strong>to</strong> link Oracle <strong>to</strong> SBT. If this step<br />
did not work, then your Oracle Recovery Manager is not setup correctly. You need <strong>to</strong> correct this<br />
be<strong>for</strong>e proceeding.<br />
9.1.2 Authorizing privileges and granting rights <strong>to</strong> the Oracle server account<br />
Be<strong>for</strong>e using SBT, you must authorize the VOLPRO privilege and grant the<br />
MDMS_APPLICATION identifier <strong>to</strong> the Oracle server database administra<strong>to</strong>r account. The<br />
VOLPRO privilege allows the Oracle server <strong>to</strong> mount volumes that belong <strong>to</strong> ABS. All volumes<br />
belong <strong>to</strong> ABS. The MDMS_APPLICATION allows the Oracle server <strong>to</strong> use the objects in the<br />
MDMS database.<br />
The following example shows the commands that modify the privileges and grant the right <strong>to</strong> an<br />
account called ORACLE9I:<br />
$ MCR AUTHORIZE<br />
UAF> MODIFY ORACLE9I/PRIVILEGES=VOLPRO<br />
UAF> GRANT/ID MDMS_APPLICATION ORACLE9I<br />
UAF> EXIT<br />
$<br />
Note<br />
Be sure <strong>to</strong> logout and log back in so that the privileges and rights take effect.<br />
9.1.3 Editing Oracle's Link Option File and Command Procedures<br />
In order <strong>to</strong> link the SBT shareable image, you must change Oracle's link option file and command<br />
procedures. This section covers what you need <strong>to</strong> do <strong>for</strong> Oracle8i and Oracle9i.<br />
9.1.3.1 Editing Oracle8i Link Option File and Command Procedures<br />
In order <strong>to</strong> link the SBTshareable image, you must change three of Oracle's files. Be<strong>for</strong>e editing<br />
these three files, we suggest that you make a copy of the file. In each file, you may need <strong>to</strong> comment<br />
out the line ora_rman_mml_64/lib and/or add the line<br />
SYS$SHARE:MDMS$SBTSHR_MA64.EXE/SHARE. The following are the three files and an<br />
example of each file with the line <strong>to</strong> comment out and/or the line <strong>to</strong> be added commented:<br />
• ORA_UTIL:RDBMS_RMAN_NOSHARE.OPT as shown in Example 9–2.<br />
• ORA_RDBMS:LORACLE_64.COM as shown in Example 9–3.<br />
• ORA_UTIL:LOUTL.COM as shown in Example 9–4<br />
<strong>System</strong> <strong>Backup</strong> <strong>to</strong> Tape <strong>for</strong> Oracle Databases 9–3