Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007
Topic Last Modified: 2006-08-18

Exchange Server Database Utilities (Eseutil.exe) integrity mode is a reliable way to verify whether an Exchange Server database contains specific inconsistencies such as bad pages, inconsistent data, flipped bits, missing data, or other issues that could appear in a database. Using this tool to test database integrity is a safe approach because the check is performed in a read-only mode. It is important to detect specific types of anomalies or inconsistencies to take proper steps to fix the database. You should recover the database to a clean shutdown state before running an integrity check.

Many of the integrity checks involve reconstructing indexes and other data inside a temporary database. Then, a comparison is done between the two databases. If you do not have free disk space equivalent to 20 percent of the size of the files being checked, there is greater likelihood of running out of disk space during the check. You can add the T switch to the Eseutil /G command to redirect the scratchpad or temporary database to a drive with more space.

The Eseutil integrity mode does not perform a database recovery. If a database is inconsistent or is in a dirty shutdown state, we recommend that you perform a recovery operation to make sure that the database operations are completed correctly. After you perform the recovery operation, you can use the Eseutil tool to perform the integrity check.

For more information about performing an integrity check using Eseutil, see How to Run Eseutil /G (Integrity).

For More Information