EDB Renamed and Corrupted after Defragmentation

Exchange data fragmentation occurs within theWhen you try to perform soft database
database. To reduce its effect, Exchange Serverrecovery, you get an error message, as below:
includes a default defragmentation process (called“Checking database integrity.Operation
online defragmentation) on daily basis as a part ofterminated with error -1206
regular maintenance process. Also, the application(JET_errDatabaseCorrupted, Non-database file or
provides an offline defrafgmentation technique,corrupted db) after n seconds”
which is accomplished by eseutil /d command.The database is inaccessible .
Both of these methods discard the unused space,Cause
but occasionally introduce some database errorsThe EDB file is severely corrupted and cannot be
that cause database to corrupt. To repair suchmounted.
corrupted databases, you need to apply eseutilSolution
repair commands or restore from the lastYou can try to implement the following
available backup. However, if these measuressuggestions to solve the described issue:
don't help, you should repair the corrupted1.Restore from the last backup you have.
database using an Exchange Recovery tool.2.If the soft recovery has failed, you can use
For instance, consider the following practicalhard recovery command- eseutil /r. Make sure
scenario. You try to defragment the Exchangeyou backup the file first. It is the hard command
database (*.edb) with eseutil /d command, but theand usually deletes the corrupted pages that it
process fails while it is defragmenting thecannot understand.
database. After this, you observe that the file in3.If the above solutions are not valid, you should
effect is named as *.edb.edb. You rename it touse a third-party database repair utility. Such
*.edb, but Exchange Server refuses to mount itsoftware can easily repair a corrupted EDB file
further.without harming the original integrity of the file.