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

•
A Datafile virtual copy indicates that the virtual copy for the database was created while it
was OPEN (online) and contains only datafiles (no archive log destination).
•
An Archlog virtual copy indicates that the virtual copy was created for archive log destination
only.
A virtual copy's status can be either Available, Removed, Mounted, Mounted(P), or
Database
.
•
Available status indicates that the virtual copy exists and is not currently mounted or cloned.
•
Removed status indicates that the virtual copy is removed.
•
Mounted status indicates that the virtual copy is currently mounted.
•
Mounted(P) status indicates that the virtual copy is partially mounted.
NOTE: To remount the virtual copy, use the rmora_mount command with the –r option.
To change the virtual copy status to Available, use the rmora_umount command.
•
Database status indicates that a database has been cloned using the virtual copy.
A virtual copy's backup status can be either Y or N, where Y indicates that the virtual copy has
been backed up and N indicates that the virtual copy has not been backed up.
The Virtual Copy Mount Utility
HP 3PAR Recovery Manager Software for Oracle’s mount utility mounts an existing database virtual
copy that was created using the create utility on the backup server using the rmora_mount
command. 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 virtual copy's status 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 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:
◦ If the ASM version on the backup server is 10.2.0.5 or 11.1.0.7 and above, one virtual
copy per database can be mounted at any time on the backup server. However, virtual
copies from different databases can be mounted concurrently.
◦ If the ASM version on the backup server is 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.
12 Overview of Recovery Manager Operations