Jul 7, 2013

0 Exchange 2010 Database Dirty Shutdown

Exchange 2010 Database Dirty Shutdown State

When an administrator has installed an Exchange 2010 server in own environment then a database created name as exchange database by automatically. The Exchange 2010 database generally contains the .EDB file, .LOG file and .CHK file.
These files are enough to maintain the complete database of any organization in a perfect way.
All email messages, attachments, contacts, and related information’s are stored in EDB file, and exchange parallel maintains all transaction record in .LOG file as a text format.
So it means to say that these log files are important for Exchange 2010 database as well as administrator because all transaction is recorded in this file after any update.

All email information is stored in the form of the page in memory; these all pages are updated at the time of transaction and automatically written into a log file. When these pages are not required by the exchange administrator then they are updated in the database.

Thus, the Exchange 2010 database file is an open file which can store some email data in the log files before this is finally deleted to the database. At this stage, the database is dismounted and shut down cleanly and no issue for administrator. But if as same stage the Exchange 2010 has been crashed then database will be shut down abnormally. This state of database called ‘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 2010 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:

Check the database State:
You can use the Eseutil tool to check whether a database is in a clean shutdown state – if it is not in a clean shutdown state you can perform a repair to get the database into consistency.

Run Command   eseutil /mh “database name”

If you want to check the header of the log file you can use eseutil /mh
but this time you would indicate the log, for example E00.log

An Exchange Database Dirty Shutdown state has shown as below:

How to Fix: You can fix this error by run the soft recovery command:

ESEUTIL  /r  “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.

To know more about Visit here:  http://support.microsoft.com/kb/896143

Source : LINK


Post a Comment