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

To use the rmora_rsync command, the following requirements must be satisfied:
•
Each database instance must be started up using either a parameter file (pfile) or server
parameter file (spfile) from default location ($ORACLE_HOME/dbs).
•
The database must be running in archive log mode and automatic archival must be enabled
in order to create an online Virtual Copy.
•
If archive log mode is enabled, the datafiles and archive logs must reside on separate HP
3PAR virtual volumes.
•
The online redo logs and control files should not reside on the same HP 3PAR virtual volumes
used by the datafiles and archive logs to avoid being restored when using Recovery Manager
rollback (promote) feature. However, the online redologs and control files can share the same
HP 3PAR virtual volumes.
•
If database files reside on Symantec VxVM volumes, the datafiles and archive logs must reside
on separate VxVM disk groups. The online redo logs and control files should not reside on
the same VxVM Volumes used by the datafiles and archive logs.
•
If you use LVM Volume Manager, the Oracle datafiles and archive logs must reside on separate
LVM volume groups. In addition, online redo logs and control files must not reside on LVM
volume groups that are used by Oracle datafiles and archive logs. However, the online redo
logs and control files can reside on the same LVM volume group.
•
If the Oracle database is an ASM-managed database, the Oracle datafiles and archive logs
must reside on separate ASM disk groups. To avoid being rolled back when using the Recovery
Manager Rollback feature, the online redo logs and control files should not reside on the same
ASM disk groups used by the datafiles and archive logs. In addition, ASM disk groups should
not be shared between different databases.
•
If the Oracle database is an RAC database, all RAC instances must share the same archive
log destinations (i.e., the same cluster file system or the same ASM disk groups).
•
Datafile and archive log volumes can be in the same Remote Copy (RC) group or separate
RC groups for periodic or synchronous mode. In SyncLD configuration, if datafile and archive
log volumes are in the same RC group, when a failover occurs, a full synchronization of the
RC group between the periodic secondary system and the new primary system is required.
Redo log volumes are not required to be in an RC group for periodic mode. Redo log volumes
must not belong to neither datafile nor archive log RC groups for synchronous mode or SyncLD
configuration.
•
The Remote Copy group resynchronization frequency must be disabled to avoid interfering
with Recovery Manager for Oracle operations.
OPTIONS
The following options are supported:
-s
The Oracle SID of the database instance. For Real Application Cluster (RAC) database, an Oracle
SID of any RAC instance can be specified.
-p
The corresponding host name of the database server where the specified Oracle database instance
is running. The value of the database server name must match the output of the hostname
command.
-l
The host name of a local backup server. When specified, a database Virtual Copy is also created
on the local/primary system. The database Virtual Copy information is saved to the repository on
the local backup server.
Recovery Manager Commands 99