Backing up the database from snapshot volumes (db2ed_vmclonedb)
Prev Using Database FlashSnap for backup and off-host processing Next

Backing up the database from snapshot volumes (db2ed_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 datafiles to tape using snapshot volumes. You can also use the DB2 Backup utility to backup a snapshot database if all the tablespaces are DMS type.

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

Figure: Example system configuration for database backup on the primary host

Example system configuration for database backup on the primary host

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

Figure: Example system configuration for database backup on a secondary host

Example system configuration for database backup on a secondary host

Prerequisites

  • You must be logged in as the DB2 instance owner to use db2ed_vmclonedb command.

  • Before you can use the db2ed_vmclonedb command, you must create and validate a snapplan, and create a snapshot.

    See Summary of database snapshot steps.

    See Validating a snapplan (db2ed_vmchecksnap).

    See Creating a snapshot (db2ed_vmsnap).

  • The volume snapshot must contain the entire database.

  • Before you can use the db2ed_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 DB2 instance owner.

  • The SNAPSHOT_MODE must be online_snapshot or offline. If SNAPSHOT_MODE is set to offline, a two-host configuration is required.

Usage notes

  • The db2ed_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.

  • See the db2ed_vmclonedb(1M) manual page for more information.
Prev Up Next
Creating a snapshot (db2ed_vmsnap) Home Mounting the snapshot volumes and backing up