we have SQL AG role set up on Windows 2012R2 up OS. When SQL AG failovered, how can you sure that
WFCS caused and not AG role?
We need to start from SQL server error log and windows cluster log to analysis why SQL AG failover. The log will tell you that SQL or windows cause this issue.
Generate and analyze the CLUSTER.LOG for an Always On availability group
Use the cluster /log /g command at the command prompt. This command generates the cluster logs to the \windows\cluster\reports directory on each WSFC node. or use the Get-ClusterLog PowerShell cmdlet. Refer to MS document Generate and analyze the CLUSTER.LOG for an Always On availability group.
If the response is helpful, please click "Accept Answer" and upvote it, as this could help other community members looking for similar thread.
Windows Server Failover Cluster (WSFC) A WSFC is a group of independent servers that work together to increase the availability of applications and services.
An Always On Failover Cluster Instance (FCI) is a SQL Server instance that is installed across nodes in a WFCS. This type of instance depends on resources for storage and virtual network name.
High availability for an Always On solution is accomplished through proactive health monitoring of physical and logical WFCS cluster resources, together with automatic failover onto and re-configuration of redundant hardware. A system administrator can also initiate a manual failover of an availability group or SQL Server instance from one node to another.
Hope this answers all your queries, if not please do repost back.
If an Answer is helpful, please click "Accept Answer" and upvote it : )
16 people are following this question.