Backing up the database from snapshot volumes (dbed

Backing up the database from snapshot volumes (dbed_vmclonedb)

Prev	Using FlashSnap for backup and recovery	Next

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.

Example system configuration for database backup on the primary host shows a typical configuration when snapshot volumes are located on the primary host.

Example system configuration for database backup on the primary host

Click the thumbnail above to view full-sized image.

Example system configuration for database backup on a secondary host shows a typical configuration when snapshot volumes are used on a secondary host.

Example system configuration for database backup on a secondary host

Click the thumbnail above to view full-sized image.

Prerequisites

You must be logged in as the Oracle database administrator to use dbed_vmclonedb command.
Before you can use the dbed_vmclonedb command, you must validate a snapplan and create a snapshot.
See Summary of database snapshot steps

See Validating a snapplan (dbed_vmchecksnap)

See Creating a snapshot (dbed_vmsnap)
The volume snapshot must contain the entire database.
Before you can use the dbed_vmclonedb command with the -r relocate_path option (which specifies the initial mount point for the snapshot image), the system administrator must create the mount point and then change the owner to the Oracle database administrator.

Usage Notes

The dbed_vmclonedb command can be used on the secondary host.
In a single-host configuration, the primary and secondary hosts are the same.
In a single-host configuration, -r relocate_path is required.
In a node in the cluster configuration, the sfdbvol=vol_name option is required.
If SNAPSHOT_MODE is set to offline or instant, a two-host configuration is required and -r relocate_path is not allowed.
See the dbed_vmclonedb(1M) manual page for more information.

Note You cannot access Database FlashSnap commands (dbed_vmchecksnap, dbed_vmsnap, and dbed_vmclonedb) with the SFDB menu utility.

Prev	Up	Next
Creating a snapshot (dbed_vmsnap)	Home	Mounting the snapshot volumes and backing up