VERITAS Storage Foundation 4.1 Oracle Administrator's Guide

Chapter 10, Using Database FlashSnap for Backup and Off-Host Processing
Prerelease 8 September 2005, 8:55am Validating a Snapplan (dbed_vmchecksnap)
227
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 repository. The snapplan is validated using the
dbed_vmchecksnap command with the -o validate option.
Prerequisites
◆ The database must be up and running while executing the dbed_vmchecksnap command.
Usage Notes
◆ The dbed_vmchecksnap command must be run as the Oracle database administrator.
◆ After validating the snapplan, you have the option of modifying the snapplan file to meet your
storage configuration requirements.
◆ When using dbed_vmchecksnap to validate the snapplan and storage, you can save the
validation output. The system administrator can use this information to adjust the storage setup
if the validation fails.
◆ If a snapplan is updated or modified, you must re-validate it. It is recommended that snapplans
are revalidated when changes are made in the database disk group.
◆ The dbed_vmchecksnap command can be used on the primary or secondary host.
◆ See the dbed_vmchecksnap(1M) manual page for more information.
▼ To validate a snapplan
1. Change directories to the working directory your snapplan is stored in:
$ cd /working_directory
2. Validate the snapplan using the dbed_vmchecksnap command:
$ /opt/VRTS/bin/dbed_vmchecksnap -S ORACLE_SID \
-H ORACLE_HOME -f SNAPPLAN -o validate
Note In HA environment, you must modify the default snapplan, use the virtual host name defined
for the resource group for the PRIMARY_HOST and/or SECONDARY_HOST, and run
validation.
For information on validating a snapplan using the GUI, see “Validating or Modifying a Snapplan”
on page 309.