< Previous  | TOC | Index | Next  >

Storage Checkpoints and Database FlashSnap

The following are limitations of Storage Checkpoints and Database FlashSnap:

• You cannot create a clone database using a mounted Storage Checkpoint.
• If you create an Oracle instance using the spfile option, you must run the dbed_update command before you can successfully perform any Storage Checkpoint or Database FlashSnap functions.
• Storage Checkpoints require file system layout version 6 or 7. Use the vxupgrade(1M) command to check the current layout version and to change the layout version if necessary. When upgrading a CFS file system, issue the command from the primary node.

  Note: After you upgrade a system to layout version 6 or 7, the file system is no longer compatible with older VxFS file systems.

• When cloning a database using Database FlashSnap, the Oracle database must have at least one mandatory archive destination. For more information about Oracle parameters for archiving redo logs, see your Oracle documentation.
• For an Oracle RAC database, the dbed_vmsnap, dbed_vmclonedb, and dbed_vmchecksnap commands must be run on the CVM master node. Also, only online snapshots are supported, which means the database instance should be up and running on the master node where validation is performed.
• After running dbed_vmsnap -o reverse_resync_commit, your primary database is started using a pfile. If your original primary database used an spfile, you need to shut down the database and restart it using the spfile. Then, run dbed_update to update the repository.
• The Storage Checkpoint and Database FlashSnap features of SF Oracle RAC do not support the GUI of the Veritas Storage Foundation for Oracle product.
• The Database FlashSnap feature does not support RAID-5 volumes.