%20on%20daily%20basis%20as%20a%20part%20of%20regular%20maintenance%20process.%20Also,%20the%20application%20provides%20an%20offline%20defrafgmentation%20technique,%20which%20is%20accomplished%20by%20eseutil%20/d%20command.%20Both%20of%20these%20methods%20discard%20the%20unused...){kind=link}
EDB Renamed and Corrupted after Defragmentation
Author: Axel Culver
Author: Axel Culver
Exchange data fragmentation occurs within the database. To reduce its effect, Exchange Server includes a default defragmentation process (called online defragmentation) on daily basis as a part of regular maintenance process. Also, the application provides an offline defrafgmentation technique, which is accomplished by eseutil /d command. Both of these methods discard the unused space, but occasionally introduce some database errors that cause database to corrupt. To repair such corrupted databases, you need to apply eseutil repair commands or restore from the last available backup. However, if these measures don't help, you should repair the corrupted database using an Exchange Recovery tool. For instance, consider the following practical scenario. You try to defragment the Exchange database (*.edb) with eseutil /d command, but the process fails while it is defragmenting the database. After this, you observe that the file in effect is named as *.edb.edb. You rename it to *.edb, but Exchange Server refuses to mount it further.
When you try to perform soft database recovery, you get an error message, as below: Checking database integrity.Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non-database file or corrupted db) after n seconds The database is inaccessible . Cause The EDB file is severely corrupted and cannot be mounted. Solution You can try to implement the following suggestions to solve the described issue: 1.Restore from the last backup you have. 2.If the soft recovery has failed, you can use hard recovery command- eseutil /r. Make sure you backup the file first. It is the hard command and usually deletes the corrupted pages that it cannot understand. 3.If the above solutions are not valid, you should use a third-party database repair utility. Such software can easily repair a corrupted EDB file without harming the original integrity of the file. Microsoft Exchange Recovery tools are specifically designed products with high competency to repair a corrupted Exchange database. An Exchange Recovery utility has a self-explaining interface and suitable documentation. They can repair a database corrupted due to any logical instance. For this, the software apply a powerful set of scanning procedures, which are also safe for the database originality. Exchange Server Recovery is a powerful solution that repairs and restores damaged Exchange databases in each case. The Exchange Recovery Software supports Exchange Server 5.5, 2000 and 2003. It is a safe database repair tool with various user-end graphic features. The tool recovers all user mailboxes in individual *.pst files, which can be imported in Outlook.About the Author:
Axel Culver has passion for writing Technical article. He is right now writing articles related to Product like Microsoft Exchange Recovery Tools and Inbox Repair Tool for MS Outlook. He is a professional writer and has written many blogs, article, press releasing and content for many websites.