VERITAS Storage Foundation 4.1 Oracle Administrator's Guide

Chapter 10, Using Database FlashSnap for Backup and Off-Host Processing
Prerelease 8 September 2005, 8:55am Cloning a Database (dbed_vmclonedb)
245
The snapshot status has been updated.
dbed_vmclonedb ended at 2004-04-09 23:34:35
▼ To clone the database automatically
Use the dbed_vmclonedb command as follows:
$ /opt/VRTS/bin/dbed_vmclonedb -S ORACLE_SID -g snap_dg \
-o recoverdb,new_sid=new_sid[,vxdbavol=vol_name] -f SNAPPLAN \
[-H ORACLE_HOME] [-r relocate_path]
Where:
◆ ORACLE_SID is the name of the Oracle database used to create the snapshot.
◆ snap_dg is the name of the diskgroup that contains all the snapshot volumes.
◆ new_sid specifies the ORACLE_SID for the clone database.
◆ vxdbavol is the volume that contains the snapplan data. This name is provided after you run
dbed_vmsnap -o snapshot.
◆ SNAPPLAN is the name of the snapplan file.
◆ ORACLE_HOME is the ORACLE_HOME setting for the ORACLE_SID database.
◆ relocate_path is the name of the initial mount point for the snapshot image.
Note When cloning a database on a secondary host, ensure that PRIMARY_HOST and
SECONDARY_HOST parameters in the snapplan file are different.
When the -o recoverdb option is used with dbed_vmclonedb, the clone database is
recovered automatically using all available archive logs. If the -o recoverdb option is not used,
you can perform point-in-time recovery manually.
For information on cloning a database using the GUI, see “Using the VERITAS Storage
Foundation for Oracle Graphical User Interface” on page 265.
Example
In the following example, a clone of the primary database is automatically created on the same host
as the primary database.
$ /opt/VRTS/bin/dbed_vmclonedb -S PROD -g SNAP_PRODdg \
-o recoverdb,new_sid=NEWPROD -f snap1 -r /clone
dbed_vmclonedb started at 2004-04-02 14:42:10
Mounting /clone/prod_db on /dev/vx/dsk/SNAP_PRODdg/SNAP_prod_db.
Mounting /clone/prod_ar on /dev/vx/dsk/SNAP_PRODdg/SNAP_prod_ar.
All redo-log files found.
Database NEWPROD (SID=NEWPROD) is running.
dbed_vmclonedb ended at 2004-04-02 14:43:05