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

4. From the database server, deport/export the database volume groups if volume groups are
in use.
Depends on volume groups involved, the deport/export volume group commands are slightly
different, the following are some of examples:
- For Symantec VxVM volume group, use the following command to deport the volume group:
# vxdg deport
Example :
# vxdg deport myvxvmdb_datadg
- For HP-UX logical volume groups, use the following command to deactivate and export volume group information
to a temporary file (the tmpfile will be used for later import):
# vgchange -a n
# vgexport -m
Example:
# vgchange -a n lvmtest_datadg
# /vgexport -m /tmp/lvmtest_datadg.map lvmtest_datadg
- For Linux logical volume groups, use the following command to deactivate logical volumes and export volume
groups:
# lvchange -an /dev/ /
# vgexport
Example:
# lvchange -an /dev/rh6lvm-data/lvol0
# lvchange -an /dev/rh6lvm-data/lvol1
# vgexport rh6lvm-datavg
5. From the HP 3PAR StoreServ Storage system, remove the VLUNs for the database virtual
volumes.
Example:
cli>removevlun Oracle_data1 101 pilot
6. Keep the list of the VLUNs, which are removed by the command . The database virtual volumes
need to be exported to the same VLUNs.
7. From the backup server, perform a rollback of the database virtual volumes using a database
read-only Virtual Copy.
Example:
# rmora_rollback -s TEST920 -p pilot -t 042903142921 -v
NOTE: Use with the -f option if the database virtual volumes are in Remote Copy groups.
The Remote Copy group which contains the virtual volumes must be stopped prior to the
rmora_rollback
operation.
8. On the HP 3PAR StoreServ Storage system, export the database volumes back to the database
server with the same VLUNs saved in step 6.
Example:
cli>createvlun Oracle_data1 101 pilot
118 Using the Recovery Manager Rollback Utility