@dustinb3403 said in Exchange migrations, scenarios to hope you're never in.:
User abuse is the only bug we can't fix with technology.
Good to know eseutil was able to correct the issue.
Even that was just very weird. The status had stopped updating and processes associated with it quit doing anything for around 20 minutes. We were both wondering what was going on when I was like "I'm going to ctrl+c it." So the cancel current command actually kicked off a whole bunch of activity that went quite quickly compared to what it had been running at before and actually repaired the DB. We were both more than a little confused over that one.