I have a database server setup where there are three SQL Server database instances set up on three nodes of a Windows Server Failover Cluster (WSFC).
The sysadmin, who is responsible for the Windows Cluster, is accusing me of manually setting the primary cluster node as something other than what it is.
Can failing Availability Groups over to secondary replicas, to include during reboots when they automatically take over, also cause the underlying Windows Server Failover Cluster to switch the primary node and not switch it back?
This has the potential to become a distracting issue, keeping me from getting work done. I'm hoping to be pointed in the right direction to keep this from happening again.