I have an availability group with 3 replicas, as below:
Node1: Sync Commit, Automatic Failover
Node2: Sync Commit, Automatic Failover
Node3: (Sync or Async) Commit, <===================I do not want this node to become Primary replica
In the abovementioned list, I want to make use of Node3
, as dedicated backup node, which will never become the primary node(except when both Node 1 and Node2 are down), but is responsible for taking backups from my database(s). Is it possible to do this using AlwaysOn and Windows Failover Cluster?
I know that I can exclude nodes from participating in backup by configuring them in backup priority section, and I can exclude Node1
and Node2
, but this will not prevent Node3
, from being Primary node(Node3 can become as a primary node, whenever BOTH Node1 and Node2 are down). I think I should manage it via Windows Failover Cluster, but I do not know how...!
Event if I use AlwaysOn Availability Groups, how can I prevent Node3 from becoming a Primary node and also route the backups only to Node3, not any available secondary?