HP 3PAR Application Software Suite for Oracle - Manual (Page 23)

Recovery Manager for Oracle with Oracle Standby Database
All HP 3PAR Recovery Manager Software for Oracle’s utilities can be run against an Oracle
physical standby database instead of the production database. This completely eliminates the
performance impact on the production database.
In addition to the current Recovery Manager for Oracle’s limitations and restrictions when running
against an Oracle primary database, the following limitations and restrictions apply when running
against an Oracle physical standby database:
•
Only Oracle 10g and 11g are supported.
•
A standby database must be a physical standby database. Logical and snapshot standby
databases are not supported.
•
If using Oracle RMAN for backup, the primary database, and not the standby database, must
be registered with Oracle Recovery Catalog.
•
A snapshot of a standby database can be used to promote back to the standby database
volumes, but it cannot be used to promote back to the primary database volumes.
•
Oracle parameter file and control file are not compatible between the standby database and
the primary database. They cannot be used to restore to the primary database unless Oracle
RMAN (11g) is used for restoring. This means that the Oracle parameter file and control file
of the primary database must be backed up manually outside of the Recovery Manager for
Oracle.
Recovery Manager for Oracle and Autonomic Groups
HP 3PAR Autonomic Groups allow domains, hosts, and virtual volumes to be grouped into a set
that is managed as a single object. HP 3PAR Recovery Manager Software for Oracle supports
domain sets, and can coexist with host sets and volume sets. Refer to the HP 3PAR OS Concepts
Guide for additional information about 3PAR Autonomic Groups.
Recovery Manager for Oracle and Domain Sets
HP 3PAR Recovery Manager Software for Oracle allows the management of multiple database
servers belonging to different virtual domains from a single backup server.
The following configuration requirements must be met:
•
The HP 3PAR StoreServ Storage system must be running HP 3PAR OS 2.3.1 or later.
•
The backup server must belong to a domain set, which contains all database servers’ virtual
domains to be managed by the backup server.
•
The HP 3PAR OS user used by Recovery Manager for Oracle to access the HP 3PAR StoreServ
Storage system from the backup server must belong to the virtual domains of all the database
servers.
Recovery Manager for Oracle and Host Sets
Database servers (nodes) within the same Real Application Cluster (RAC) can be grouped into a
set, which can then be managed as a single object. If the backup server also belongs to a host
set, Recovery Manager for Oracle continues to export/deport database Virtual Copies to the
backup server, rather than the host set that contains the backup server.
Recovery Manager for Oracle and Virtual Volume Sets
Database virtual volumes can be grouped into a set on the database server, which can be managed
as a single object. Recovery Manager for Oracle works with the volume sets, but from the backup
server, it does not make use of them as database virtual volumes must still be discovered to ensure
that all database volumes are included in the volume set.
Recovery Manager for Oracle with Oracle Standby Database 23