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

rmora_mount
SYNTAX
rmora_mount -s <oracle_sid> -p <db_server> -t <timestamp> [-m
<mountpoint>] [-r] [-v]
DESCRIPTION
The rmora_mount command mounts an existing Virtual Copy created by the rmora_create
command or rmora_rsync command on the backup server. The mounted Virtual Copy can be
used for off-host processing purposes such as backup or database cloning.
The following restrictions apply when mounting a database Virtual Copy:
•
The Virtual Copy must have an Available or Mounted(P) status in order to be mounted.
The status of a Virtual Copy can be retrieved using the Recovery Manager for Oracle display
utility.
•
The same Virtual Copy cannot be mounted concurrently at different mount points.
•
If the database files reside on Symantec VxVM Volumes, only one Virtual Copy per database
can be mounted at any time on the backup server. This is due to the VxVM disk groups from
different Virtual Copies of the same database having the same names and so cannot be
imported at the same time.
•
If Oracle datafiles and archive logs reside on HP or Linux LVM volumes, HP 3PAR Recovery
Manager for Oracle allows only one Virtual Copy of the same database to be mounted. You
must unmount a mounted Virtual Copy before mounting a different Virtual Copy.
•
If the database files reside on ASM disk groups, it is dependent on which ASM database
version is installed on the backup server, different restrictions apply as follows:
◦ Make sure the backup host has +ASM instance created and configured properly in order
for Recovery Manager for Oracle mount and/or unmount operations being able to use
the existing +ASM instance, or bring it up if it is originally down.
◦ If the ASM version on the backup server is 10.2.0.5 or 11.1.0.7 or above, one Virtual
Copy per database can be mounted on the backup server. Virtual copies from different
databases can be mounted concurrently.
◦ If the ASM version on the backup server is running versions lower than the releases
mentioned in the previous bullet, only one Virtual Copy can be mounted at any time on
the backup server. This restriction prevents an Oracle ASM instance on the backup server
from hanging due to some ASM's idle processes still holding a Virtual Copy's devices,
even though the corresponding ASM disk groups are dropped.
•
For OCFS2 1.4.1 or above, Recovery Manager for Oracle supports multiple Virtual Copies
per database being mounted simultaneously. For versions lower than OCFS2 1.4.1, only one
Virtual Copy per database can be mounted at any time on the backup server.
•
For online backup and archlog backup, all MANDATORY archive log destinations are mounted.
If no MANDATORY archive log destinations are found, all OPTIONAL archive log destinations
are mounted.
Mounting a database Virtual Copy involves the following actions:
•
Creates a read-write Virtual Copy of the original read-only Virtual Copy.
•
Imports the read-write Virtual Copy to the backup server.
•
Imports snapshot Symantec VxVM disk groups and starts up all corresponding snapshot VxVM
volumes if the database files reside on VxVM volumes.
72 Using the Recovery Manager Command Line Interface