HP 3PAR Recovery Manager 4.5.0 for Oracle on Solaris, Red Hat Linux, and Oracle Enterprise Linux User's Guide (QL226-97705, May 2014)

6 Using the Recovery Manager Rollback Utility
Recovery Manager for Oracle provides a way to rollback a database to a point-in-time image by
promoting a read-only or read-write Virtual Copy back to the base (database) virtual volumes.
The base (database) virtual volume must not be exported to any host during the rollback process.
In other words, the database LUNs of the corresponding database virtual volumes must be removed
from the database server prior to the rollback process. Once the rollback process completes, the
database LUNs can be exported back to the database server. If base volumes are to be rolled
back using read-write virtual copies, the read-write virtual copy can not be exported to any host
during rollback process. The database LUNs of the corresponding clone database read-write virtual
copy volumes must be removed from the backup server prior to the rollback process. After the
rollback process is completed, if needed, the clone database LUNs can be exported back to the
backup server.
NOTE: When using rollback utility with Remote Copy configuration. The Virtual Copy will rollback
on the secondary HP 3PAR StoreServ Storage system. The Remote Copy group that contains the
related volumes must be stopped before running the rmora_rollback with -f option.
Refer to the HP 3PAR Remote Copy Software User’s Guide to reverse the Remote Copy configuration.
If a Virtual Copy is a standby database, the base virtual volumes of the standby database (not the
primary database) is rolled back.
rmora_rollback Usage
Refer to “rmora_rollback” (page 96) for the syntax and available options for the
rmora_rollback command.
Syntax: rmora_rollback -s <oracle_sid> -p <primary_host> -t <timestamp>
[-o data|arch] [-v] [-w] [-f]
The purpose of this procedure is to rollback the database base volumes to the point in time when
the Virtual Copy was taken.
Rollback Using a Database Read-Only Virtual Copy
1. From the database server, shutdown the database. If the database is a Real Application
Clusters (RAC) database, all RAC instances must be shutdown.
2. From the database server, unmount all database file systems if they are on file systems.
Example:
# umount /oradata
3. From the database server, drop the database ASM disk groups if ASM is in use.
Example:
SQL>drop diskgroup <disk_group> including contents;
rmora_rollback Usage 117