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

For a time-based policy example, if the expiration time is one month (specified in the configuration
file), then the Virtual Copy that reaches the expiration time will be removed from the HP 3PAR
StoreServ Storage system automatically. The system has all the Virtual Copies for last month.
Expiration time can be changed using the rmora_set command.
Database Rollback from a Virtual Copy
When a database is corrupted, you can restore the database to the most recent database images
from the most recently created Virtual Copy by using the rollback utility.
The Database Rollback Utility
The database rollback utility (rmora_rollback) of HP 3PAR Recovery Manager Software for
Oracle promotes the volume of a Virtual Copy back to its base virtual volumes. In other words, the
base virtual volumes used by the database are rolled back to the Virtual Copy volumes. Once the
rollback process completes successfully, the base virtual volumes are exactly the same as the Virtual
Copy volumes. If the base volume size has been changed since the Virtual Copy was taken, the
rollback process will not affect the new size.
•
When rolling back from an online Virtual Copy, both datafile and archive log virtual volumes
are rolled back by default. Use the -o option to rollback only datafile virtual volumes or only
archive log virtual volumes.
•
When rolling back from an offline or datafile Virtual Copy, only datafile virtual volumes are
rolled back.
•
When rolling back from an archive log Virtual Copy, only archive log virtual volumes are
rolled back.
The following restrictions apply when rolling back a Virtual Copy:
•
The online redo logs and control file should not reside on the same virtual volumes used by
the datafiles and archive logs. Otherwise, they will be rolled back along with the datafile and
archive log virtual volumes.
•
The database instance must be CLOSED for this operation. If the database is an RAC database,
all RAC instances must be CLOSED.
•
The base (datafile and/or archive log) virtual volumes must be temporarily removed from the
original database server.
NOTE: For detailed instructions and examples for using the rollback utility, see “Using the Recovery
Manager Rollback Utility” (page 100) .
Recovery Manager for Oracle saves an ascii control file and a binary control file for each created
Virtual Copy in its repository. After a rollback, you may need to restore the control file in order to
perform database recovery.
Recovery Manager for Oracle and Third-Party Backup Tools
HP 3PAR Recovery Manager Software for Oracle integrates HP 3PAR Virtual Copy Software with
Symantec NetBackup (NBU) and/or Oracle RMAN to perform off-host backup. Off-host backups
can dramatically reduce performance impact on the database server and minimize database down
time or database in backup mode during backup.
Recovery Manager for Oracle creates a Virtual Copy (snapshot) of the database, mounts it to the
backup server, then performs backup of the Virtual Copy.
Recovery Manager for Oracle supports online (hot), offline (cold), datafile, or archive log backups.
•
Online backup - A database backup while it is OPEN.
•
Offline backup - A database backup while it is CLOSED.
Database Rollback from a Virtual Copy 17