Windows 2012 R2 Failover Cluster and Availability Group resource

Xain deSleena 1 Reputation point

I have a 2 node WFSC 2012 R2 which uses a File Share Witness (FSW) for Quorum purposes.
I manage the cluster and have found that the FSW is a resource to the single Availability Group (AG) Role.
I cannot figure out how the FSW became a resource to the AG as I have other similar WFSC which do not have the FSW as a resource.
You also cannot add it seems a FSW to an AG as a resource.
I want to remove the FSW resource from the AG because some time recently the FSW failed and this caused the AG to go into Pending state and would not come online.
Does anyone know why an FSW would be a resource to an AG and any issues if I remove the FSW from the AG.
I believe the FSW will still remain as a resource as part of the cluster core resources group.

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
11,593 questions
Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
912 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Limitless Technology 38,771 Reputation points

    Hi @Xain deSleena

    There is no requirement for the FSW to be a resource of the AG and you should see no detrimental affect from removing it. The FSW will remain a resource of the CCRG.

    Here is a guide I have used in the past for deploying an FSW:

    An FSW can be used on multiple clusters for high availability.

    I hope this answers your question.


    --If the reply is helpful, please Upvote and Accept as answer--

    0 comments No comments