Veritas Storage Foundation™ for Oracle 5.0.1 Administrator's Guide

Reverse resychronization is aborted on the primary host.
$ /opt/VRTS/bin/dbed_vmsnap -S PROD -f snap1 \
-o reverse_resync_abort
dbed_vmsnap started at 2004-04-02 16:16:44
The option reverse_resync_abort has been completed.
dbed_vmsnap ended at 2004-04-02 16:16:51
Reverse resychronization changes are committed on the primary host.
$ dbed_vmsnap -S FLAS10r1 -f snaptst
-o reverse_resync_commit
$ dbed_vmsnap -S FLAS10r1 -f snaptst -o reverse_resync_commit
dbed_vmsnap started at 2009-07-30 14:14:47
Oracle instance FLAS10r1 successfully started.
The database is not running in archivelog mode.
SFORA dbed_vmsnap WARNING V-81-5725 After reverse_resync_commit is performed,
you need to recreate the Authentication Password
File using the ORAPWD utility.
The option reverse_resync_commit has been completed.
dbed_vmsnap ended at 2009-07-30 14:20:07
Resynchronizing the snapshot to your database
When you have finished using a clone database or want to refresh it, you can
resynchronize it with the original database. This is also known as refreshing the
snapshot volume or merging the split snapshot image back to the current database
image. After resynchronizing, the snapshot can be retaken for backup or
decision-support purposes.
There are two choices when resynchronizing the data in a volume:
■ Resynchronizing the snapshot from the original volume.
■ Resynchronizing the original volume from the snapshot. This choice is known
as reverse resynchronization. Reverse resynchronization may be necessary
to restore a corrupted database and is usually much quicker than using
alternative approaches such as full restoration from backup media.
Reverse resynchronization is not supported in Oracle RAC configurations.
Before resynchroninzing the snapshot to your database, make sure the following
conditions are met:
Using Database FlashSnap for backup and off-host processing
Resynchronizing the snapshot to your database
290