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

•
The online redo logs and control files should not reside on the same 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
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 HP 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. 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.
OPTIONS
The following options are supported:
-s <oracle_sid>
The Oracle SID of the database instance. For Real Application Cluster (RAC) database, an Oracle
SID of any RAC instance can be specified.
-p <db_server>
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 <local_backup_server>
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.
NOTE: Recovery Manager for Oracle must be pre-configured on the local backup server prior
to executing rmora_sync with the -l option.
-o online
Create an online database virtual copy in Remote Copy or Synchronous Long Distance configuration.
The specified database instance must be online.
-o hotbkup
This option is the same as the -o online and is deprecated.
-o offline
Create an offline database virtual copy in Remote Copy or Synchronous Long Distance configuration.
The specified database instance must be offline.
Recovery Manager Commands 83