Veritas Storage Foundation for Oracle 5.0 Administrator's Guide, HP-UX 11i v3, Second Edition, December 2008

■ The dbed_vmsnap command can only be executed on the primary
host, or if in an Oracle RAC configurration, on the CVM master
node.
■ In a two-host configuration, the dbed_vmsnap command imports
the disk group that was deported from the secondary host and
joins the disk group back to the original disk group. The snapshot
volumes again become plexes of the original volumes. The snapshot
is then resynchronized.
Two-host operations are not applicable to Oracle RAC
configurations.
■ See the dbed_vmsnap(1M) manual page for more information.
■ As a good practice, it is recommended to remove the old archive
logs after performing a reverse resynchronization.
Usage notes
To resynchronize the snapshot image
◆
Use the dbed_vmsnap command as follows:
$ /opt/VRTS/bin/dbed_vmsnap -S ORACLE_SID -f SNAPPLAN -o resync
In this example, the snapshot image is resynchronized with the primary database.
$ /opt/VRTS/bin/dbed_vmsnap -S PROD -f snap1 -o resync
Now you can again start creating snapshots.
Removing a snapshot volume
If a snapshot volume is no longer needed, you can remove it and free up the disk
space for other uses by using the vxedit rm command.
■ You must be logged in as root.
■ If the volume is on a mounted file system, you must unmount it
before removing the volume.
Prerequisites
To remove a snapplan and snapshot volume
1
To remove the snapshot and free up the storage used by it:
If the snapshot has been taken:
■ Remove the snapshot as follows:
# vxsnap -g diskgroup dis snapshot_volume
# vxvol -g diskgroup stop snapshot_volume
# vxedit -g diskgroup -rf rm snapshot_volume
Using Database FlashSnap for backup and off-host processing
Removing a snapshot volume
280