I am using AlwaysOn Availability Groups in SQL Server 2016 with a primary and secondary replica. I have a Quorum file share witness on a separate file server. This file server needs to be rebooted, so I'm wondering what I need to consider before rebooting this box...
Anyone have experience with this?
Also, I have some flexibility here in terms of down time and making adjustments to the primary and/or secondary. I'm really looking for the best way to take down this server and get the AG to be back and synchronized as easily as possible--even if it means an outage or temporarily removing a database from an AG and adding it back in later, etc.
Any guidance is appreciated!
EDIT: I have since found this thread, which essentially answers my question.
But would someone mind confirming that my assumption is right in that I wouldn't need to do anything special whatsoever to reboot the file share witness? Simply reboot it, let the AG continue to operate as normal, and then when the file share witness comes back online, carry on?
- This topic was modified 1 month, 1 week ago by Mike Scalise.
Mike Scalise, PMP