September 29, 2018 at 7:55 am
Hello,
There are three nodes in Availability Group, Node 1 as Primary, Node 2 Read-Only, Node 3 Secondary.
When Patching Node 2 (Read-only) How should be done? what happens to read-only connections?
Thanks for your time, Very much appreciated of your help.
September 29, 2018 at 10:50 pm
Joe-420121 - Saturday, September 29, 2018 7:55 AMHello,
There are three nodes in Availability Group, Node 1 as Primary, Node 2 Read-Only, Node 3 Secondary.
When Patching Node 2 (Read-only) How should be done? what happens to read-only connections?
Thanks for your time, Very much appreciated of your help.
I do patching on Read-Only node as it is and it the instance will go offline when patches are applied ,connections will be directed to Primary and wont be impacted. Mine is only 2 node. Experts can give more in depth comment.
September 30, 2018 at 3:57 am
Thanks for the information. I searched online but could NOT find any authentic source for the behavior of [Ready-only node/ Connections] on Patching/ when it goes OFFLINE. Is the direction Automatic to Primary OR Manual? Thanks everyone.
October 1, 2018 at 3:50 am
I believe that connections will fail that are actively connected to the secondary right at the time it goes down, but new connections will be rerouted automatically.
October 1, 2018 at 4:15 am
I would suspend data movements to the databases that are part of the AG group, before applying any updates. We did this when applying a service pack to all servers in an AG group. You can also set the secondary server so that it is not a readable secondary but I've never bothered with that one myself. This all just makes the environment 'simpler' for the update - there's no traffic from the Primary to contend with at the same time and less to go wrong.
Ensure that your Primary log files are large enough to hold the data that is waiting, while data movements are suspended.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply