Solved DCs out of sync
-
@scottalanmiller said in DCs out of sync:
Anytime something happens to a DC to get out of sync, just rebuild fresh.
So you would just deploy a new DC?
-
Yes, new DC would be my choice. No worries of lingering problems.
-
@scottalanmiller said in DCs out of sync:
Yes, new DC would be my choice. No worries of lingering problems.
That's what I'm always praying. But better safe than sorry, that's why I asked. Thanks Scott.
-
Good luck, and enjoy your trip!
-
@scottalanmiller said in DCs out of sync:
Good luck, and enjoy your trip!
Thanks. dcpromo looks good so far. Waiting for the reboot.
Still one hour left until I need to leave to catch the train
-
@thwr said in DCs out of sync:
@scottalanmiller said in DCs out of sync:
Good luck, and enjoy your trip!
Thanks. dcpromo looks good so far. Waiting for the reboot.
Still one hour left until I need to leave to catch the train
And... done
repadmin /showrepl does not show any errors. Same for dcdiag, which only complains about minor things as far as I can tell right now.
-
Cool
-
I think that I'm too late, but I concur that rebuilding is better than trying to find a way to recover the out of sync node - just not worth it.
-
@StrongBad said in DCs out of sync:
I think that I'm too late, but I concur that rebuilding is better than trying to find a way to recover the out of sync node - just not worth it.
That's the point. As long as you still have a working DC, issues are better solved by depolying a new machine.
-
@thwr said in DCs out of sync:
No substantial changes have been made during the last couple of weeks. Just a few new users and password changes plus maybe 2 or 3 new machine accounts. Some clients and servers now refuse to authenticate users during login due to the well known "trust could not be established between..." error.
Where you still getting those errors after you powered down the broken DC? I'm guessing not since you moved forward with the install of another DC.
-
@Dashrender said in DCs out of sync:
@thwr said in DCs out of sync:
No substantial changes have been made during the last couple of weeks. Just a few new users and password changes plus maybe 2 or 3 new machine accounts. Some clients and servers now refuse to authenticate users during login due to the well known "trust could not be established between..." error.
Where you still getting those errors after you powered down the broken DC? I'm guessing not since you moved forward with the install of another DC.
Nope. Only "missing that other DC" errors now, which is fine. I've got some crappy internet connection (free WiFi in the train, next to no 3G/4G signal) here and can't check the current state. but it was fine half an our ago.
-
@thwr said in DCs out of sync:
@Dashrender said in DCs out of sync:
@thwr said in DCs out of sync:
No substantial changes have been made during the last couple of weeks. Just a few new users and password changes plus maybe 2 or 3 new machine accounts. Some clients and servers now refuse to authenticate users during login due to the well known "trust could not be established between..." error.
Where you still getting those errors after you powered down the broken DC? I'm guessing not since you moved forward with the install of another DC.
Nope. Only "missing that other DC" errors now, which is fine. I've got some crappy internet connection (free WiFi in the train, next to no 3G/4G signal) here and can't check the current state. but it was fine half an our ago.
OK, reading your OP, it seemed that you were getting those errors after turning off the broken DC, but since you're not - seems like you found a good solution.
