Table of ContentsLibraryView in Frames

Considerations for selecting the database verification server

You can manage verification your backup sets on either your production Exchange server or on a remote verification server, and you can use any of deferred verification, remote verification, and verification throttling to do so.

Verification of databases in a backup set can be done on the production Exchange server (the Windows host system running the Exchange server used to service the users) or on a remote verification system (a different Exchange server with Exchange management tools installed). Running database verification on a production Exchange server is CPU-intensive for the Windows host and also involves a substantial amount of activity on the storage system.

Note: When you change the database verification server, this change does not affect any database backup (with verification) or database verification-only jobs that are already scheduled. You must re-create the scheduled backup jobs for the change to apply.
SnapManager offers three methods for managing database verification load that you can use separately or in any combination:

Both the deferred verification and remote verification manage database verification load by separating database verification from the backup operation. Verification throttling manages database verification load by slowing down the verification throughput rate.

Related concepts
Database verification load management
How SnapManager checks database integrity in backup sets
Verification override entry in the SnapManager restore report
Related tasks
Selecting the Snapshot copy access method for database verification
Configuring database verification throttling