Creating or Shutting Down a Clone Database Using dbed_vmclonedb

You can use the VERITAS Storage Foundation for Oracle dbed_vmclonedb command to create or shutdown a clone database on either the primary or secondary host using snapshot volumes from the primary host.

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 complete the steps in Summary of Database Snapshot Steps, Validating a Snapplan (dbed_vmchecksnap), and Creating a Snapshot (dbed_vmsnap).
• The volume snapshot must contain the entire database.
• The system administrator must provide the database administrator with access to the necessary volumes and mount points.
• 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.
• If SNAPSHOT_MODE is set to offline or instant, a two-host configuration is required and -r relocate_path is not allowed.

Usage Notes

• The dbed_vmclonedb command can be used on the secondary host.
• In a single-host configuration, the primary and secondary hosts can be the same.
• In a single-host configuration, -r relocate_path is required.
• In a two-host configuration, the vxdbavol=vol_name option is required.
• Database FlashSnap commands are integrated with Storage Checkpoint functionality. It is possible to display and mount Storage Checkpoints carried over with snapshot volumes to a secondary host. However limitations apply. For details, see Mounting the Snapshot Volumes and Backing Up.
• See the dbed_vmclonedb(1M) manual page for more information.

Options

  To clone a database automatically

In a single-host configuration:

To create a clone of the primary database on the same host as the primary database, use the dbed_vmclonedb command as follows:

In a two-host configuration:

To create a clone of the primary database on a secondary host, use the dbed_vmclonedb command as follows:

  To clone a database manually

In a single-host configuration:

To mount file systems and create a clone of the primary database on the same host as the primary database without recovering the clone database, use the dbed_vmclonedb command as follows. The clone database must be manually recovered before it can be used:

Recover the database manually.

Update the snapshot status (database_recovered) for the clone database on the primary host after manual recovery has been completed:

In a two-host configuration:

To mount file systems and create a clone of the primary database on a secondary host without recovering the clone database, use the dbed_vmclonedb command as follows. The clone database must be manually recovered before it can be used:

Recover the database manually.

Update the snapshot status (database_recovered) for the clone database on the secondary host after manual recovery has been completed:

  To shut down the clone database and unmount all snapshot file systems

In a single-host configuration:

To shut down the clone database and unmount file systems for a clone on the same host as the primary database, use the dbed_vmclonedb command as follows:

In a two-host configuration:

To shut down the clone database, unmount file systems, and deport the snapshot disk group for a clone on a secondary host, use the dbed_vmclonedb command as follows:

  To restart a clone database

In a single-host configuration:

To start the clone database on the same host as the primary database, use the dbed_vmclonedb command as follows:

In a two-host configuration:

To start the clone database on the secondary host, use the dbed_vmclonedb command as follows: