Through networking programs like MS Exchange Server, an individual at shops, offices etc can either send or read emails. With the help of email system several users get connected through Microsoft Exchange Server. It provides several facilities like instant messaging, emailing, calendaring, task scheduling etc. Exchange databases or EDB folders is the place where MS Exchange Server saves users email records. Transaction logs, EDB and Checkpoint files are in all EDB files. Primary Exchange database is another name given to EDB file. Based on Exchange Server, it is important for smooth functioning of email system. But, there are several factors that affect smooth functioning of MS Exchange Server and they are mentioned below:

€ Non-functioning or corrupted computer drive
€ Mailbox store is oversize
€ Malicious codes installation
€ Unexpected System shutdown and many more
€ Internet connectivity slow
€ Twisted or broken LAN cable
€ MS Exchange Server crashed

Exchange database corruption due to several reason cripple emailing services on network of MS Exchange. Synchronization failure is the result of most Exchange corruption along with client server and crashed Jet Engine database.

Manual Recovery Options:

MS Exchange Server has two inbuilt diagnostic and recovery tools i.e. Eseutil.exe and Isinteg.exe. provided by Microsoft. Both of these contain set of commands that will be able troubleshoot all issues of Exchange database corruption. The dual database recovery switches is being offered by Eseutil tool:

1. Eseutil/R: This is known to be the Eseutil soft recovery option. When EDB file has minor issue or only some Exchange database files of a Server have been damaged then this is used.

2. Eseutil/P: This is known to the Eseutil hard recovery option. Major Exchange corruption such as Exchange disasters can be troubleshooted. Sometimes, user loses important data of EDB files which can be repaired.

Before using Eseutil recovery command first check the EDB file status i.e., either it is mounted on the Exchange Server or switched in offline mode:

Eseutil/mh €:C:\Program files\Exchsrvr\MDBData\Primary name.EDB€

When the above command returns €Dirty Shutdown€ state occurs which means that the EDB file has switched in offline mode and require to repair using Eseutil/R command as shown below:

Eseutil/R €:C:\Program files\Exchsrvr\MDBData\Primary name.EDB€

If you cannot do with EDB corruption with Eseutil/R then make use of Eseutil hard recovery option as shown below:

Eseutil/P €:C:\Program files\Exchsrvr\MDBData\Primary name.EDB€

When the EDB file is recovered i.e., Priv1.EDB or Pub1.EDB then then you require to compact repair file using Eseutil/D command:

Eseutil/D €:C:\Program files\Exchsrvr\MDBData\Primary name.EDB€

Now the next step is to check all Exchange mailbox stores consistency of MS Exchange Server using Isinteg command:

Isinteg- s (Name of Exchange Server)- fix- test all tests

Until MS Exchange Server does not show zero error, you need to use Isinteg command repeatedly. You need to mount the repaired mailbox store or Public store on Exchange Server that uses Exchange Management Shell or Exchange Management Console after the successful execution of Eseutil and Isinteg commands. The following limitation is present in Exchange Diagnostic and recovery tools:

Both Eseutil and Isinteg work on offline EDB files only.
For recovering large Exchange databases, considerable time is required.
Many critical Exchange corruption issues is been fail to fixed.

EDB to PST conversion tool:

In order to recover your corrupt Exchange databases from the latest backup folder or using a third party EDB to PST tool, this is the best option. From internet, you are able to find many EDB to PST tools that can recover perfectly inaccessible public stores or mailbox stores of an organization. Thus, EDB Repair Tool is the efficient software that can restore inaccessible EDB files to PST format. It can retrieve huge information of Exchange mailbox from the damaged EDB files successfully.