Tips to Fix Exchange Dirty Shutdown State in Exchange Server

Microsoft has made some major enhancements in Exchange Server 2010 over its earlier versions. One of the most fundamental features is Data Availability Groups (DAGs). It enables you create a setup of multiple servers that host copies of individual databases. DAGs along with other features (such as Cluster Continuous Replication) ensure high availability of user mailboxes even in Exchange downtime situations. In addition, you can mix and match copies of databases stored on each server.

When an Exchange Server 2010 Mailbox Server is installed, a mailbox database is created automatically. This database contains the ‘.EDB’ file, ‘.CHK’ file, and ‘.LOG’ files. The actual data resides either in the server memory inside the log files or in the mailbox database. Initially, the mail data is stored in memory in the form of pages. These pages are updated as a part of transaction and then written to the log file. When the pages are not required by Exchange, they are written to the database. Lastly, changes are made to the checkpoint file to indicate the new checkpoint location.

Thus, the mailbox database file is an open file that has some of its data in the log files, before this is finally flushed to the database. At this stage, the database is dismounted and shut down cleanly. In case the Exchange Server crashes, the database will be shut down abnormally. This database state is known as the ‘dirty shutdown’ state. Here, the log files still contain the actual data. When you start the server again, it would perform an automatic recovery based on the data stored in the log files. The Exchange Server starts at the checkpoint and replays all the information after that to make your database consistent. If it fails to mount the database after replaying the logs, you can use ‘ESEUTIL’ to perform database recovery as follows:

  • Run the below command from the BIN folder to perform a soft recovery of your database:

ESEUTIL /P database_filename.edb

  • If the database is still inconsistent, perform a hard repair by running the following command from the same BIN folder:

ESEUTIL /P database_filename.edb

  • Now, delete all the ‘.log’ and ‘.chk’ files.
  • Defrag the Exchange database by running ‘ESEUTIL /d database_filename.edb
  • Try to mount the database.

If you are unable to mount your Exchange database, then take help of professional Exchange recovery software. These utilities are proficient in repairing damaged Exchange databases to safely recover your precious mailboxes. They support recovery of databases created with MS Exchange Server 2010, 2007, 2003, 2000, and 5.5.


About rickytechblog

Working as an MS Exchange server administrator.
This entry was posted in Tech. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s