How to perform Exchange Recovery for corrupt Exchange Server Database

Inconsistency of Exchange Server database depends on various factors, such as abrupt/unexpected system shutdown, hardware issues, and use of Anti-virus software. Whatever may be the reason, Exchange Server when gets inconsistent, may put you into serious problems, such as data inaccessibility. However, to get rid of the state of inconsistency, you have an Exchange's Eseutil utility that can be used to repair Exchange Server. But Eseutil utility is also not a perfect solution for the problem. Moreover, you can opt for a third party Exchange Server Recovery software.

Suppose, you are dealing with a corrupt Exchange Server database when you make an attempt to repair it with the help of a Eseutil/p command. After the completion of repair process, you noticed that some of the columns of a particular record is showing inconsistency. These columns are still not repaired or corrupt. On seeing the application log, you come across below event:

Event ID: 502
Source: ESE
process name (process id) The database engine lost one or more bad columns of data in one record. It is highly recommended that an application-level integrity check of the database be run to ensure application-level data integrity.

When a database is in inconsistent state and a repair using Eseutil /p is performed on a database, Event ID is usually generated.

Above event ID is generated, because of corrupt columns in a database. When you try to repair it with
Eseutil /p command and finds some bad columns in a record, but fails to repair them and the columns were discarded.

To solve above problem, and to perform Exchange data recovery. You have to follow the below steps:
  1. If the database repair process is successful, execute Isinteg -fix on the database, then ExMerge can be used to save the data to Outlook PST files, execute ExMerge to restore the data back into a newly created new database. You can also use Move Mailbox to transfer the mailboxes to another server. If the cause is the hardware problems, then it is advised not to use ExMerge or Move Mailbox until you do not fix the problems related to hardware.
  2. If the database repair process is unsuccessful because the database is badly damaged, then it is suggested to restore from online backup of Exchange aware. If no valid backup is available, then first of all verify whether Outlook users are locally storing data in Outlook PST files or not. If the data is locally stored in PST files, then make a new blank database and use the Outlook PST files to recover as much data as possible. 

However, if no proper results get found, then it is suggested to go for a third party Exchange Server Recovery tools. Such tools perform MS Exchange Recovery quite easily. Make a Google search for buying any one of the product that is used to recover exchange server. Quite simple and easy to use.

About the Author:
The author of this article has a strong background in computer technology; She has been a technical writer and blogger for over 5 years. Currently she has been writing articles related to topics like Exchange Server Recovery and EDB to PST Converter to recover and convert .edb to .pst file.


Post a Comment

All about Technology