Storage Group Logs went corrupt/database ESEUTIL stated in Dirty Shutdown, how to proceed forward
Posted on 2008-06-12
We've been migrating users over from new hardware to a new server. Last night during one major mailbox move the LUN the logs are stored on went on the fritz. As a result we lost the logs (can restore but had problems).
Anyway when I did a ESEUTIL check on the database it said it was in a dirty shutdown state, but I believe the data to be good. I would like to restore access to being writing logs "fresh" moving forward.
What is the easiest/most effective way to do this? I've been told to just do a eseutil /p on the database however also read horror stories about how long the Deleting unicode fixup table process takes (the EDB is about 40 GB.
In other words what is the best way to do this both in general and if the logs happen to be missing.