< Previous  | TOC | Index | Next  >

Shutting Down the Clone Database and Unmounting File Systems

When you are done using the clone database, you can shut it down and unmount all snapshot file systems with the dbed_vmclonedb -o umount command. If the clone database is used on a secondary host that has shared disks with the primary host, the -o umount option also deports the snapshot disk group.

  Note   Any mounted Storage Checkpoints mounted need to be unmounted before running dbed_vmclonedb -o umount.

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

Use the dbed_vmclonedb command as follows:

$ /opt/VRTS/bin/dbed_vmclonedb -o umount,new_sid=new_sid \

-f SNAPPLAN [-r relocate_path]

Example

In this example, the clone database is shut down and file systems are unmounted for a clone on the same host as the primary database (a single-host configuration).

$ /opt/VRTS/bin/dbed_vmclonedb -o umount,new_sid=NEWPROD \

-f snap1 -r /clone

dbed_vmclonedb started at 2004-04-02 15:11:22

NOTICE: Umounting /clone/prod_db.

NOTICE: Umounting /clone/prod_ar.

dbed_vmclonedb ended at 2004-04-02 15:11:47

Example

In this example, the clone database is shut down, file systems are unmounted, and the snapshot disk group is deported for a clone on a secondary host (a two-host configuration).

$ /opt/VRTS/bin/dbed_vmclonedb -o umount,new_sid=NEWPROD \

-f snap2

dbed_vmclonedb started at 2004-04-09 23:09:21

NOTICE: Umounting /clone/arch.

NOTICE: Umounting /clone/prod_db.

dbed_vmclonedb ended at 2004-04-09 23:09:50