April 11, 2017 at 1:19 am
Morning All,
We have a maintenance Window weekly of a couple of hours - At the moment when I am patching or need to down one of the replicas I set automatic failover to false and then do whatever needs doing (in this case patching and memory (re)throttling. Then I started to wonder if this is the correct way of doing it?
Should I be altering automatic failover when rebooting/restarting during a planned maintenance window? Is there a better method?
Cheers
Alex
April 17, 2017 at 6:52 pm
Hi Alex,
it does not matter if you keep the automatic fail over to true or false as long as you perform the operation on the passive node. If you want to be on the sure side that nothing goes wrong, you can also disable it.
If have a clustered instance with an availability group on a standalone instance acting as secondary. I patch the standalone instance, review after patching/restart the AG still synchronizing and afterwards start patching the the clustered instance by starting with the passive node.
I don't know if you have the same configuration or you have only standalone instances. Be aware that AGs on standalone instances do not fail over automatically when database related errors occur (for example the disk for the user database is no longer available).
April 17, 2017 at 9:09 pm
As long as you remember to set it back to the desired setting.
I know some people like to also suspend data movement when doing patches.
Personally, I think it is a matter of preference.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply