When corruption strikes Exchange Information stores, you may run across a range of problems while trying to access your database files. The Information store service may quit unexpectedly, the service may stop responding at startup, or you may lose your mailbox data. Logical corruption in Information stores may be triggered due to myriad reasons, such as transaction log files are missing or are corrupt, Information store database exceeds 16 GB, or an antivirus scan has damaged the store files. The following list describes the reasons responsible for causing logical corruption in Exchange databases:
Deletion of EDB.LOG file:
The ‘EDB.LOG’ file may contain some committed or uncommitted transactions. If this file is deleted, some changes will never be committed to the database. This may result in various problems, such as partially-moved messages or internal inconsistency in one or more B-trees. This may render your Exchange database logically corrupt
Write-back Caching:
Logical database corruption may also happen when you run an unprotected write-back cache against the log drive. If there is a power surge, the data in the unprotected write-back cache is erased. Usually, if the data is written to the log disk, Extensible Storage Engine commits the transaction and flushes the changes to the database page on the disk. If no data was written to the log disk, the database cannot be restored to its original state (the state before corruption) by the recovery process. In order to avoid this, you can protect your cache with a battery backup. You may also use some error corruption procedures.
Using ESEUTIL /P
The Eseutil /p command repairs the database by deleting some data and results in inefficient space usage in the database. To get rid of wasted space, you can perform offline defragmentation of the database using ‘ESEUTIL /D’. You should also run an integrity check against your database using ‘Isinteg -fix’. This will repair all the damages at the Store-level that were introduced by the repair process.
If your database gets logically corrupt due to any of the aforementioned reasons, you should take help of professional Exchange Server recovery software. These competent tools perform comprehensive scan of the corrupt Exchange database to recover all inaccessible user mailboxes. With the help of these utilities, you can repair and restore Unicode-formatted EDB files. In addition, they support close recovery of databases created in MS Exchange 2010, 2007, 2003, 2000 and 5.5![]()
Deletion of EDB.LOG file:
The ‘EDB.LOG’ file may contain some committed or uncommitted transactions. If this file is deleted, some changes will never be committed to the database. This may result in various problems, such as partially-moved messages or internal inconsistency in one or more B-trees. This may render your Exchange database logically corrupt
Write-back Caching:
Logical database corruption may also happen when you run an unprotected write-back cache against the log drive. If there is a power surge, the data in the unprotected write-back cache is erased. Usually, if the data is written to the log disk, Extensible Storage Engine commits the transaction and flushes the changes to the database page on the disk. If no data was written to the log disk, the database cannot be restored to its original state (the state before corruption) by the recovery process. In order to avoid this, you can protect your cache with a battery backup. You may also use some error corruption procedures.
Using ESEUTIL /P
The Eseutil /p command repairs the database by deleting some data and results in inefficient space usage in the database. To get rid of wasted space, you can perform offline defragmentation of the database using ‘ESEUTIL /D’. You should also run an integrity check against your database using ‘Isinteg -fix’. This will repair all the damages at the Store-level that were introduced by the repair process.
If your database gets logically corrupt due to any of the aforementioned reasons, you should take help of professional Exchange Server recovery software. These competent tools perform comprehensive scan of the corrupt Exchange database to recover all inaccessible user mailboxes. With the help of these utilities, you can repair and restore Unicode-formatted EDB files. In addition, they support close recovery of databases created in MS Exchange 2010, 2007, 2003, 2000 and 5.5
