Logical Corruption and Bad Page Error in Exchange Server Database

Logicalcorruption in Microsoft Exchange Server database (EDB) is veryproblematic and quite difficult to identify and repair than physicaldamage. The administrators and users are generally unaware of logicalcorruption to EDB file. Microsoft Exchange Server does not includeany inbuilt tool to diagnose and warn you about the logical databasecorruption. There are no specific symptoms to recognize such kind ofcorruption. In case of logical corruption, entire database becomesinaccessible and you come across critical data loss situations. Inorder to overcome logical database corruption, you are required to gofor ExchangeRecoverysolutions.

Ina practical scenario, when you attempt to access data from MicrosoftExchange Server, you might find the following entries in ApplicationEvent Log:

EventID: 42
Source: EDB
Type: Warning
Category:General
Description: MSExchangeIS ((###)) The database enginefound a bad page.

Theabove event shows that the inner structure of the database has gotdamaged, because the internal references (pointers) are misaligned orcorrupted. The Exchange Server might become unusually unresponsive,sluggish or slow.

Cause

Thelogical corruption of Exchange Server Database might take place ifyou replay the wrong transaction log files, after restoring thedatabase. The logical corruption is indicated by the “bad pagelink” or JET_errBadPageLink errors. In such cases, you need to gofor Exchange Repairto get your valuable data back.

Resolution

Inorder to sort out this issue, go through the underwritten steps:

1. Restore Exchange Server database (EDB) from recent backup. It is important that only log file, which are restored from backup get replayed, not any existing log file that might available on Exchange Server hard drive.

2. Use exmerge.exe (Microsoft Exchange Mailbox Merge) tool to export data, then important into new priv.edb file.

3. Use “Move Mailbox” feature in Exchange Administrator program for moving users from damaged Exchange Server to another one. Recreate priv.edb file on original server and then move users back to original server.

Whenall else fails, repair and restore corrupted EDB file with the helpof third party ExchangeRecovery tools.These applications used advanced scanning mechanisms to methodicallyscan the entire EDB file and extract all of the user mailboxes fromit. These programs are very easy to use and allow you to have Do ItYourself ExchangeRepair.

StellarPhoenix Mailbox Exchange Recoveryis the most advanced and effective solution to retrieve data from EDBfiles of Exchange Server 2003, 2000 and 5.5. This software isdesigned to work with Microsoft Windows 2003, XP and 2000. Withread-only and non-destructive conduct, this software is completelysafe to use.