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.
Click the thumbnail above to view full-sized image.
Example system configuration for database backup on the primary hostExample system configuration for database backup on a secondary host,shows a typical configuration when snapshot volumes are used on a secondary host.
Click the thumbnail above to view full-sized image. 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 hostdbed_vmclonedb
command.
dbed_vmclonedb
command, you must complete the steps in Summary of database snapshot steps, Validating a snapplan (dbed_vmchecksnap), and Creating a snapshot (dbed_vmsnap.
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.
dbed_vmclonedb
command can be used on the secondary host.
-r relocate_path
is required.
SFDBvol=
vol_name
option is required.
SNAPSHOT_MODE
is set to offline
or instant
, a two-host configuration is required and -r
relocate_path
is not allowed.
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.