Filter
Top Products
Integrating Oracle and Data Protector
Integration Concept
Chapter 1 7
These features can be used for online or offline backup of the Oracle
target database. However, you must ensure that the backup objects (such
as tablespaces) are switched into the appropriate state before and after a
backup session. For online backup, the database instance must operate
in the ARCHIVELOG mode; whereas for offline backup, objects need to be
prepared for backup using the Pre-exec and Post-exec options in the
backup specification.
The Data Protector backup specification contains information about
backup options, commands for RMAN, Pre- and Post-exec commands,
media, and devices.
The Data Protector backup specification allows you to configure a backup
and then use the same specification several times. Furthermore,
scheduled backups can only be performed using a backup specification.
Backup and restore of an Oracle target database can be performed using
the Data Protector User Interface, the RMAN utility, or the Oracle
Enterprise Manager utility.
The heart of the Data Protector Oracle integration is MML, which
enables an Oracle server process to issue commands to Data Protector for
backing up or restoring parts or all of the Oracle target database files.
The main purpose is to control direct interaction with media and devices.
Backup Flow A Data Protector scheduled or interactive backup is triggered by the
Data Protector Backup Session Manager, which reads the backup
specification and starts the ob2rman.pl command on the Oracle Server
under a specific user. This user must be defined as the owner of the Data
Protector Oracle backup specification. Further on, ob2rman.pl prepares
the environment to start the backup, and issues the RMAN backup
command. RMAN instructs the Oracle Server processes to perform the
specified command.
The Oracle Server processes initialize the backup through MML, which
establishes a connection to the Data Protector Backup Session Manager.
The Backup Session Manager starts the General Media Agent, sets up a
connection between MML and the General Media Agent, and then
monitors the backup process.
The Oracle Server processes read the data from the disks and send it to
the backup devices through MML and the General Media Agent.
RMAN writes information regarding the backup either to the recovery
catalog (if one is used) or to the control file of the Oracle target database.