Backing up an Oracle Data Guard environment

In Oracle 9i it is not possible to backup the current control file from the Standby database backup.
The best way to get a control file backup is to create a separate backup specification using the DP
GUI and in the Source Window select the current control file only. This backup will be taken directly
from the Production database, but the impact on the running production instance can be ignored.
To backup the control file of the Standby database in the same backup job do the following:
• Save the new backup specification and go back to “Options – Application Specific Options”
• Click on Advanced and hit the “Edit” button to get an Editor Window with the RMAN script
• Add a new backup statement with “backup … current control file for standby;” as shown in
the example below
run {
allocate channel 'dev_0' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DG1,OB2BARLIST=DG1_CTL_ONLY)';
backup
format 'DG1_CTL_ONLY<DG1_%s:%t:%p>.dbf'
current controlfile;
backup
format 'DG1_CTL_ONLY<DG1_%s:%t:%p>.dbf'
current controlfile for standby;
}
III. Backup with RMAN
The backup of a Standby database is also possible by calling Oracle’s RMAN utility directly.
To control the way how Data Protector will deal with the Oracle data, four Data Protector specific
options must be specified in the “allocate channel” command:
• OB2BARTYPE = Oracle8
• OB2APPNAME = <SID>
• OB2BARHOSTNAME = <Oracle Database system>
• OB2BARLIST = <Name of the Backup Specification>
While OB2BARTYPE, OB2APPNAME and OB2BARHOSTNAME are required by the backup Session
Manager (BSM) to resolve the instance details on the Data Protector Cell Manager, the OB2BARLIST
setting is used to allocate and start the backup tape devices that are specified in the named backup
specification.
13