To create an Oracle backup specification, proceed as follows:
1. In the Context List, click Backup.
2. In the Scoping Pane, expand Backup Specifications, right-click Oracle Server, and click Add Backup.
3. In the Create New Backup dialog box, double-click Blank Oracle Backup to create a backup specification without predefined options, or use one of the pre-defined templates given below:
Archive Backs up the Archived Redo Logs.
Archive_Delete Backs up the Archived Redo Logs, then deletes them after the backup.
Whole_Online Backs up the database instance and the Archived Redo Logs.
Whole_Online_Delete Backs up the database instance and the Archived Redo Logs, and then deletes the Archived Redo Logs.
Database_Archive Backs up the database instance and the Archived Redo Logs.
Database_Switch_Archive Backs up the database instance, switches the Online Redo Logs and backs up the Archived Redo Logs.
Database_Switch_ArchiveDel Backs up the database instance, switches the Online Redo Logs, backs up the Archived Redo Logs and then deletes the Archived Redo Logs.
Direct_Database Backs up the database instance and controlfile.
SMB_Proxy_Database Backs up the database instance and control file in the ZDB (split mirror or snapshot) mode using the proxy-copy method.
SMB_BackupSet_Database Backs up the database instance and control file in the ZDB (split mirror or snapshot) mode using the backup set method.
Click OK.
4. In the Client, select the Data Protector Oracle integration client. In a cluster environment, select the virtual server.
RAC: Select either the node or the virtual server of the Oracle resource group. The latter can only be selected on HP-UX.
Oracle Data Guard: Select either a primary system or secondary (standby) system.
In Application database, type the name of the database to be backed up.
The database name can be obtained as follows:
SQL> select name from v$database;
NOTE In a single-instance configuration, the database name is usually the same as its instance name. In this case, the instance name can be also used. The instance name can be obtained as follows:
SQL>select instance_name from v$instance;
RAC: Note that the database name is the same for all instances.
UNIX only: Type the username and user group of the Oracle user.
See “Configuring Oracle Users on UNIX and OpenVMS” on page 21 for information on how to identify that user.
Figure 1-8 Specifying an Oracle Server System (Windows)
Figure 1-9 Specifying an Oracle Server System (UNIX)
Click Next.
5. If the Oracle database is not configured yet for use with Data Protector, the Configure Oracle dialog box is displayed. Configure the Oracle database for use with Data Protector as described in
“Configuring Oracle Databases” on page 24.
6. Select the Oracle database objects to be backed up.
For example, a single tablespace can be separately selected for backup, but for a complete online backup of the database, the ARCHIVELOGS must also be selected.
Oracle 10g: The archived logs can reside in the flash recovery area.
In this case, if you select the FLASH RECOVERY AREA to be backed up, you do not need to select also ARCHIVELOGS.
Oracle Data Guard (10g): If the database is configured with standby connection, you can back up a control file for the standby
NOTE If your database uses a recovery catalog, it is backed up by default after each database backup, unless otherwise specified in the backup
specification.
Figure 1-10 Selecting Backup Objects
Click Next.
7. Select the device(s) you want to use for the backup. Click Properties to set the device concurrency, media pool, and preallocation policy. For more information on these options, click Help.
You can also specify whether you want to create additional copies (mirrors) of the backup during the backup session. Specify the desired number of mirrors by clicking the Add mirror and Remove mirror buttons. Select separate devices for the backup and for each mirror.
For detailed information on the object mirror functionality, see the online Help index: “object mirroring”.
Click Next to proceed.
8. Set the backup options.
For information on the Backup Specification Options and Common Application Options, see the online Help.
Oracle Data Guard: To back up a standby database, you must select Back up standby database in the Application Specific Options dialog box.
For information on the Application Specific Options (Figure 1-11), see Table 1-2 on page 44 or online Help.
TIP When backing up data from the Oracle 10g flash recovery area to tape, you can specify the location of the RMAN script that performs backups to the flash recovery area in the Pre-exec or Post-exec text box. The script will be executed every time before (Pre-exec) or after (Post-exec) the Data Protector Oracle integration backup to tape.
Figure 1-11 Oracle Specific Options
Click Next.
9. Optionally, schedule the backup. For more details, see “Scheduling a Backup” on page 58.
Click Next.
10. Save the backup specification. It is recommended that you save all Oracle backup specifications in the Oracle group.
IMPORTANT The word DEFAULT is a reserved word and therefore must not be used for backup specification names or labels of any kind. Oracle does not allow full stops in backup piece. Therefore, do not use a punctuation in the names of backup specifications, since the Oracle channel format is created from the backup specification name.
Figure 1-12 Saving the Backup Specification
Click OK.
To start the backup, see “Backing Up an Oracle Database” on page 55.
11. On UNIX, after the backup specification is saved, verify that the owner of the backup specification is the specified Oracle user. See
“Configuring Oracle Users on UNIX and OpenVMS” on page 21 for details about this user.
12. You can examine the newly-created and saved backup specification in the Backup context, under the specified group of backup
specifications. The backup specification is stored in the following file on the Cell Manager:
Windows:
<Data_Protector_home>\Config\server\Barlists\Oracle8\<B ackup_Specification_Name>
UNIX:
/etc/opt/omni/server/barlists/oracle8/<Backup_Spec_Name>
13. It is recommended to test the backup specification. See “Testing the Integration” on page 52 for details.
Table 1-2 Oracle Backup Options
Disable recovery catalog auto backup
By default, Data Protector backs up the recovery catalog in every backup session. Select this option to disable backup of the recovery catalog.
Disable Data Protector managed control file backup
By default, Data Protector backs up the Data Protector managed control file in every backup session. Select this option to disable backup of the Data Protector managed control file.
Back up standby database
Oracle Data Guard: This option is applicable if the database is configured with the standby connection. By default, RMAN backs up the database files and archived redo logs on the primary system. Select this option to enable backup of the database files and archive logs on standby system. However, only the archive logs created after the standby database was configured can be backed up at standby site. Archive logs created before the standby database was configured must be backed up on the primary database.
Note that the current control file or the control file for standby will still be backed up from the primary system.
RMAN Script You can edit the Oracle RMAN script section of the Data Protector Oracle backup specification. The script is created by Data Protector during the creation of a backup specification and reflects the backup specification’s selections and settings. You can edit the script only after the backup specification has been saved. For information on how to edit the RMAN script section, see “Editing the Oracle RMAN Script” on page 47.
Pre-exec, Post-exec
Specify a command or RMAN script that will be started by ob2rman.pl on the Oracle server system before the backup (pre-exec) or after it (post-exec). RMAN scripts must have the .rman extension. Do not use double quotes.
For example, you can provide scripts to shut down and start an Oracle instance. For UNIX, see “Examples of Pre-Exec and Post-Exec Scripts on UNIX” on page 46.
Provide the pathname of the command or RMAN script.
OpenVMS: Provide the pathname of the command (OMNI$ROOT:[BIN]).
Table 1-2 Oracle Backup Options
Examples of Pre-Exec and Post-Exec Scripts on UNIX
Pre-Exec Example The following is an example of a script that shuts down an Oracle instance:
#!/bin/sh
export ORACLE_HOME=$2
export ORACLE_SQLNET_NAME=$1
if [ -f $ORACLE_HOME/bin/sqlplus ]; then
$ORACLE_HOME/bin/sqlplus << EOF
connect sys/manager@$ORACLE_SQLNET_NAME as sysdba shutdown
EOF
echo "Oracle database \"$DB_NAME\" shut down."
exit 0 else
echo "Cannot find Oracle SQLPLUS ($ORACLE_HOME/bin/sqlplus)."
exit 1 fi Post-Exec
Example
The following is an example of a script that starts an Oracle instance:
#!/bin/sh
export ORACLE_HOME=$2
export ORACLE_SQLNET_NAME=$1
if [ -f $ORACLE_HOME/bin/sqlplus ]; then
$ORACLE_HOME/bin/sqlplus << EOF
connect sys/manager@$ORACLE_SQLNET_NAME as sysdba startup
EOF
echo "Oracle database \"$DB_NAME\" started."
exit 0 else
($ORACLE_HOME/bin/sqlplus)."
exit 1 fi