Veritas Storage Foundation™ for Oracle 5.0.1 Administrator's Guide

■ You must be logged in as the Oracle database administrator.
■ Before you can reverse resynchronize the snapshot image, review
the database snapshot procedure and create the snapshot.
■ The mount point for the primary database must be created by and
owned by the Oracle DBA user before mounting the VxFS file
system.
■ If a clone database has been created, you must shut it down and
unmount the file systems using the dbed_vmclonedb -o umount
command before you can reverse resynchronize the snapshot
image. This command also deports the disk group if the primary
and secondary hosts are different.
See “Shutting down the clone database and unmounting file
systems” on page 284.
■ The primary database must be offline.
Prerequisites
■ The dbed_vmsnap command can only be executed on the primary
host.
■ Before you execute the reverse_resync_commit command, you
should remove the old archive log when ODM is enabled.
■ If the Oracle authentication password is used, you need to recreate
it using the ORAPWD utility after executing dbed_vmsnap -o
reverse_resync_commit.
Usage notes
To begin reverse resynchronization
◆
Use the -o reverse_resync_begin option to the dbed_vmsnap command:
$ /opt/VRTS/bin/dbed_vmsnap -S ORACLE_SID -f SNAPPLAN \
-o reverse_resync_begin
Any mounted storage checkpoints must be unmounted before running
dbed_vmsnap -o reverse_resync.
After executing reverse_resync_commit, checkpoints created on the original
database will be deleted.
The -o reverse_resync_begin option imports the disk group that was
deported from the secondary host and joins it back to the original disk group.
The command unmounts the original volumes, mounts the snapshot volumes
with the file systems that are configured for the primary database, and brings
up the database snapshot image as the primary database. This operation
requires the primary database to be offline so that its contents remain
unchanged.
Using Database FlashSnap for backup and off-host processing
Resynchronizing your database to the snapshot
288