customer had unresponsive SBS 2011 (running on Hyper-V as VM) and only chance was to roll-back to yesterday's backup. But unfortunately, Veeam B&R was NOT made with Application-Aware option, so now customer has:
- SBS 2011 with Exchange in USN Journal Roolback state, NETLOGON paused, reg Key confirmed 0x4, it is not replication
- 2 addtional DCs in this domain, which are OK
I read a lot of MS articles and they all say we need to DEMOTE SBS from domain and DCPORMO it back...but this is an illusion, Exchange will break for sure. I am even not sure if SBS can be demoted anyway. The second option MS recommends is to DEMOTE all other DCs, make SBS primary, remove "DSA Not Writable" KEY from registry, and then re-add other DCs back.
But all this seems like too big deal for me.
Wouldn't I just simply do a non-authoritative restore, and USN Journal would get back into sync?