Database verification load management

If you run database verification on a production server, it can place a significant load on both the server and the storage systems. This degrades Exchange response, particularly during peak work hours. There are four methods to manage database verification load.

• Deferred database verification
  You can distribute your system workload by disabling automatic integrity verification, which takes place immediate after your backup is created, and then performing a separate verification later.
• Remote database verification
  You can distribute your system workload by disabling automatic integrity verification, which takes place immediate after your backup is created, and then run verification from another Exchange server.
• Verification throttling
  You can slow down the integrity verification to decrease the load on the Windows host and the storage systems by using verification throttling if you are using Microsoft Exchange Server 2003 SP2, or higher, or Microsoft Exchange Server 2007.
• Integrity verification on the destination SnapMirror volume
  SnapManager 5.0 and later supports integrity verification on the destination SnapMirror volume. SnapDrive uses FlexClone to access data in the Snapshot copy on destination SnapMirror volumes.