| Logical corruption in Microsoft Exchange Server | | | | wrong transaction log files, after restoring the |
| database (EDB) is very problematic and quite | | | | database. The logical corruption is indicated by the |
| difficult to identify and repair than physical | | | | “bad page link” or JET_errBadPageLink |
| damage. The administrators and users are | | | | errors. In such cases, you need to go for |
| generally unaware of logical corruption to EDB file. | | | | Exchange Repair to get your valuable data back. |
| Microsoft Exchange Server does not include any | | | | Resolution |
| inbuilt tool to diagnose and warn you about the | | | | In order to sort out this issue, go through the |
| logical database corruption. There are no specific | | | | underwritten steps: |
| symptoms to recognize such kind of corruption. In | | | | 1. |
| case of logical corruption, entire database | | | | Restore Exchange Server database (EDB) from |
| becomes inaccessible and you come across critical | | | | recent backup. It is important that only log file, |
| data loss situations. In order to overcome logical | | | | which are restored from backup get replayed, not |
| database corruption, you are required to go for | | | | any existing log file that might available on |
| Exchange Recovery solutions. | | | | Exchange Server hard drive. |
| In a practical scenario, when you attempt to | | | | 2. |
| access data from Microsoft Exchange Server, | | | | Use exmerge.exe (Microsoft Exchange Mailbox |
| you might find the following entries in Application | | | | Merge) tool to export data, then important into |
| Event Log: | | | | new priv.edb file. |
| Event ID: 42 | | | | 3. |
| Source: EDB | | | | Use “Move Mailbox” feature in Exchange |
| Type: Warning | | | | Administrator program for moving users from |
| Category: General | | | | damaged Exchange Server to another one. |
| Description: MSExchangeIS ((###)) The database | | | | Recreate priv.edb file on original server and then |
| engine found a bad page. | | | | move users back to original server. |
| The above event shows that the inner structure | | | | When all else fails, repair and restore corrupted |
| of the database has got damaged, because the | | | | EDB file with the help of third party Exchange |
| internal references (pointers) are misaligned or | | | | Recovery tools. These applications used advanced |
| corrupted. The Exchange Server might become | | | | scanning mechanisms to methodically scan the |
| unusually unresponsive, sluggish or slow. | | | | entire EDB file and extract all of the user |
| Cause | | | | mailboxes from it. These programs are very easy |
| The logical corruption of Exchange Server | | | | to use and allow you to have Do It Yourself |
| Database might take place if you replay the | | | | Exchange Repair. |