We had a secondary server bite the dust... we were remarkably able to resurrect it. Everything is great and intact... except for the windows server cluster configuration. We basically need to evict it and add it back...

I was thinking.. we could stop SQL services on this secondary replica, do the cluster work (evict / re-add) and then once the WSFC is happy for this node, start sql services back up... databases continue syncing as normal.

Or... would we need to completely remove the secondary replica from the AG and then rebuild everything?

Thanks for thoughts!

  • I believe the first approach should work, subject to condition the WSFC is working fine. If AG sync does not works then you would have to re sync it from scratch. – Shanky Jun 26 '20 at 14:41
  • Make sure that you don't lose the Quorum when you evict that node. If the quorum is not lost, then everything should work fine without removing the node from the AG. Keep in mind that there will be no log truncation until that other node come back (as the AG sync will be suspended). If you have some really highly active database in those AGs, you may want to remove them to avoid log disk to fill. – Dominique Boucher Jun 26 '20 at 18:34
  • Original idea worked great.Thanks for the input! Sometimes its just reassuring to bounce ideas off the community. Thanks again! – user119362 Jun 29 '20 at 13:00

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.