VERITAS Storage Foundation 4.1 Oracle Administrator's Guide

Creating a Snapplan (dbed_vmchecksnap) Prerelease 8 September 2005, 8:55am
220 VERITAS Storage Foundation for Oracle Administrator’s Guide
Creating a Snapplan (dbed_vmchecksnap)
The dbed_vmchecksnap command creates a snapplan that dbed_vmsnap uses to create a
snapshot of an Oracle database. The snapplan specifies snapshot scenarios (such as online,
offline, or instant).
You can name a snapplan file whatever you choose. Each entry in the snapplan file is a line in
parameter=argument format.
When using dbed_vmchecksnap to create or validate a snapplan, the following parameters are
set:
Parameter Value
SNAPSHOT_VERSION Specifies the snapshot version for this major release of VERITAS
Storage Foundation for Oracle.
PRIMARY_HOST The name of the host where the primary database resides.
SECONDARY_HOST The name of the host where the database will be imported.
PRIMARY_DG The name of the VxVM disk group used by the primary database.
SNAPSHOT_DG The name of the disk group containing the snapshot volumes.
The snapshot volumes will be put into this disk group on the
primary host and deported. The secondary host will import this disk
group to start a clone database.
ORACLE_SID The name of the Oracle database. By default, the name of the Oracle
database is not included in the snapplan.
ARCHIVELOG_DEST The full path of the archive logs.
There are several archive log destinations that can be used for
database recovery if you are muliplexing the archive logs. You must
specify which archive log destination to use.
It is recommended that you have the archive log destination on a
separate volume if SNAPSHOT_ARCHIVE_LOG is yes.
SNAPSHOT_ARCHIVE_LOG yes or no
Specifies whether to create a snapshot of the archive log volumes.
Specify yes to split the archive log volume mirrors and deport
them to the secondary host. When using the Oracle remote archive
log destination feature to send the archive logs to the secondary
host, you can specify no to save some space.
Because the archive logs may not always be delivered to the
secondary host reliably, it is recommended that you specify yes.