Have an sbs 2011 server running exchange 2010. Server was crashed this morning. Only recourse was to have onsite customer power cycle. After the initial power cycle I know for sure Exchange worked because emails cmae to me from them that had been queued in their outlook. However, I guess someone got impatient with the long boot times of the server and power cycled the server two more times each time before it finished.
So now we have corrupted log files. Backups are no good for a variety of reasons and all of them boil down to the customer ignoring repeated warnings and not holding up their end. Which is nice for the blame game, but doesn't help fix the problem which is all I care about at this point.
I am not an expert on fixing this specific problem. I have tried following several online instructions, but things may have gotten worse.
I've tried eseutil /r, but it fails with a -501 log file is corrupt after 0.172 seconds.
Tried it on older set of log files from before the crash (shadow copy), but this gets half way then fails out with -1216 an outstanding database attachment has been detected at the start or end of recovery, but database is mising or does not match attchment info after 1.263 seconds
so before I make it any worse, I'm hoping someone can help me. I'd just love to get the thing back in the state it was at 9 am before the crash. I have shadow copies and that's it.
If we lose some recent data, fine. I just need this sucker mounted and running.