Online defragmentation of the Exchange databases is done as part of the maintenance routine. In this process, several database objects that are not being used are identified and removed. However, at times some problems may also occur in the EDB database file because of online defragmentation, which could result in serious problems in the longer run. In such cases, you should use appropriate corrective measures to repair the Exchange database. If you are unable to perform Exchange recovery, then you should use a third-party Exchange Server Recovery software to do so.
Consider a scenario wherein you are using MS Exchange 2003 in your organization. You perform online defragmentation on the Exchange database. After it gets over, you check the event log that displays either of the following error signatures:
“Date: date Source: ESE
Time: time Category: (12)
Type: Error Event ID: 447
Information Store (nnnn) A bad page link (error -327) has been detected in a
B-Tree (ObjectId: 19, PgnoRoot: 113) of database E:\Program
Files\Exchsrvr\mdbdata\priv1.edb (3440582 => 3443648, 3443232).”
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\exchsrvr\mdbdata\priv1.edb (157120 => 296404, 296403).
There could be the following reasons for this behavior:
The Server crashed as some transactions failed to commit to the hard disk.
Incorrect logs were copied while you restored the database.
Some database log files were removed that were not fully committed.
You should perform the following methods to resolve the problem:
Restore from backup: You should check if the backup is updated and clean. If yes, then restore the database from its online backup.
Run Eseutil utility: You should use the Eseutil utility to perform either hard repair of the database or for performing offline defragmentation.
Run Isinteg utility: You should run the Isinteg utility to rebuild the information store to fix the errors.
Run Exmerge: And finally, you should run the Exmerge utility to export the data to a newly created database.
If you are still facing while performing online defragmentation of the database, then you should use a third-party exchange recovery software to recover EDB database. Such read-only tools use fast yet sophisticated scanning algorithms to perform safe and secure EDB recovery.
Stellar Phoenix Mailbox Exchange Recovery is an exchange server recovery software that recovers corrupted EDB database files. Specifically designed for MS Exchange Server 5.5, 2000, 2003, and 2007, this edb recovery utility recovers the user mailboxes in separated PSTs files. It is compatible with Windows 7, Vista, Server 2003, XP, and 2000.