The dbed_vmsnap
command creates a snapshot of an Oracle database by splitting the mirror volumes used by the database into a snapshot database. You can use the snapshot image on either the same host as the database or on a secondary host provided storage is shared by the two hosts.
The snapshot image created by dbed_vmsnap
is a frozen image of an Oracle database's datafiles. dbed_vmsnap
ensures that a backup control file is created when the snapshot database is created, which allows for complete data recovery, if needed.
For Database FlashSnap status information, see Veritas Storage Foundation for Oracle Administrator's Guide.
Note
You cannot access Database FlashSnap commands (dbed_vmchecksnap
, dbed_vmsnap
, and dbed_vmclonedb
) with the SFDB menu utility.
dbed_vmchecksnap
before you can create a snapshot image with dbed_vmsnap
.
dbed_vmsnap
command can only be used on the primary host.
$ORACLE_HOME/dbs
directory.
dbed_vmsnap
(1M) manual page for more information.
SNAPSHOT_MODE
is set to offline
in the snapplan, shut down the database.
$ /opt/VRTS/bin/dbed_vmsnap -S
ORACLE_SID -f
SNAPPLAN
\ -o snapshot
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 commands. (That is, the volumes were synchronized without using Veritas Storage Foundation 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.
Note
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 SFDB repository volume for a two-host configuration. 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 snapplan name, and the SFDB repository.
The snapshot volumes now represent a consistent backup copy of the database. You can backup the database by copying the snapshot volumes to tape or other backup media.
See Backing up the database from snapshot volumes (dbed_vmclonedb)
You can also create another Oracle database for decision-support purposes.
See Cloning a database (dbed_vmclonedb)
In this example, a snapshot image of the database, PROD
, is created for a single-host 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
dbed_vmsnap started at 2004-04-02 14:15:27
SFDB repository is up to date.
The database is running in archivelog mode.
A snapshot of ORACLE_SID PROD is in DG SNAP_PRODdg.
Snapplan snap1 is used for the snapshot.
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:
dbed_vmsnap ended at 2004-04-02 14:16:11
In this example, a snapshot image of the primary database, PROD
, is created for a two-host configuration. In this case, the SECONDARY_HOST
parameter specifies a different host name than the PRIMARY_HOST
parameter in the snapplan.
$ /opt/VRTS/bin/
dbed_vmsnap
-S PROD -f snap2 -o snapshot
dbed_vmsnap started at 2004-04-09 23:01:10
SFDB repository is up to date.
The database is running in archivelog mode.
A snapshot of ORACLE_SID PROD is in DG SNAP_PRODdg.
Snapplan snap2 is used for the snapshot.
SFDB repository volume is SNAP_arch.
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:
dbed_vmsnap ended at 2004-04-09 23:02:58