How to use ESEUTIL to repair/recover Exchange Databses?

Health of a databse: Run Eseutil /mh “Path of the database” and check the state of the database.

1. State= Clean Shutdown

Move log files from the Transaction logs folder location and mount the databse

2. State= Dirty Shutdown

Ensure that the log files required is in a Clean state by performing Eseutil /ml “Path of the log fileslog prefix” command

If the health status os ‘OK’ perform the Soft recovery with the command Eseutil /r <Log Prefix> /l “Path of the log files” /d “Path of the database”

Mount the database after completing the operation

Sometimes the ‘/i’ switch is also used when the operation has failed to complete

Hard Recovery

In the situation where log files are missing, restore from a successful back up or perform Hard repair

Once the restoration completes, a file named restore.env along with the logs that were backed up without being committed to the database will be created in C:Temp

Perform Hard Recovery by the command Eseutil /cc “Path of the restore.env containing folder”

restore.env file will be deleted after the completion of hard recovery

If we misses the sequence of logs, the recovery will fail and should use the command eseutil /cc “Path of the restore.env folder” /t to recover the databse

Hard Repair

Use eseutil /p “path of edb file”

Offline Defragmenation

Once Eseutil /p finishes we will need to defrag the databases. You must have available hard disk space equal to 110 percent of the size of the database that you want to defragment.

Tech Tip : Move your Exchange server into the cloud with desktop hosting service from with 24*7 dedicated migration support from Apps4Rent – Exchange, SharePoint, Desktop Hosting provider.

How useful was this post?

Click on a star to rate it!

Average rating / 5. Vote count:

As you found this post useful...

Follow us on social media!

We are sorry that this post was not useful for you!

Let us improve this post!

6 thoughts on “How to use ESEUTIL to repair/recover Exchange Databses?

  1. Florin Copil’s comment:
    1. Do not forget to check the latest committed log against the db with Eseutil /mk “path to the checkpoint file”
    2. You can move the logs which are already committed BUT you need to order them by date otherwise you might have some problems afterward with the backup.

    1. My exchange dtabaase became inaccessible after a power failure, and I had the same error message popping up again and again. I tried to fix it using inbuilt tools, but that didn’t help. I got to know about this tool from a friend and thought of giving it a shot. The demo version showed me all of my data and after purchasing the software, I recovered everything. This is really a great tool and the interface is pretty easy to understand.

Leave a Reply

Your email address will not be published. Required fields are marked *

Protected by WP Anti Spam