Integrating Oracle and Data Protector

Configuring the Integration

The Data Protector Oracle integration does not support the RMAN disk backup of a target database to the flash recovery area. The Data Protector Oracle integration supports only backups from the flash recovery area to a backup device. However, you can create an RMAN script that backs up the target database to the flash recovery area before or after the Data Protector backs up files from the flash recovery area to a backup device. The script can be set up using the Pre-execor Post-execoption when creating a backup specification.

On an OpenVMS client, you can only configure a Data Protector admin user with the username <Any> and the group name <Any>. This limitation is due to the lack of the user group name concept on OpenVMS.

Oracle Data Guard:

You cannot configure only a standby database (without configuring primary database).

Only physical standby database backup is supported.

Recovery catalog database is required for standby configurations.

The Oracle database identifier (DBID) must be unique for all databases within a Data Protector cell.

For other limitations regarding RMAN backup, restore, recovery, and duplication in Oracle Data Guard environment, see the Oracle documentation.

Before You Begin

Configure devices and media for use with Data Protector.

Test whether the Oracle Server system and the Cell Manager communicate properly: Configure and run a Data Protector filesystem backup and restore on the Oracle Server system.

Identify the Oracle database user that will be used by Data Protector for backup. This user must have the SYSDBA privilege granted. For example, it could be the Oracle user sys, which is created during database creation.

See the Oracle documentation for more information on user privileges in Oracle.

Chapter 1

13

Page 35
Image 35
HP OpenView Storage B6960-96008 manual Before You Begin, Oracle Data Guard