HP A.06.11 - Manual (Page 35)

• Oracle database identifiers (DBIDs) of all databases must be unique within a Data
Protector cell.
• 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.
• 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.
Cluster-aware clients
In cluster environment, if you intend to use the Data Protector CLI, set the Data Protector
environment variable OB2BARHOSTNAME to the virtual server name. Set the variable
on the Oracle Server system as follows:
Windows: set OB2BARHOSTNAME=virtual_server_name
UNIX: export OB2BARHOSTNAME=virtual_server_name
RAC: Configure an Oracle database on every node from where you want to run
backups and restores.
HP-UX with RAC: If you want to use virtual hostname, create an MC/ServiceGuard
package containing only the virtual IP and the virtual hostname parameters and
distribute it among the RAC nodes.
Integration guide for Oracle and SAP 35