Veritas Storage Foundation 5.1 SP1: Storage and Availability Management for Oracle (5900-1504, April 2011)

ORACLE_SID=slave
ARCHIVELOG_DEST=/oraarch1_1/slave
SNAPSHOT_ARCHIVE_LOG=yes
SNAPSHOT_MODE=online
SNAPSHOT_PLAN_FOR=database
SNAPSHOT_PLEX_TAG=dbed_flashsnap
SNAPSHOT_DG_PREFIX=SNAP_
SNAPSHOT_VOL_PREFIX=SNAP_
ALLOW_REVERSE_RESYNC=no
SNAPSHOT_MIRROR=1
archdg1:arch1vol1=
datadg1:data1vol2=
datadg1:data1vol1=
datadg2:data1vol1=
datadg2:data1vol2=
Edit the snapplan and add the mountpoints to the dg:volume pairs before you
validate the snapplan. The mountpoints entered would be the location where the
clone database would be mounted after a dbed_vmclonedb operation.
Creating multi-mirror snapshots
To make the Database Snapshots highly available, the snapped snapshot volume
should contain more than one mirror. This makes the snapshot volumes available
even if one of the mirrors becomes disabled. Snapshot volumes can be mounted
and the entire database snapshot is usable even if one of the mirrors becomes
disabled. The multi-mirror snapshots are enabled by SNAPSHOT_MIRROR=<n> in
the snapplan.
Note: There are no changes to the command-line usage or arguments for the
Flashsnap tools.
Before taking the snapshot, make sure all tagged snapshot mirrors are in
SNAPDONE state.
For information about snapshot mirrors, refer to the Veritas Volume Manager
Administrator's Guide.
Validating a snapplan (dbed_vmchecksnap)
After creating a snapplan, the next steps are to validate the snapplan parameters
and check whether the snapshot volumes have been configured correctly for
creating snapshots. If validation is successful, the snapplan is copied to the
167Using Database FlashSnap for backup and off-host processing
FlashSnap commands