born2see
asked on
Exchange Database is in a Dirty Shutdown State
I keep getting these informational events (event id 200) but the server is working fine. I need to reboot it but I'm afraid the IS won't remount. Thanks in advance.
Instance 2: Database headers have been successfully validated. All databases are in a dirty shutdown state. To bring these databases to a clean shutdown state, log generations 3487 (0x00000d9f) to 3488 (0x00000da0) will be required.
As per the event two transaction logs are missing or corrupted which are not committed to the database. For which the databases went in to dirty shutdown state. You can go for three options.
1. The little bit harder and risky option is dismount the databases. Copy the transaction logs to some other location. Delete the above mentioned two transaction logs if present and then rename the next two transaction logs with the deleted one and then rename other transaction logs also sequentially. You should be more careful while renaming. Now you should be able to mount the store without any errors. You loose only 10MB of emails.
2. As KCTS mentioned, you need to dismount and repair your databases. But this case a possibility is there the repair may fail.
3. More safe and best option is using Exmerge export all the current mailboxes to PSTs online. Then repair the databases. Evenif the repair fails, you can successfully mount the blank mailboxes stores after moving out the database files from the store location. Then you can import/merge the PSTs to the individual mailboxes online.
Sekhar
1. The little bit harder and risky option is dismount the databases. Copy the transaction logs to some other location. Delete the above mentioned two transaction logs if present and then rename the next two transaction logs with the deleted one and then rename other transaction logs also sequentially. You should be more careful while renaming. Now you should be able to mount the store without any errors. You loose only 10MB of emails.
2. As KCTS mentioned, you need to dismount and repair your databases. But this case a possibility is there the repair may fail.
3. More safe and best option is using Exmerge export all the current mailboxes to PSTs online. Then repair the databases. Evenif the repair fails, you can successfully mount the blank mailboxes stores after moving out the database files from the store location. Then you can import/merge the PSTs to the individual mailboxes online.
Sekhar
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
When a database is still online, the database is always in dirty shutdown state. Only if the database is taken offline, it will then appear in clean shutdown state, as all the transaction logs not submitted will be played into the database.
Event 200 is an information event, not an error event. So when the event 200 appears, it is not indicating an error in your Exchange database.
Event 200 is an information event, not an error event. So when the event 200 appears, it is not indicating an error in your Exchange database.
If a database is in a "Dirty Shutdown" state, all existing transaction logs from the checkpoint forward must be present before you can mount the database again. If these logs are unavailable, you must repair the database with Eseutil /p to make the database consistent and ready to start.
Caution :
If you have to repair a database, some data may be lost. Data loss is frequently minimal; however, it may be catastrophic. After running Eseutil /p on a database, you should complete repair of the database with two further operations: