Article Content King

You are viewing: Logical Corruption and Bad Page Error in Exchange Server Database
By Axel Culver

Logical Corruption and Bad Page Error in Exchange Server Database

Articles - Computers - Data-Recovery - View Article



Publish this article

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. 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 Microsoft Exchange Recovery 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.
See All articles From Author

Axel Culver has passion for writing Technical article. He is right now writing articles related to Product like Exchange Server Software and Exchange Recovery Tool. He is a professional writer and has written many blogs, article, press releasing and content for many websites.

for More Visit at: Microsoft Exchange Recovery

Article Source : http://www.articlecontentking.com

Tags: exchange recovery exchange server recovery exchange server software microsoft exchange recovery
Word Count Appx. : 479 | Article Views 621 Published 25-10-2009


Related articles
Data Recovery
By: Russell Phillips | 05-11-2008
Memory storage has witnessed a technological revolution in the last few years, from the big sized floppy disks that allowed nothing over a mere megabyte of data to the gigabytes that we can easily store on a Flash today. (read entire article)
Boot Sector Corruption and File Loss Due to Power Off/Shutdown in Windows
By: Richard Dawson | 06-10-2009

Sometimes you may face boot sector corruption issues on a Windows NT-based operating system computer, if you've installed the operating system on a FAT file system formatted partition. In such situations, the computer might not start properly, when you (read entire article)

Hard Drive Recovery Is Not For the Faint of Heart
By: Tom Stabler | 29-06-2009
I went to work and during lunch I purchased a new hard drive. When I got home I told my wife that everything was under control. I installed the new hard drive and using my most recent backups (six months old) and the recovery disks, I was able to get & (read entire article)
How to Recover Data From a Failed Hard Drive
By: Stephen Drummonsy | 09-05-2010

This article will help you to recover hard drive data before it is too late.

(read entire article)
Data Recovery and Your Computer
By: Clive Haman | 11-12-2009

Data recovery for your computer

(read entire article)
Easy way for removing duplicate Outlook contacts
By: mac nicolson | 04-10-2010

Contacts imported to PST file results in duplicity of contact information. But duplicate Outlook contacts are easy to remove from PST file using manual methods. Also, there is an efficient tool to remove duplicate contacts in much easier way.

(read entire article)
The Fix Computer Problems Virus Scan Guide
By: Bryon Zirker | 20-12-2009

Downsides to ineffective repairs and loading the OS new include having...

(read entire article)
How to Solve MAPI call "OpenMsgStore" failed Error?
By: Axel Culver | 30-12-2009

For Exchange Server, MAPI uses different interface methods. The OpenMsgStore is the method associated with IMAPISession interface that is used to open a message store.

(read entire article)
Simply Create a System Image in Windows 7
By: Mike Rogers | 27-08-2010

Windows 7 owns good tools that you could use to periodically backup your important files, but not just documents. You'll be able to make a clone of entire Windows 7 partition and then restore that later along with all the earlier applications, setting (read entire article)