Repair Corrupt Exchange Database using 6 Simple Steps of EseUtil
A corrupted or insanely damaged Exchange database goes into the dirty shutdown state. Due to this, it dismounted and stopped working. As a result, the disseverment of users with their mailboxes affects organizations on a very large scale. EseUtil is a command-line tool that is used to repair corrupt Exchange database. Exchange Admins also use EseUtil to perform the regular monitoring of database issues and then deal with them.
EseUtil helps the administrators to repair the corrupted Exchange database, because of uncommitted logs to the database, deletion or missing logs, server crashes, malware, etc. This write-up is all about the necessary steps to repair a corrupted Exchange database using EseUtil. Let’s move to the steps in detail.
6 Steps to Repair Corrupt Exchange Database
It’s time to explore the required steps for repairing the corrupted Exchange database. Execute the below steps sequentially for an error-free repair of the corrupted or dismounted Exchange database.
Step 1. Know Corrupted EDB File Location
The first step is to find the location of the corrupted EDB file. During the installation of the Exchange server, the EDB file is created. That can be stored at different locations. Most of the admins move EDB files from one location to another just to create space in the specified drive. Also, identify the location of the .log and .chk files.
Step 2. Verify Database Status
In this step, you need to decide whether you need to repair corrupt Exchange database or not. Find the status of the Exchange database using the below steps:-
1. Type Windows+R and then enter \EXCHSRVR\BIN and OK.
2. Hit on the address bar and copy the path of the Eseutil.exe.
3. Run the Exchange Management Shell (EMS) and then move to the Eseutil.exe location.
4. Now run the below commands in the PowerShell window:
Eseutil.exe /mhEseutil.exe /mh C:\mbx01\mbx01.edb
Through these commands, you will find detailed information regarding the Exchange server. Verify the header state, if it is clean shutdown then it is consistent and working fine. If Exchange dirty shutdown, then the database is inconsistent or dismounted.
Step 3. Backup Database Files
After locating and verifying the database inconsistency. It’s time to backup the database files such as logs, and checkpoints. The backup of files can be stored in separate folders to maintain the folder hierarchy.
Step 4. Repair Corrupt Exchange Database Using Soft Recovery
To deal with the minor fixes in the Exchange database. The soft recovery is the first approach. In this fix, EseUtil tries to commit the logs on the database which was left behind because of several issues. It also takes care of data integrity and security throughout the process. To fix the Exchange database using soft recovery execute the below commands:-
EseUtil /rEseUtil /r C:\mbx01\mbx01.edb
These commands take some time as per the performance and storage of the server.
Step 5. Check the Status of the Database
To check the status of the database after performing the soft recovery, run the below command.
EseUtil /mh C:\mbx01\mbx01.edb
Validate the status is it a clean shutdown or a dirty shutdown? If it is a clean shutdown then the database becomes consistent. If it is a dirty shutdown, then the Exchange database is still inconsistent.
Step 6. Perform Hard-Recovery using EseUtil
The hard recovery is only performed when the soft recovery has failed. Make sure that you are using it when there is no more option to repair corrupt Exchange database. To do so execute the below command.
eseutil /p “name_of_the_database.edb”
Note:- Eseutil/p recovers the data of the mailboxes. It also removes the data which looks to be corrupted or deemed. So, this process also leads to data loss.
This is all about the steps to repair corrupt Exchange database. There is no surety that the dirty shutdown error does not occur again. There might be the possibility that the same issue can persist again.
To maintain the integrity and security of the Exchange database, the best approach is to perform transition from Exchange to Office 365 mailbox because there is a huge difference between Exchange On-Premises and Exchange Online. Office 365 comes up with different benefits such as accessing data becoming easier and enhancing the security of the data. But the question is how to do this. Don’t worry, in the next section, you will find how to move to Office 365 seamlessly.
The Transition from Exchange to Office 365
One of the widely used and expert choices is the Migrator Wizard Exchange Migration Tool. It is trial and tested by experts to migrate Exchange Mailbox to Office 365 without hassle. This tool is composed of several advanced features such as a Date filter, Retry failed items, Delta migration, and many more. An interactive dashboard is also incorporated within the tool through which, you can keep track of the complete process. It preserves the folder hierarchy after the process ends. This tool is not limited to techy users only, it can be used by non-tech users also.
Final Words
Exchange server databases can be corrupted for several reasons such as malware and server crash. EseUtil tool can repair corrupt Exchange database using two distinct approaches such as soft and hard recovery. But it is not sure that the same issue will not arise again. So for a permanent and reliable solution, you should move to Office 365 from the Exchange server for a better and error-free platform.