Exchange 2010 DB in Dirty Shutdown after deleting transaction logs
Posted on 2012-03-31
I made a bit of a noob error last night. I was moving a load of mailboxes over from a database on hard drive 1 which was pretty much full to a new DB on an empty Hard drive, HDD 2.
I all of a sudden saw that HDD 2 had pretty much zero free space, it had generated nearly 60GB of transaction log files. I didn't have time for a backup and it appeared the database had dismounted. I didn't look at the event log and on auto pilot I just started deleting the transaction logs and tried to remount the DB.
I then found the DB was in a dirty shutdown state and eseutil /mh had a jet error of missing transaction logs. Oops.
I quickly started trying to recover the transaction logs, and I have managed to get about 4/5ths of them back, but eseutil /mh still complains of log files missing, which is no real surprise.
I am currently trying eseutil /p on a copy of the DB to see what kind of data loss I'm looking at, I do not have a backup so please don't go there - the mailboxes were being moved in a live environment so there would be mails lost from during the working day if I reverted to an old DB from HDD1.
Is there any way I can limit the damage by taking advantage of what log files I DO have? The thing that really worries me is one of our big, very important mailboxes was in the middle of a move when this happened, and the move request is still marked as "moving". Does anyone know what might happen to this?
Thanks in advance.
PS the box is exchange 2010 SP1 and 2008 R2 standard.