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

The cloned database is shutdown with the shutdown immediate option. The database related
files (Oracle parameter file, control files and redo logs), which are previously created by the
rmora_createdb
command, are removed. The read-write Virtual Copy remains mounted.
The Virtual Copy Removal Utility
HP 3PAR Recovery Manager for Oracle’s Virtual Copy removal utility removes an existing Virtual
Copy from the HP 3PAR StoreServ Storage system. The Virtual Copy must have Available or
Available(P)
status in order to be removed using the rmora_remove command. The status
of a Virtual Copy is obtained by using the display utility rmora_display.
This utility only removes the read-only Virtual Copy from the system to free up the snapshot space.
It does not actually remove the repository information if the Virtual Copy has been backed up to
the media. This enables Recovery Manager for Oracle to restore a Virtual Copy, which has been
previously backed-up to the media on the original volumes, as long as the Virtual Copy repository
exists.
Integration with HP 3PAR Virtual Lock Software
HP 3PAR Virtual Lock Software allows administrators to apply a configurable retention period to
virtual volumes - including thin volumes created with HP 3PAR Thin Provisioning Software and
virtual volume copies such as those created with HP 3PAR Recovery Manager for Oracle.
The Virtual Lock utilities prevent read-only Virtual Copies from being accidentally or intentionally
removed. This is achieved by enforcing a predefined retention time for the read-only Virtual Copy.
Be cautious that once the retention time is set, it cannot be removed or reduced. It can only be
removed after the retention time ends.
This feature is only available for HP 3PAR OS 2.3.1 or later and requires an HP 3PAR Virtual Lock
Software license.
There are a few ways to enforce the retention time for read-only Virtual Copies.
•
During configuration, the retention value specified will be the default value for new read-only
Virtual Copies created via rmora_create, rmora_rsync, and rmora_backup (without
the -t option).
•
Use rmora_create -r or rmora_rsync -r to override the default value specified during
configuration.
•
Use the rmora_set command for the specified Virtual Copy to extend its retention time.
•
Retention time can be displayed by using rmora_display with the -r option.
The Virtual Copy Repository
HP 3PAR Recovery Manager Software for Oracle records important information for each Virtual
Copy taken by the Recovery Manager for Oracle utilities. The information is used by Recovery
Manager for Oracle, especially for database restoration. The information is stored in the repository
at:
/etc/3par/solutions/<db_server>.ora.<oracle_sid>/<timestamp>
To avoid unpredictable errors, do not manually modify the directories and files in this repository.
The Virtual Copy Repository Removal Utility
HP 3PAR Recovery Manager Software for Oracle’s Virtual Copy repository removal utility removes
a Virtual Copy’s repository created using the create utility (
“The Virtual Copy Creation Utility”
(page 11) ). The Virtual Copy that has been removed must have Removed status in order for
Recovery Manager for Oracle to remove the repository. The status of a Virtual Copy can be obtained
using the display utility (
“The Virtual Copy Display Utility” (page 12) ).
16 Overview of Recovery Manager Operations