Veritas Storage Foundation™ for Oracle 5.0.1 Administrator's Guide

■ Storage must be configured properly.
See “Hosts and storage for Database FlashSnap ” on page 229.
■ You must be the Oracle database administrator.
■ The disk group must be version 110 or later. For more information
on disk group versions, see the vxdg(1M) manual page.
■ Be sure that a DCO and DCO volume are associated with the volume
for which you are creating the snapshot.
■ Snapshot plexes and their associated DCO logs should be on
different disks than the original plexes, and should be configured
correctly for creating snapshots by the system administrator.
■ Persistent FastResync must be enabled on the existing database
volumes and disks must be assigned for the snapshot volumes.
■ The database must be running in archive log mode. Archive log
mode is set in the Oracle initialization parameter file (init.ora).
■ The Oracle database must have at least one mandatory archive
destination.
See “Establishing a mandatory archive destination” on page 262.
■ ORACLE_HOME cannot reside on disk which will be used for
snapshot.
Prerequisites
■ The snapplan can be created on the master or slave node.
■ After creating the snapplan using the dbed_vmchecksnap
command, you can use a text editor to review and update the file,
if necessary.
■ It is recommended that you create a local working directory to
store your snapplans in.
■ See the dbed_vmchecksnap(1M) online manual page for more
information.
■ If the SNAPSHOT_MODE for the database is set to online, the
primary and secondary hosts can be the same. If the
SNAPSHOT_MODE is set to offline or instant, the primary and
secondary hosts must be different.
Usage notes
257Using Database FlashSnap for backup and off-host processing
Creating a snapplan (dbed_vmchecksnap)