“I am using Microsoft Exchange Server to meet my business requirements. However, I am sick with all the major solutions of backup. Even with the Windows server backup, which includes the backup of EDB database & associated logs. Before mounting back the Exchange databases, it ended up in dirty shutdown. I am a bit curious in knowing that is there any possible method to recover Exchange database from dirty shutdown state?”
Exchange Server is like a blessing to users by Microsoft. It is one of the popular media for the storage of database and for executing cross-communication among organizations. However, sometimes the issue like dirty shutdown in Exchange has come up in front of users. Now, the question arises that what is dirty shutdown in Exchange?
The database in MS Exchange is based on the technology of JET Blue engine. This technology uses a cache of the database to reduce the number of Input-Output process to the transaction logs. If the update is not done it will not write into the outstanding transaction and JET engine marks the database as dirty. Moreover, an obstruction caused the system to shutdown, resulting in the dirty shutdown state.
Now, we will discuss the method how to repair Exchange database from the dirty shutdown.
Methods to Recover Exchange Database From dirty Shutdown Using ESEUTIL
In this section, will discuss that how by using ESEUTIL command users can perform recovery of Exchange database from dirty shutdown. However, there are certain points that a user must keep in mind before opting for this process such as:
- An expert should operate the ESEUTIL command. The reason behind this is that it is complicated & may result in data loss.
- There should be 20 and 110 percent availability of free space to repair & defragmentation respectively.
- The consumption of the time to repair Exchange database DB from Dirty shutdown state depends upon the size of the Exchange database.
- Quite often, the mounting database can cause the problematic situation. Therefore, it should be dismounted from the server so that it can run against ESEUTIL.
Method 1 – Soft Recovery of Database:
At the time when Log files present in a clean state, then users can repair data by using ESEUTIL. In soft recovery, the log transaction will be replayed with the help of log & checkpoint files. ESEUTIL is a command line tool that helps in performing different operations against the database as it comes with a variety of switches.
Note: It is very important to check the state of the database before executing soft recovery.
To check the state of the database use /ml switch of ESEUTIL. This is the syntax for this Eseutil /ml “Path of the log files\log prefix
Now, once it is done, use this syntax for soft recovery
ESEUTIL / r enn /L(path to log files) /s(path to checkpoint file) /d(path to database file) /i
Method 2 – Hard Recovery of Database:
Hard recovery is different from soft recovery as it replays log transaction by restoring the database from online backup. In case there is an availability of valid & recent database then you can restore .stm, .log, and .edb files. After the restoration, you will get restore.env file.
Note: There is a possibility of loss of data in hard recovery method, therefore, it is recommended to create a copy of restore.env & log files.
You need to use this syntax for hard recovery Eseutil //cc “Path of the restore.env containing folder”
Once the hard recovery is finished, the folder that is temporary with restore.env will be empty. However, what if there is no valid backup? This is possible if the log data files are inconsistent & there is no backup. In such circumstances, you need to repair the database with help of /p switch.
- The syntax used for this is D: \Program Files\Exchsrvr\Bin>eseutil / “D: \Exchsrvr\Mailbox Store (Server).edb”
- You will receive a message that this process might result in the loss of data. It will ask if you want to proceed further. In this box, you need to click on OK.
- Now, the process of database repairing will begin. Those pages, which are unused, will be eliminated in this process from the Exchange database.
After this completion of recovery process, check the state of the database with the help of /mh switch once again. In case, the state is Clean Shutdown, then proceed to defragmentation offline process.
Perform Offline Defragmentation in MS Exchange via ESEUTIL Command
One of the main reasons behind performing defragmenting is to delete unused pages as mentioned above. Use this syntax for this eseutil /d Database_Name.
ESEUTIL Commands Fails: Go for an Expert Solution
It is possible that the above-mentioned method will fail to perform the recovery of Exchange database from dirty shutdown. Therefore, in such situations, it is recommended to opt for a third party utility. One such reliable third party tool is Exchange Recovery. This software can repair the database of Exchange in an effortless way and also provide an option to export Exchange EDB mailbox to PST format so that user can also open in Outlook. It can even repair Exchange database DB from dirty shutdown state. The simple interface makes the software popular among its users.
ESEUTIL is a command line tool that comes up with different switches to repair and recover Exchange database. However, sometimes it fails to recover Exchange database from the dirty shutdown state. Therefore, in above article, we have come up with an automated solution. With this, the process of recovery has become easy, smooth and quick.