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

rmora_create
SYNTAX
rmora_create -s <oracle_sid> -p <db_server> [-o
online|offline|archlog|archonly|datafile] [-r <time>{d|D|h|H} -f] [-v]
[-e <expiration_time>{d|D|h|H}]
DESCRIPTION
The rmora_create command can be used to create an online, offline, datafile, or archive log
virtual copy of a specified Oracle database instance. The Oracle database instance can be either
a regular database or a physical standby database. The database virtual copy can be set to be
retained for a period of time (retention time) preventing them from being removed accidentally or
intentionally. The database virtual copy can also be set to expire after a period of time (expiration
time) in which the storage system will remove the expired virtual copy automatically once the
expiration time is reached.
•
An online or offline virtual copy is a consistent point-in-time snapshot image of the database
when it is online or offline, respectively.
•
An archive log virtual copy is a snapshot image of the archive log destination only. You can
use the archive log virtual copy in conjunction with an online virtual copy to simulate an
incremental backup.
•
A datafile virtual copy is a snapshot image of the datafiles only (without the archive logs). If
you use datafile virtual copies, be sure to back up the archive logs separately so they are
available for performing database restore and recovery from a datafile virtual copy. You can
mount the virtual copy on the backup server for any offhost processing purposes (for example;
backup or database cloning).
The specified database instance must be offline when creating an offline virtual copy or online
when creating an online, datafile or archive log virtual copy. The database instance is considered
to be offline if it is in CLOSED mode. If the database is a RAC database, all RAC instances must
be offline. The database instance is considered to be online if it is in OPEN mode (for regular
database) or in managed recovery mode (for physical standby database). If the database is a
RAC database, the specified database instance must be online, all other RAC instances can be
either online or offline.
If the database being snapshot is a physical standby database and Oracle release is not 11g, the
Oracle parameter file and control file of the production database must be backed up manually in
addition to the virtual copy. This is because the parameter file and control file are not compatible
between the standby and production database.
When you create an online or archlog virtual copy, a virtual copy is created for the virtual volumes
used by all MANDATORY archive log destinations. If there is no MANDATORY archive log
destination, a virtual copy is created for the virtual volumes used by all OPTIONAL archive log
destinations.
Recovery Manager for Oracle does not create virtual copies for virtual volumes used by Oracle
database temporary files, in order to be consistent with Oracle's backup procedure. However,
Recovery Manager for Oracle does take virtual copies for read-only and offline datafiles. (After
the database is cloned on the backup server, be sure to rename the read-only and offline datafiles
as appropriate: use the syntax in the ascii control file that is saved in the timestamp repository to
replace the real file names that are based on the mount points during cloning.)
When creating an online or datafile virtual copy:
•
If the specified database instance is a regular database, the database will be temporarily put
into backup mode before the virtual copy of datafile virtual volumes is created. The database
62 Using the Recovery Manager Command Line Interface