Exchange Server is used extensively across the globe for the world-class services it has to offer. Microsoft offers an easy to use and ideal email environment for the corporate users so that they can carry on with the communication effortlessly. Exchange Server comprises of Information Store; this acts as the most important part of MS Exchange Server. Therefore, in any case of corruption in Exchange Server, Information Store is also affected.

Let’s talk about Information Store first; it expands over four different kinds of database files which are Priv1.edb, Priv1.stm, Pub1.edb and Pub1.stm. Like other database files, these files too are prone to corruption situations. When corruption issues strike Priv1.edb or Pub1.edb then Exchange administrator will experience a number of symptoms and MS Exchange Information Store service will stop or would decline to initiate.

With information store failing to start and allowing you to access the data stored in these files. Consequently, the Exchange users find it difficult to continue their communication. MS Exchange Server displays a number of error messages that limit the user to send or receive emails.

However, you can avoid this havoc situation if you have a latest database backup available with you. Usually, administrators in the workplaces keep updating the backups of the Exchange databases in-lieu of these databases. But if you are left with no available backup then the administrator must immediately use the available Exchange recovery solutions to recover Exchange databases. Consider a real-time workplace situation, where you try mounting the mailbox store in Exchange Server and come across the following error message:

“Unable to Mount the Mailbox Store with error c104173c The Information Store is Busy”

The above-mentioned error message appears when there is possible corruption in one or both EDB database files which are Priv1.edb and Pub1.edb of information store. In order to perform Exchange recovery, follow these steps to ensure your EDB databases are safe:

Run eseutil/mh command to make sure that the database is in consistent state or not.

1. If the result is displayed as ‘Clean Shutdown’ then remove all the log files from Exchsvrmbddata folder

2. If the result is displayed as ‘Dirty Shutdown’, then run eseutil/r command to perform soft recovery

3. If the database fails to come to the consistent state, then run eseutil/p command to perform hard recovery to recover Exchange

Corruption in EDB database files can be resolved easily with the above mentioned commands. However, at times data in Exchange Server database files might display messages that show messages that were in log files and are not related to Information Store database.

In a situation of corruption, use of third party Exchange Recovery software is ideal as it helps you to recover Exchange databases in even the most severe situations of corruption. In such a situation use Kernel for Exchange Server repair utility to help you perform Exchange recovery from corrupt EDB database safely so that it comes into a consistent state. Owing to the robust scanning algorithms of this software, you can Recover Exchange data that became inaccessible effortlessly.