Veritas Storage Foundation™ for Oracle 5.0.1 Administrator's Guide

Note: To force snapshot creation, use the -F option. The -F option can be used
after a snapshot operation has failed and the problem was fixed without using
Veritas Storage Foundation for Oracle commands. (That is, the volumes were
synchronized without using Veritas Storage Foundation for Oracle commands.)
In this situation, the status of the snapplan will appear as unavailable for creating
a snapshot. The -F option ignores the unavailable status, checks for the availability
of volumes, and creates the snapshot after the volumes pass the availability check.
After the snapshot is created, dbed_vmsnap returns values you will need to run
dbed_vmclonedb. These values include the snapshot disk group, the snapplan
name, and the primary database server name (server_name). Make a note of these
values so you have them when running dbed_vmclonedb. You can also use the
command dbed_vmchecksnap -f snapplan -o list to access the information
regarding the snapshot disk group.
The snapshot volumes now represent a consistent backup copy of the database.
You can back up the database by copying the snapshot volumes to tape or other
backup media.
See “Backing up the database from snapshot volumes (dbed_vmclonedb)”
on page 274.
You can also create another Oracle database for decision-support purposes.
See “Cloning a database (dbed_vmclonedb)” on page 278.
In this example, a snapshot image of the database, PROD, is created for a single-host
configuration (or for the RAC cluster, if in an Oracle RAC configuration). In this
case, the SECONDARY_HOST parameter is set the same as the PRIMARY_HOST
parameter in the snapplan.
$ /opt/VRTS/bin/dbed_vmsnap -S PROD -f snap1 -o snapshot
In case of single disk group environment:
dbed_vmsnap started at 2009-05-31 23:57:05
The database is running in archivelog mode.
A snapshot of ORACLE_SID FLAS10r2 is in DG SNAP_flashdg15.
Snapplan ofsnap4 is used for the snapshot.
Oracle Database server is dbhppa15.
.
If -r <relocate_path> is used in dbed_vmclonedb,
make sure relocate_path is created and owned by
Oracle DBA. Otherwise, the following mount points
need to be created and owned by Oracle DBA:
Using Database FlashSnap for backup and off-host processing
Creating a snapshot (dbed_vmsnap)
272