September 29, 2023 at 4:25 am
Hi.
Two node windows clusters Node1 and Node2 and configured alwayson availability group.
Will it possible to Alwyason availability group can set primary role permanently any one of the node?
Thanks
September 29, 2023 at 8:26 am
If you set failover to manual, then one replica will always be primary unless you manually force a failover.
Kind of negates the point of having an AG if you're removing the HA/DR functionality, you probably have a valid reason for it, but if I wanted one replica to always be primary, then I wouldn't of chosen AG's as the technology, would have gone log shipping as its easier to maintain than an AG and you don't have the nuances of keeping a WSFC healthy, and lease timeouts etc etc etc to contend with.
September 29, 2023 at 2:11 pm
Thank you for you reply.
Reason behind is every night whole VM backup taken and backup completion time 2.5 Hours ,
during backup time AG got failover automatically to node2 due to network ping lost for more than 20 seconds. after failover AG listener and cluster objects are online and healthy state. but AG listener not pinging.
AG listener got pinging after again manual failover node1. following errors found at cluster event logs during VM backup time.
The cluster Resource Hosting Subsystem (RHS) process was terminated and will be restarted. This is typically associated with cluster health detection and recovery of a resource. Refer to the System event log to determine which resource and resource DLL is causing the issue.
Cluster service failed to start because this node detected that it does not have the latest copy of cluster configuration data. Changes to the cluster occurred while this node was not in membership and as a result was not able to receive configuration data updates
Cluster node 'Node1' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Cluster node 'Node2' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
September 29, 2023 at 2:24 pm
Increase the lease timeout, or change your HA/DR technology or change your backup technology.
but if after failover the listener isn’t working you got bigger issues you need to fix and fix now as when the proverbial hits the fan and the listener doesn’t work, well your up the creek without a paddle.
additionally if the cluster rhs is terminating then again you have deeper issues as if the cluster goes down due to backup then your ag will go down also.
i suggest you seriously look into everything you have here as it all sounds wrong on so many levels.
September 29, 2023 at 4:56 pm
Thank you for you reply.
Reason behind is every night whole VM backup taken and backup completion time 2.5 Hours ,
during backup time AG got failover automatically to node2 due to network ping lost for more than 20 seconds. after failover AG listener and cluster objects are online and healthy state. but AG listener not pinging.
AG listener got pinging after again manual failover node1. following errors found at cluster event logs during VM backup time.
The cluster Resource Hosting Subsystem (RHS) process was terminated and will be restarted. This is typically associated with cluster health detection and recovery of a resource. Refer to the System event log to determine which resource and resource DLL is causing the issue.
Cluster service failed to start because this node detected that it does not have the latest copy of cluster configuration data. Changes to the cluster occurred while this node was not in membership and as a result was not able to receive configuration data updates
Cluster node 'Node1' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
Cluster node 'Node2' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
As Ant-Green said, you have multiple issues that need to be addressed. Changing the failover to manual will not correct your issue. The cluster appears that it will go offline even if you set it to manual.
First, how is your quorum set up, if you have one? If you are using a cluster disk as a quorum, then your cluster will have no quorum and it will go offline.
Second, what are you using to backup the VM? Is it VMWare snapshots? I think you need to quiescese the snapshot.
Third, along with the quorum setup, you need to adjust your lease timeout, and cluster health check timeout to higher values.
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
December 10, 2023 at 1:41 am
This was removed by the editor as SPAM
December 10, 2023 at 1:42 am
This was removed by the editor as SPAM
December 10, 2023 at 1:43 am
This was removed by the editor as SPAM
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply