Recover and Convert Exchange 2010 Mailbox to PST File Post Logical Corruption

Now since Exchange Server is becoming improved with every new edition and the hardware has become more fault tolerant, database corruption is a rare phenomenon to occur. Meanwhile, considering that Exchange DB can never fail to function is absolutely wrong. Database needs to managed on regular basis and if that is not done properly, possibility is that it can get corrupted. Exchange database is structured and divided into different Sections: Page Level, ESE Database Level, and Application Level.

Damage at Page Level (also known as Physical Corruption) is detectable at earlier stage and thus easy to fix. While ESE database and Application level damage (also known as Logical Corruption) is not easily detected as it is caused due to issues with Operating System or Exchange Server itself and so it gives a hard time to administrator to fix it. In the upcoming section of this article we will discuss about how to recover database from errors that are encountered due to logical corruption and how to fix them.

First of all, what is logical database corruption? Before understanding this concept, let us have a brief overview at the structure of Exchange DB. Basically, the database file (.edb) of Exchange® is a B-Tree structure that is based on the conception of data tree.

So, there are nodes that store data in it and the parent of all the nodes in the tree is the Root-Node. Another important node in the tree is Leaf -Node that has no child node.

Then, for quick navigation through the tree-there is Pointers that are basically fields to help locating related records.

There are Indexes (that are again B-Trees) that help in minimizing number of I/O operations.

If logical corruption to database occurs, its consequences would be distortion of B-Tree, Dis-ordered index, broken links between tables and records, incorrect physical and logical numbering of pages in B-tree etc. Such threats cannot be detected easily and thus are hard to fix. However, for such issues Microsoft has provided ISInteg utility that works on corruption at application level like damage to keys, links, tables etc. Its main task is to correct relationships between tables and records.

Another recommendation to fix such kind of damage to database is retrieving and convert mailbox data from corrupt Exchange 2010 to PST file by preventing any mounting issues. To avail this facility, investment in some third party EDB to PST recovery software is necessary.

Exchange Recovery software has online demand because of its ability to retrieve corrupt Edb to Pst. Developers of this high up solution is involved in catering its services in truth of domains like data recovery, email migration, Pst management etc.