September 23, 2015 at 10:37 am
"If we fail over a SQL AG group on a failover cluster from one node to another making the secondary the new primary, is there any reason why we would have to fail it back over to the old primary node?"
September 23, 2015 at 10:52 am
Not necessarily, unless you have secondary copies as read-only / no.
Example under the readable secondary if you have both primary/secondary to readable secondary = YES
when ever you need to failover (whether it is automatic or manual) the primary becomes secondary and vice versa.
This would allow regardless of which copy is primary/secondary to allow users to continue to work seamlessly while connecting via the group listner name.
September 24, 2015 at 9:12 am
balcock (9/23/2015)
"If we fail over a SQL AG group on a failover cluster from one node to another making the secondary the new primary, is there any reason why we would have to fail it back over to the old primary node?"
you may have a preferred node in a preferred datacentre, in this case you may want to
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply