There are some situations, such as virus infection, improper system shutdown, application malfunction, and missing database objects, where the Exchange Server Database (EDB file) may get damaged and all of the stored data become inaccessible. To handle such situations, Exchange Server includes a repair utility called Eseutil. It can detect errors, repair them and defragment the hard drive. But this utility can not handle the situation in case of severe damage and you encounter data loss situations. At this point, you are required to go for
Exchange Server Recovery solutions.
Sometimes when you attempt to repair a damaged Exchange Server database using Eseutil tool, the process might fail and you may find the following entries in the Application Event Log of Exchange Server:
Event Type: Information
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 301
Date: 29-08-2003
Time: 13:44:26
User: N/A
Computer: SNUCKERSERVER
Description:
Information Store (2040) 8f47d891-b071-466b-b70d-ae123f886ea6: The database engine has begun replaying logfile C:\Program Files\Exchsrvr\mdbdata\E00.log.
For more information, click http://www.microsoft.com/contentredirect.asp.
And
Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 494
Date: 29-08-2003
Time: 13:44:27
User: N/A
Computer: SNUCKERSERVER
Description:
Information Store (2040) Database recovery failed with error -1216 because it encountered references to a database, 'C:\Program Files\Exchsrvr\mdbdata\priv1.edb', which is no longer present. The database was not brought to a consistent state before it was removed (or possibly moved or renamed). The database engine will not permit recovery to complete for this instance until the missing database is re-instated. If the database is truly no longer available and no longer required, please contact PSS for further instructions regarding the steps required in order to allow recovery to proceed without this database.
For more information, click http://www.microsoft.com/contentredirect.asp.
This situation occurs generally in case of serious damage to Exchange Server database, which can not be repaired by Eseutil. In such circumstances, you need to repair and restore the database using third party Exchange Server Repair solutions.
These solutions are available in the form of easy to use applications, known as Exchange Server Recovery software. These software apply efficient scanning algorithms on the corrupted EDB file to retrieve all of its damaged or corrupted objects such as emails, notes, contacts, tasks and so forth. These tools have interactive and simple graphical user interface to provide easy, quick and absolute recovery.
Microsoft Exchange Recovery tool is the most effective and advanced tool to effectively retrieve all of the inaccessible data from EDB file. It works well with Exchange Server 2003, 2000 and 5.5. This Exchange Recovery software is compatible with Windows 2003, XP, Windows 7 and 2000.
