Rollback using a database read-write virtual copy – HP 3PAR Application Software Suite for Oracle User Manual
Page 116
Rollback Using a Database Read-Write Virtual Copy
The steps to rollback from a read-write Virtual Copy are the similar to rollback from a read-only
Virtual Copy. First, perform step 1 to 6 from the section
“Rollback Using a Database Read-Only
on the database server for the primary database. Then perform the
following steps:
1.
On the backup server, if a clone database is created, shutdown the database. If the clone
instance is part of a Real Application Clusters (RAC) database, all RAC instances must be
shutdown.
2.
On the backup server, unmount all file systems which are mounted using the read-write virtual
copy volumes.
Example for systems with VxFS:
# umount /oradata
3.
On the backup server, unmount the ASM diskgroups contained in the read-write virtual copy
volumes if ASM is in use.
Example:
SQL> alter diskgroup dgname dismount;
4.
On the backup server, deport the VxVM disk groups contained in the read-write virtual copy
volume if Symantec VxVM is in use
Example:
# vxdg deport <diskgroup>
5.
On the HP 3PAR StoreServ Storage system, remove the VLUNs for the read-write virtual copy
volumes.
Example:
cli>removevlun sol0000000_rw_082312134324 101 pilot
6.
Keep the list of the VLUNs which are removed by the removevlun command. The cloned
database virtual volumes need to be exported to the same VLUNs on the backup server, if
needed.
7.
Perform rollback from the database read-write Virtual Copy from the backup server.
Example:
# rmora_rollback -s TEST920 -p pilot -t 042903142921 -w -v
After the above rmora_rollback operation, perform step 8 to step 12 from the database
server as described in section
“Rollback Using a Database Read-Only Virtual Copy” (page
for the primary database. Then, perform following steps:
8.
On the HP 3PAR StoreServ Storage system, if needed, export the read-write virtual copy
volumes back to the backup server with the same VLUNs saved in step 6.
Example:
cli>createvlun sol0000000_rw_082312134324 101 pilot
9.
On the backup server, if needed, import VxVM disk groups contained in the read-write virtual
copy volumes and start all VxVM volumes if Symantec VxVM is in use.
Example:
# vxdg import <diskgroup>
# vxvol -g <diskgroup> startall
116
Using the Recovery Manager Rollback Utility