Microsoft Exchange Server Information Store is comprised of four basic database files: Priv1.edb, Priv1.stm, Pub1.edb, and Pub1.stm. When the Information Store is corrupted, typically one or both of the EDB files, which are located in Program Files\Exchsrvr\Mdbdata folder, are involved. These database files comprise stored and in-process non-SMTP e-mails and thus their corruption leads to data unavailability for the users. To correct such instances of database corruption, an Exchange administrator requires applying an updated, healthy copy of affected database or otherwise, running edb recovery solutions.
An Exchange database corruption can be detected by different symptoms that server generates. For example, consider a scenario when an Exchange administrator accesses the Exchange System Manager and tries to mount the mailbox store. The administrator finds that it cannot complete the database mount operation and receives the below mentioned error message:
'Unable to Mount the Mailbox Store with error c104173c "The Information Store is Busy”'
This error is one among the clear indications that one or both of EDB database files is/are corrupted.
Pre-assuming few attributes like, single site and server issue, KM Manager not being used, and existence of an offline database backup (either on same drive or external storage media), following is the solution that can help you isolate database corruption:
Run eseutil /mh command to check the database consistency while making sure that Information Store service is not running.
If state of one or both of databases is dirty, replay the uncommitted transactions using soft recovery command- eseutil /r. In case, the command fails, you need to run hard database recovery using eseutil /p command, delete all the .chk and temp.edb files, run off line defragmentation with eseutil /d command, and then run Isinteg.exe utility.
If database(s) appear to be consistent and are still in unmountable state, you can run hard database recovery, as described above.
The Information Store databases should successfully mount if the above methods work. However, if they don't, you are suggested to opt for a third-party exchange recovery utility. An EDB Recovery tool can effectively scan a corrupted Exchange database and recover its contents in usable format.
Stellar Phoenix Mailbox Exchange Recovery is a reliable utility designed to repair corrupted EDB database files and extract their data in *.pst files. This exchange recovery utility supports MS Exchange Server 2007, 2003, 2000, and 5.5. With deleted mailbox recovery feature, the software allows you to perform recovery for only selective mailboxes.