Veritas Storage Foundation™ 5.0.1 for Oracle RAC Installation, Configuration, and Administrator's Guide Extracts for the HP Serviceguard Storage Management Suite on HP-UX 11i v3

If -r is used in dbed_vmclonedb, make sure
is created and owned by Oracle DBA. Otherwise,
the following mount points need to be created and owned by
Oracle DBA:
/prod_db.
/prod_ar.
dbed_vmsnap ended at 2006-03-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 2005-03-02 23:01:10
VxDBA 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.
VxDBA repository volume is SNAP_arch.
If -r is used in dbed_vmclonedb, make sure
is created and owned by Oracle DBA. Otherwise,
the following mount points need to be created and owned by
Oracle DBA:
/prod_db.
/prod_ar.
dbed_vmsnap ended at 2005-03-02 23:02:58
Backing Up the Database from Snapshot Volumes (dbed_vmclonedb)
Snapshots are most commonly used as a source for backing up a database. The advantage of
using snapshot volumes is that the backup will not contest the I/O bandwidth of the physical
devices. Making the snapshot volumes available on a secondary host will eliminate the extra
loads put on processors and I/O adapters by the backup process on the primary host.
A clone database can also serve as a valid backup of the primary database. You can back up the
primary database to tape using snapshot volumes.
Figure 5-5 shows a typical configuration when snapshot volumes are located on the primary
host.
Figure 5-5 Example System Configuration for Database Backup on the Primary Host
74 Using FlashSnap for Backup and Recovery