Logical Corruption And Bad Page Error In Exchange Server Database Article

	1888 Articles Home \| Computer Articles \| Data Recovery Articles \| Windows Articles	Data Recovery RSS
Logical Corruption and Bad Page Error in Exchange Server Database

Logical corruption in Microsoft Exchange Server database (EDB) is very problematic and quite difficult to identify and repair than physical damage. The administrators and users are generally unaware of logical corruption to EDB file.

Author: Axel Culver

Article Tools:

Microsoft Exchange Server does not include any inbuilt tool to diagnose and warn you about the logical database corruption. There are no specific symptoms to recognize such kind of corruption. In case of logical corruption, entire database becomes inaccessible and you come across critical data loss situations. In order to overcome logical database corruption, you are required to go for Exchange Recovery solutions.

In a practical scenario, when you attempt to access data from Microsoft Exchange Server, you might find the following entries in Application Event Log:

Event ID: 42
Source: EDB
Type: Warning
Category: General

Description: MSExchangeIS ((###)) The database engine found a bad page.
The above event shows that the inner structure of the database has got damaged, because the internal references (pointers) are misaligned or corrupted. The Exchange Server might become unusually unresponsive, sluggish or slow.

Cause

The logical corruption of Exchange Server Database might take place if you replay the wrong transaction log files, after restoring the database. The logical corruption is indicated by the “bad page link” or JET_errBadPageLink errors. In such cases, you need to go for Exchange Repair to get your valuable data back.

Resolution

In order 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.

When all else fails, repair and restore corrupted EDB file with the help of third party Exchange Recovery tools. These applications used advanced scanning mechanisms to methodically scan the entire EDB file and extract all of the user mailboxes from it. These programs are very easy to use and allow you to have Do It Yourself Exchange Repair.

Stellar Phoenix Mailbox Exchange Recovery is the most advanced and effective solution to retrieve data from EDB files of Exchange Server 2003, 2000 and 5.5. This software is designed to work with Microsoft Windows 2003, XP and 2000. With read-only and non-destructive conduct, this software is completely safe to use.

About Author

Axel Culver has passion for writing Technical article. He is right now writing articles related to Product like Exchange Server Software and Exchange Repair Software. He is a professional writer andhas written many blogs, article, press releasing and content for many websites. For more information: http://www.ms-exchange-server-recovery.com

Article Source: http://www.1888articles.com/author-axel-culver-22336.html

Logical Corruption and Bad Page Error in Exchange Server Database