November 16, 2018 at 3:57 pm
Sorry to ask this I have tried google but not found a reliable answer, If I had time, I would build it and test it however that is not an option either right now.
1. A SQL 2016 failover cluster instance with 2 nodes in site 1.
2. Not an AG just clustered SQL at this stage whole instance fails from one node to the other etc)
3. If I then configure a Synchronous AG with auto failover for the databases on the above cluster, with the secondary copy going to another separate instance of SQL in site 2
4. Does the AG failover automatically if the cluster becomes unavailable? Or is the only failover for the AG manual regardless of the cluster state?
TIA
November 17, 2018 at 11:01 am
global5729 - Friday, November 16, 2018 3:57 PMSorry to ask this I have tried google but not found a reliable answer, If I had time, I would build it and test it however that is not an option either right now.
1. A SQL 2016 failover cluster instance with 2 nodes in site 1.
2. Not an AG just clustered SQL at this stage whole instance fails from one node to the other etc)
3. If I then configure a Synchronous AG with auto failover for the databases on the above cluster, with the secondary copy going to another separate instance of SQL in site 2
4. Does the AG failover automatically if the cluster becomes unavailable? Or is the only failover for the AG manual regardless of the cluster state?
TIA
I would not configure the synchronous AG as auto failover - and I would probably set the node weight on that secondary AG node to 0 to make sure it doesn't count as quorum in the cluster. This is to insure that if that node crashed or was restarted or any other communication issue does not cause any issues for the FCI cluster.
Since this is for DR - i wouldn't set it up as synchronous because the secondary is in another site. You may find performance issues due to latency across the network. In my opinion - switching to DR systems should be a manual step that is determined based on the event and how long to recover the primary systems. If you truly need auto failover to DR and all components are setup/configured to support the auto failover - then you probably don't want an FCI configured as that is a more complex setup and configuration.
Instead - remove the FCI and add a synchronous AG group in site1 (first secondary with auto failover) and an asynchronous AG in site2 with manual failover. Either way - the DR secondary should not be synchronous and should be be configured as auto failover.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply