In my AG, I have two nodes using synchronous commit, automatic failover, allow all connections in primary role, and readable secondary as yes. The failover cluster is using a fileshare witness as the quorum. I have to reboot the secondary replica tonight.

What is the best practice for handling this type of maintenance? Since I have quorum, can I just reboot the secondary? Do I need to drain roles of the secondary in the cluster manager? Is there an AG maintenance mode?

  • Are you sending queries to the readable secondary? If so, how?
    – Greg
    Sep 12, 2018 at 20:43
  • Not directly. If so, just a few ssrs reports that are non-critical. Our applications all point to the AG listener name.
    – phoeneous
    Sep 12, 2018 at 21:01

1 Answer 1


No AG maintenance mode. You can restart secundary node and you will get events in logs, both SQL server and cluster, but nothing else. If you need to restart primary, first do an AG manual failover and check everything went fine.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.