Table of ContentsLibraryView in Frames

When to verify the databases in a backup set

You can verify the databases in your SnapManager backup sets immediately after creation, at a scheduled time later, or when you restore them.

By default, SnapManager automatically verifies full backup sets at the time the backup is created. This is simple and ensures that each database in the backup set is verified. However, this method significantly increases the time required to complete the backup.

You can start an operation to verify the databases contained in one or more backup sets that have already been created. You can start the verification immediately, or you can schedule the verification to occur later, when it does not affect performance or delay later backups.

If you attempt to restore from a backup set on which a database consistency check has not been run successfully, SnapManager prompts (but does not require) you to first verify the databases in that backup set.

Note: When you perform verification on a LUN clone, and you make a Snapshot copy of the volume while a LUN clone exists, a “busy Snapshot copy” is created, which might cause problems when you attempt to delete Snapshot copies. To avoid this, do not schedule backups while a verification is in progress, to enable the use of FlexClone for Snapshot copy access. If the FlexClone volume is licensed on the storage system, it is used without SnapMirror verification.
Related concepts
Database backup using SnapManager
Backup database verification