Home > Veritas Storage Foundation™ for Oracle Manual Pages
-o setdefaults[ ,validate ] -t [ -p plex_tag ] -t SECONDARY_HOST
dbed_vmchecksnap -S ORACLE_SID -H ORACLE_HOME -f SNAPPLAN
-o validate [ -n ]
dbed_vmchecksnap -S ORACLE_SID [ -f SNAPPLAN ] -o list
dbed_vmchecksnap -S ORACLE_SID -f SNAPPLAN -o copy | remove
lslpp -L VRTSdbed
When you first run dbed_vmchecksnap with the -o setdefaults option, the command creates a snapplan template with a number of variables. Some of the variables are assigned default values. You may edit the snapplan file manually to set the variables for different snapshot scenarios.
Use the -o validate option to check that the snapplan is correct and copy it to the repository. When used in an Oracle RAC database, the -o validate option must be run on the Veritas Cluster Volume Manager master node.
Snapshot plexes and their associated data change object (DCO) logs should be on different disks than the original plexes and must be configured correctly for creating snapshots by the system administrator. To verify that the plexes are configured correctly, run dbed_vmchecksnap with the -o validate option. For more information about snapshots and DCO logs, see the Veritas Volume Manager Administrator's Guide.
Use the -o list option to list all the snapplans associated with a specific ORACLE_SID.
Use the -o list -f SNAPPLAN options to get detailed information about the snapplan.
Use the -o copy | remove option to copy the snapplan from the Veritas Storage Foundation for Oracle repository to your local directory or remove the snapplan from the repository.
You can use Database FlashSnap commands in a high availability (HA) environment. See the NOTES section below for details.
$ /usr/bin/cd /export/snap_dir $ /opt/VRTS/bin/dbed_vmchecksnap -S PROD -H /oracle/product/9i -f snap2 -o setdefaults -t host2 Snapplan snap1 for PROD. ===================================================== SNAPSHOT_VERSION=5.0 PRIMARY_HOST=host1 SECONDARY_HOST=host2 PRIMARY_DG=PRODdg SNAPSHOT_DG=SNAP_PRODdg ORACLE_SID=PROD ARCHIVELOG_DEST=/mytest/arch SNAPSHOT_ARCHIVE_LOG=yes SNAPSHOT_MODE=online SNAPSHOT_PLAN_FOR=database SNAPSHOT_PLEX_TAG=dbed_flashsnap SNAPSHOT_VOL_PREFIX=SNAP_ ALLOW_REVERSE_RESYNC=no SNAPSHOT_MIRROR=1
In the following example, the snapplan, snap2, is validated for a snapshot image in a two-host configuration:
$ /usr/bin/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 SNAPSHOT_ARCHIVE_LOG is yes ARCHIVELOG_DEST=/mytest/arch is mount on /dev/vx/dsk/PRODdg/arch. Examining Oracle volume and disk layout for snapshot. Volume arch on PRODdg is ready for snapshot. Original plex and DCO log for arch is on PRODdg01. Snapshot plex and DCO log for arch is on PRODdg02. Volume prod_db on PRODdg is ready for snapshot. Original plex and DCO log for prod_db is on PRODdg01. Snapshot plex and DCO log for prod_db is on PRODdg04. SNAP_PRODdg for snapshot will include: PRODdg02 PRODdg04 ALLOW_REVERSE_RESYNC is yes The snapplan snap2 has been created.
In this example, all available snapplans are listed for the database PROD:
$ /opt/VRTS/bin/dbed_vmchecksnap -S PROD -o list The following snapplan(s) are available for PROD: SNAP_PLAN SNAP_STATUS DB_STATUS SNAP_READY snap1 init_full - yes snap2 init_full - yes
For descriptions of the statuses that appear for SNAP_STATUS and DB_STATUS, see the Veritas Storage Foundation for Oracle Database Administrator's Guide.
In this example, the snapplan, snap1, is displayed:
$ /opt/VRTS/bin/dbed_vmchecksnap -S PROD -f snap1 -o list SNAPSHOT_VERSION=5.0 PRIMARY_HOST=host1 SECONDARY_HOST=host1 PRIMARY_DG=PRODdg SNAPSHOT_DG=SNAP_PRODdg ORACLE_SID=PROD ARCHIVELOG_DEST=/prod_ar SNAPSHOT_ARCHIVE_LOG=yes SNAPSHOT_MODE=online SNAPSHOT_PLAN_FOR=database SNAPSHOT_PLEX_TAG=dbed_flashsnap SNAPSHOT_VOL_PREFIX=SNAP_ ALLOW_REVERSE_RESYNC=yes SNAPSHOT_MIRROR=1 STORAGE_INFO PRODdg02 SNAP_PLEX=prod_db-02 prod_ar-02 STATUS_INFO SNAP_STATUS=init_full
The dbed_vmchecksnap command runs without interaction from the user.
To take an online snapshot of the database, the database needs to be running in archive log mode, which is set in the Oracle initialization parameter file. To take an offline or instant snapshot, the primary and secondary hosts must be different.
It is recommended that you create a local working directory to store your snapplans in. If a snapplan is updated or modified, you must re-validate it.
You can use Database FlashSnap commands in a high availability (HA) environment. The following limitations apply:
- In an HA environment, you must modify the default snapplan to use the virtual host name defined for the database resource group for the PRIMARY_HOST and/or the SECONDARY_HOST parameters and validate the snapplan before creating the snapshot. The snapshot is created by running:dbed_vmsnap -S ORACLE_SID -f SNAPPLAN -o snapshot
- In an HA environment, the primary database must be down before you perform reverse resynchronization. When Veritas Cluster Server (VCS) detects that the primary database is down, however, it starts a failover process and the SFDB repository is unmounted and the dbed_vmsnap command is aborted. For more information and a workaround, see the dbed_vmsnap(1M) man page.
Veritas Storage Foundation for Oracle Administrator's Guide
Veritas Volume Manager Administrator's Guide Veritas Storage Foundation for Oracle RAC Installation and Configuration Guide ~
Last updated: 10 Apr 2006
Copyright ©2009 Symantec Corporation
All rights reserved.