Microsoft Exchange Server maintains an .edb file which stores all user mailboxes. This .edb file when goes corrupt can give a real headache to server administrators. The reasons behind corruption include abrupt system shutdown, operating system malfunction, hardware failure, power fluctuations and others. As a result, the users are not able to send or receive e-mails. Each and every task related to Exchange server comes to a halt due to server downtime. Since such situations pose a great threat to valuable data, it becomes important to take appropriate steps. Being an administrator, you must opt for an efficient EDB recovery application.
Consider a scenario, wherein, you may come across the following error with your Microsoft Exchange 2000 or 2003 server computer:
The information store won’t start and you may receive the following error:
‘1067 The information store terminated abnormally’
When you go for online defragmentation, the following event is generated in the application log:
Date: date Source: ESE
Time: time Category: Database Corruption
Type: Error Event ID: 447
Information Store (nnnn) A bad page link (error -338) has been detected in a
B-Tree (ObjectId: 70950, PgnoRoot: 157120) of database e:\Program
Files\excshsrvr\mdbdata\priv1.edb (157120 => 296404, 296403).
In case of Event ID: 447, you are not able to mount the information store and the crucial .edb files goes inaccessible. To troubleshoot the problem, you must have a thorough understanding of the exact causes. Then only, you can decide upon relevant Recover EDB steps.
The Even ID 447 clearly indicates that the logical structure of the database has become corrupt. The reasons behind corruption could be:
1. The server suffered a crash as disk caching has not committed transactions to the hard disk
2. During a database restoration, incorrect log files were replayed
3. Or if a server has a defective hard disk controller
Also, as seen in the application log, a bad page link error means logical corruption at the Jet level in the database.
In order to troubleshoot the problem, you must consider the following steps:
1.If possible, restore the database using a backup which was created before this error
2.If no backup exists, perform hard repair by using eseutil.exe / p command.
3.After the hard repair, perform an offline defragmentation by running the eseutil.exe / d command
4.Finally run, the isinteg -s servername -fix -test alltests command on the database
5.If you are still not able to mount the database, then grab a third-party EDB recovery software
Such applications, being read-only are absolutely safe to use and perform EDB file recovery in a hassle-free manner.
Stellar Phoenix Mailbox Exchange Recovery is an advanced software which repairs corrupt edb files and recovers mailboxes as separate PSTs which can be directly imported in Outlook. Compatible with Exchange Server 5.5, 2000, 2003, and 2007, the Exchange recovery software also performs recovery of deleted mailboxes.