Veritas Storage Foundation™ for Oracle 5.0.1 Administrator's Guide

To abort reverse resynchronization
◆
Use the -o reverse_resync_abort option of the dbed_vmsnap command:
$ /opt/VRTS/bin/dbed_vmsnap -S ORACLE_SID -f SNAPPLAN \
-o reverse_resync_abort
The -o reverse_resync_abort option aborts -o reverse_resync_begin,
unmounts the snapshot volumes, and mounts the original volumes back with
the file systems that are configured to use the volume. This operation is only
allowed after -o reverse_resync_begin has been executed and cannot be
used after reverse resynchronization has been committed (-o
reverse_resync_commit).
To commit reverse resynchronization changes
1
Use the -o reverse_resync_commit option of the dbed_vmsnap command:
$ /opt/VRTS/bin/dbed_vmsnap -S ORACLE_SID -f SNAPPLAN \
-o reverse_resync_commit
The -o reverse_resync_commit option commits the reverse
resynchronization changes after you have verified that they are acceptable.
The operation resynchronizes the original volume from the data in the
snapshot.
2
Restart the primary database in ARCHIVELOG mode so that it is ready to take
another snapshot.
If the Oracle authentication password file is used for the database, it needs
to be recreated using the ORAPWD utility after the reverse_resync_commit
operation is performed.
This example is valid only for the online_snapshot mode.
Reverse resynchronization is started on the primary host:
$ dbed_vmsnap -S FLAS10r1 -f snaptst
-o reverse_resync_begin
dbed_vmsnap started at 2009-07-30 14:06:38
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.
Database FLAS10r1 (SID=FLAS10r1) is running.
The option reverse_resync_begin has been completed.
dbed_vmsnap ended at 2009-07-30 14:12:22
289Using Database FlashSnap for backup and off-host processing
Resynchronizing your database to the snapshot