Veritas Storage Foundation™ for Oracle 5.0.1 Administrator's Guide

■ You must be logged in as the Oracle database administrator.
■ Before you can resynchronize the snapshot image, you must
validate a snapplan and create the snapshot.
See “Summary of database snapshot steps” on page 249.
See “Validating a snapplan (dbed_vmchecksnap)” on page 263.
See “Creating a snapshot (dbed_vmsnap)” on page 270.
■ If a clone database has been created, shut it down and unmount
the file systems using the dbed_vmclonedb -o
umountcommand. This command also deports the disk group.
See “Shutting down the clone database and unmounting file
systems” on page 284.
Prerequisites
■ The dbed_vmsnap command can only be executed on the primary
host or if in an Oracle RAC configuration, on the CVM master node
or slave 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 FLAS11r1 -f snap1 -o resync
dbed_vmsnap started at 2009-06-29 06:41:35
Snapback Volumes OK for flashdstdg15
The option resync has been completed.
dbed_vmsnap ended at 2009-06-29 06:44:45
Now you can again start creating snapshots.
291Using Database FlashSnap for backup and off-host processing
Resynchronizing the snapshot to your database