Validating a snapplan (dbed_vmchecksnap)
Prev Using Database FlashSnap for backup and off-host processing Next

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.

In Veritas Storage Foundation for Oracle RAC configurations, dbed_vmchecksnap with the -o validate option can be executed only on the VxVM CVM master node.

Consider the following prerequisites and notes before validating a snapplan:

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.

  • The default behavior is to force validation. Use the -n option if you want to skip validation.

  • After validating the snapplan, you have the option of modifying the snapplan file to meet your storage configuration requirements.

  • 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. In an Oracle RAC configuration both need to be specified as the host name of the CVM master node.

  • 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

    In an 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. In an Oracle RAC configuration both primary and secondary hosts need to be set to the host name of the CVM master node.

In the following example, a snapplan, snap1, is validated for a snapshot image in a single-host or Oracle RAC cluster configuration. The primary host is host1 and the working directory is /export/snap_dir.

$ cd /export/snap_dir 
$ /opt/VRTS/bin/dbed_vmchecksnap -S PROD -H /oracle/product/9i \
-f snap1 -o validate
PRIMARY_HOST is host1
SECONDARY_HOST is host1
The version of PRIMARY_DG-PRODdg is 140.
SNAPSHOT_DG is SNAP_PRODdg
SNAPSHOT_MODE is online
The database is running in archivelog mode.
ARCHIVELOG_DEST is /prod_ar
SNAPSHOT_PLAN_FOR is database
SNAPSHOT_ARCHIVE_LOG is yes
ARCHIVELOG_DEST=/prod_ar is mount on /dev/vx/dsk/PRODdg/prod_ar.
Examining Oracle volume and disk layout for snapshot
Volume prodvol1 on PRODdg is ready for snapshot. 
Original plex and DCO log for prodvol1 is on PRODdg1.
Snapshot plex and DCO log for prodvol2 is on PRODdg2.
Volume prodvol2 on PRODdg is ready for snapshot. 
Original plex and DCO log for prodvol2 is on PRODdg1.
Snapshot plex and DCO log for prodvol2 is on PRODdg2.
SNAP_PRODdg for snapshot will include: PRODdg2
ALLOW_REVERSE_RESYNC is NO
The snapplan snap1 has been created.

In the following example, a snapplan, snap2, is validated for a snapshot image in a two-host configuration. The primary host is host1, the secondary host is host2, and the working directory is /export/snap_dir. This example does not apply to Oracle RAC configurations.

$ cd /export/snap_dir
$ /opt/VRTS/bin/dbed_vmchecksnap -S PROD -H \
/oracle/product/9i -f snap2 -o validate

PRIMARY_HOST is host1 
SECONDARY_HOST is host2 
The version of PRIMARY_DG-PRODdg is 140. 
SNAPSHOT_DG is SNAP_PRODdg 
SNAPSHOT_MODE is online 
The database is running in archivelog mode. 
ARCHIVELOG_DEST is /mytest/arch 
SNAPSHOT_PLAN_FOR is database 
ARCHIVELOG_DEST=/mytest/arch is mount on /dev/vx/dsk/PRODdg/arch. 
Examining Oracle volume and disk layout for snapshot. 
Volume prodvol1 on PRODdg is ready for snapshot. 
Original plex and DCO log for arch is on PRODdg1. 
Snapshot plex and DCO log for arch is on PRODdg2. 
Volume prodvol2 on PRODdg is ready for snapshot. 
Original plex and DCO log for prod_db is on PRODdg1. 
Snapshot plex and DCO log for prod_db is on PRODdg2. 
SNAP_PRODdg for snapshot will include: PRODdg2 
ALLOW_REVERSE_RESYNC is NO 
The snapplan snap2 has been created.
Prev Up Next
Establishing a mandatory archive destination Home Displaying, copying, and removing a snapplan (dbed_vmchecksnap)