Microsoft Exchange Server databases suffer from two type of inconsistencies: Logical and Physical. Logical database corruption is caused due to reasons like deletion of Edb.log file and write-back caching, which generally introduce errors in B-trees and other logical structures. On the other hand, physical database corruption root from hardware failure like reasons that usually affect the database pages. Logical database corruption is hard to be detected by database administrator when compared to physical database corruption. However, at times when Exchange Server tries to read data from a corrupted database, it reports an error (as mentioned further). The corruption can be logical or physical and you need to apply EDB Recovery techniques to solve these problems.

As an instance, you might receive the below error message with your Exchange Server database:

“msgidJetDatabaseCorrupted.”...