File Share Witness Resouces Errors in a SQL 2012 Alwayson Availability Group Environment

Hi I am getting the following error in WFC Manager and in my system event log:
Event ID1564:
File share witness resource 'File Share Witness' failed to arbitrate for the file share '\\SQL2012ClusterWitnessPath'. Please ensure that file share '\\SQL2012ClusterWitnessPath' exists and is accessible by the cluster.
Event ID 1069:
Cluster resource 'File Share Witness' of type 'File Share Witness' in clustered role 'Cluster Group' failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster
Manager or the Get-ClusterResource Windows PowerShell cmdlet.
Event ID 1205:
The Cluster service failed to bring clustered service or application 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
These errors showed up every hour on the hour and then suddenly stopped. I tried looking at the cluster.log file but there wasn't anything recorded there. The file share witness shows to be online and my AG did not fail over to another node.
The cluster has read and write permissions to the share. I did not find any error messages about the witness share on the remote server.
I am wondering what caused these series of events to occur?
Thanks.

Hi Kevin Ni,
Thanks for your reply. I have ran the validation test and I have 2 warnings. My environment has 2 nodes and 2 AG's with each node a failover for each AG. So that each node hosts and primary and a secondary of an AG. Both nodes are
on the same subnet. Here are the errors.
- Validate Multiple Subnet Properties
The RegisterAllProvidersIP property causes the network name to register all dependent IP addresses whether they are online or offline. Some DNS servers and clients in multi-subnet (multi-site) environments can identify the IP address that is in their subnet
and attempt connections only to that address. In such environments, it is usually best to set RegistrerAllProvidersIP to 1. This reduces DNS replication delays.
The RegisterAllProvidersIP property for network name 'Name: Listener1' is set to 1. For the current cluster configuration this value should be set to 0.
The RegisterAllProvidersIP property causes the network name to register all dependent IP addresses whether they are online or offline. Some DNS servers and clients in multi-subnet (multi-site) environments can identify the IP address that is in their subnet
and attempt connections only to that address. In such environments, it is usually best to set RegistrerAllProvidersIP to 1. This reduces DNS replication delays.
The RegisterAllProvidersIP property for network name 'Name: Listener2' is set to 1. For the current cluster configuration this value should be set to 0.
- Validate Network Communication
Node ONE.domain.com is reachable from Node TWO.domain.com by multiple communication paths, but each path includes network interface TWO.domain.com - TWO_NIC_Team. This network interface may be a single point of failure for communication within the
cluster. Please verify that this network interface
is highly available or consider adding additional networks or network interfaces to the cluster.
Node TWO.domain.com is reachable from Node ONE.domain.com by multiple communication paths, but each path includes network interface TWO.domain.com - TWO_NIC_Team. This network interface may be a single point of failure for communication within the
cluster. Please verify that this network interface
is highly available or consider adding additional networks or network interfaces to the cluster.
I have node TWO setup with NIC Teaming. Node ONE is also setup with NIC teaming but it also has a second IP address but the second IP address cannot communicate with node TWO.

Similar Messages

Will SCCM 2012 R2 , SCOM 2012 R2 and SCDPM R2 2012 support SQL 2012 AlwaysOn Availability Group ?

Will SCCM 2012 R2 , SCOM 2012 R2 and SCDPM R2 2012 support SQL 2012 AlwaysOn Availability Group ?

Hi,
It is listed here:
http://technet.microsoft.com/en-us/library/dn281933.aspx
Configuration Manager 2012 r2 and DPM 2012 r2 does not support AlwaysOn.
regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

SQL 2012 Database Availability Group - Force Automatic Failover

Hi All,
I'd appreciate some help in understanding the following scenario in my test environment.
I have created a DAG with 2 replica servers (both of which are HyperV VM's running W2012 Std).
From a client PC in my test lab, I can connect to the virtual listener of my DAG and confirm via the "select @@servername" command that I am connecting to the primary replica server.
Using the Failover Wizard, I can easily move to primary instance between my 2 nodes and the command above confirms that the primary replica server has changed. So far so good.
What I wanted to test, was what would happen to my DAG in the event of a complete loss of power to the server that was acting as the primary replica server. At first, I thought I would stop the SQL Server service on the primary server, but this did not result
in my DAG failing over to the secondary replica. I have found out that the only way I can do this is by effectively shutting down the primary server in a controlled manner.
Is there any reason why either stopping the SQL Server service on the primary replica, or indeed forcing a power off of the primary replica does not result in the DAG failing over to the secondary replica?
Thanks,
Bob

Hi,
I would verify if Database Availability Group means AlwaysOn Availability Group.
How did you set the FailureConditionLevel?
Whether the diagnostic data and health information returned by sp_server_diagnostics warrants an automatic failover depends on the failure-condition level of the availability group. The failure-condition level specifies what failure conditions
trigger an automatic failover. There are five failure-condition levels, which range from the least restrictive (level one) to the most restrictive (level five). For details about failure-conditions level, see:
http://msdn.microsoft.com/en-us/library/hh710061.aspx#FClevel
There are two useful articles may be helpful:
SQL 2012 AlwaysOn Availability groups Automatic Failover doesn’t occur or does it – A look at the logs
http://blogs.msdn.com/b/sql_pfe_blog/archive/2013/04/08/sql-2012-alwayson-availability-groups-automatic-failover-doesn-t-occur-or-does-it-a-look-at-the-logs.aspx
SQL Server 2012 AlwaysOn – Part 7 – Details behind an AlwaysOn Availability Group
http://blogs.msdn.com/b/saponsqlserver/archive/2012/04/24/sql-server-2012-alwayson-part-7-details-behind-an-alwayson-availability-group.aspx
Thanks.
Tracy Cai
TechNet Community Support
Hi,
Thanks for the reply.
It's an AlwaysOn Availability Group.
In my test lab, I have changed the quorum configuration to a file share witness and that has allowed an automatic failover when I turn the primary replica server off (rather than power it off).
I'll take a look at the links you provided.
Regards,
Bob

Orchestrator 2012 R2 on SQL 2012 SP1 Availability Group

Hi all,
I've recently setup a new install of SCOrch 2012 R2 on a SQL 2012 SP1 Availability Group. Everything went smooth and appears to be functioning correctly up until a failover occurs (manual or automatic). Once there is a failover between database
nodes, the Orchestrator servers (Mgmt and Runbook) lose connectivity to the database and will not reconnect until the services are restarted and then they work again.
Has anyone setup Orchestrator on an Availability Group and are you seeing similar issues from a failover?
Thanks!
Jon

Hi Jon,
has each member of the availability group the same master key to read encrypted data like passwords and the license code?
https://blog.uvm.edu/jgm/2013/05/28/sql-2012-tde-and-availability-groups/
Btw, if you still interested in a SAP IP:
http://www.sc-orchestrator.eu/index.php/integration-packs/integration-pack-fuer-sap-vip4sap
Regards,
Stefan
www.sc-orchestrator.eu ,
Blog sc-orchestrator.eu

SQL Server Alwayson availability groups automation

Hi all,
I had configured SQL Server always on availability groups on windows server 2012 and it was successful.
I’ve installed and successfully configured our SQL Server 2012 AlwaysOn 2-node windows cluster servers. I've gotten AlwaysOn working great, and our
Front End servers for the Intranet will be using SharePoint 2013. The glitch is that SharePoint 2013 is configured to add databases automatically to our SQL Server 2012 back end, but NOT to AlwaysOn. As we know “we must manually find, select, back-up and then
add those new databases individually to get them into AlwaysOn."
But wait; that can be quite a task, constantly checking the SQL Server back-end servers to see what databases were created, then having to add them
into AlwaysOn, 7/24!
Im looking for an automated script or process that will check for new databases, back those new databases up in FULL mode, (for being added to AlwaysOn, of course) then
add those databases to Always On, all automatically.
Requirements:
Every time the newly created or added databases should be full backed up once in the shared location with automated script.
Newly created database should be added into always on group and should be added to available replica automatically with the TSQL script
Regards,
SQL LOVER.

awaiting for responses.
Kindly help the bewlo request.
Newly created database should be added into always on group and should be added to available
replica automatically with the TSQL script and perform restoration.
There is no out of the box solution for this. You may want to created a SQL Job (PowerShell) which can detect database which is newly created and perform steps to add new database to AG.
1. take full backup.
2. Take log backup.
3. restore then on secondary.
4. Add database to AG
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

DPM 2012 SP1 and SharePoint 2013 on a SQL 2012 AlwaysOn AG

I am trying to protect a new SharePoint Foundation 2013 farm with it's databases stored on an SQL 2012 AlwaysOn Availability Group. I've run configureSharePoint.exe -EnableSharePointProtection on my WFE and SharePoint shows up in DPM when I try to
add it to a protection group. But I get the 32008 referenced here: http://support.microsoft.com/kb/970641 when trying to select the farm to back up.
If I run ConfigureSharePoint.exe -resolveallSQLAliases on the WFE it doesn't return anything.
I'm directly backing up databases on the SQL 2012 server, but not any of the SharePoint DBs.
K

Hi,
I'm having some trouble understanding what I'm seeing in the writer output from the WFE server. Specifically the machine names that the writer is reporting.
If you look in the wfewtiters.txt, What is the machine that ends in 02 ? Is that a physical machine or an alias ?
The machine ending in 06 is the Secondary SQL Server and that is what the Sharepoint writer is pointing to.
The WFE VSS Sharepoint writer shows this for two content DB’s
* WRITER "SharePoint Services Writer"
  - Writer ID   = {da452614-4858-5e53-a512-38aab25c61ad}
  - Writer instance ID = {c0c46d7b-1c01-44bd-8353-e3433f5b8f07}
  - Supports restore events = TRUE
  - Writer restore conditions = VSS_WRE_ALWAYS
  - Restore method = VSS_RME_RESTORE_AT_REBOOT_IF_CANNOT_REPLACE
  - Requires reboot after restore = FALSE
  - Excluded files:
+ Component "SharePoint Services Writer:\XXXX02\WSS_Content_at.contoso.local"
- Name: WSS_Content_at.Contoso.local
- Logical path: XXXX02
- Full path: \XXXX02\WSS_Content_at.Contoso.local
- Caption: Content Database WSS_Content_at.Contoso.local
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\YYYY06\YYYY06\WSS_Content_at.contoso.local"
                                + Component "SharePoint Services Writer:\XXXX02\WSS_Content_fw.Contoso.local"
- Name: WSS_Content_fw.contoso.local
- Logical path: XXXX02
- Full path: \XXXX02\WSS_Content_fw.Contoso.local
- Caption: Content Database WSS_Content_fw.Contoso.local
- Type: VSS_CT_DATABASE [1]
- Is selectable: TRUE
- Is top level: TRUE
- Notify on backup complete: FALSE
- Paths affected by this component:
- Volumes affected by this component:
- Component Dependencies:
- Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\YYYY06\YYYY06\WSS_Content_fw.contoso.local"
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Backup Maintenance Plan on SQL AlwaysOn Availability Group Secondary Read-Only node

I have 3 node SQL 2012 AlwaysOn Availability nodes with the 3rd node as Read-Only.
The backup job within SQL Maintenance plan is failing with the following error:
Failed:(-1073548784) Executing the query "declare @backupSetId as int
select @backupSetId =..." failed with the following error: "Cannot open backup device 'C:\\SQLDBName_backup_2014_06_08_170156_9292095.bak'. Operating system error 2(The system cannot find the file specified.).
VERIFY DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
I have verified the SQL AlwaysOn Backup preference to be "Prefer Secondary"
Is there any special steps/settings I need to do to setup and run the backups using maintenance plan in SQL AlwaysOn?

Hi,
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Thanks.
Tracy Cai
TechNet Community Support

SQL 2012 AlwaysON High Availability for SharePoint 2013

Our Company have 2 Webfront Servers for Sharepoint 2013 and one Database SQL 2012 Server.
We got one more Server & we don't have Storage so need to configure Always On.
There are Some Confusions:
1- Database Server is in production, so how much down time required to Achieve the AlwaysOn?
2- What are the Changes need to be done on Production Server?
3- What are the Steps to be followed While Configuring new Database Server?
Regards,

Hi Genius1985,
According to your description, you want to configure a SQL Server 2012 AlwaysOn Availability Group for your database, right?
Question 1: Database Server is in production, so how much down time required to achieve the AlwaysOn?
There is no a certain downtime for AlwaysOn, it depends on the configuration of our AlwaysOn Availability Group, normally it can be several seconds or minutes. In order to understand why there is downtime for SQL Server with Microsoft Clustering, please refer
to the following article:
http://www.mssqltips.com/sqlservertip/1882/understanding-why-there-is-still-downtime-for-sql-server-with-microsoft-clustering/
Question 2 and 3: What are the Changes need to be done on Production Server? What are the Steps to be followed While Configuring new Database Server?
Since AlwaysOn Availability Groups require a Windows Server Failover Cluster, we first need to add the Windows Failover Cluster Feature to all the machines running the SQL Server instances that we will configure as replicas.
Once the Windows Server Failover Cluster has been created, we need to proceed with enabling the AlwaysOn Availability Groups feature in SQL Server 2012. This needs to be done on all of the SQL Server instances that we will configure as replicas in our
Availability Group.
For more details about Step-By-Step: Creating a SQL Server 2012 AlwaysOn Availability Group, please refer to the following article:
http://blogs.technet.com/b/canitpro/archive/2013/08/20/step-by-step-creating-a-sql-server-2012-alwayson-availability-group.aspx
If you have any question, please feel free to let me know.
Regards,
Jerry Li

Is it possible to move to Alwayson Availability groups from existing sql server FCI ?

Is it possible to move to Alwayson Availability groups from? existing sql server FCI ?
If yes, how to move and what are the pre-requisites?

Hi Rahul,
Based on your description, we need to verify if you want to move from Failover Cluster Instances(FCI) and database mirroring to SQL Server Alwayson Availability groups. If so, it is possible.
You can review the following articles to get more detailed information about this kind of migration.
How To: Migrate from Failover Cluster Instances and Database Mirroring to SQL Server AlwaysOn
– Part 1
How To: Migrate from Failover Cluster Instances and Database Mirroring to SQL Server AlwaysOn
– Part 2
Thanks,
Lydia Zhang

2012 SQL AlwaysOn Availability Group - JDBC re-connection not happening in case of Multisubnet failover

Hi There,
Having some problem with MultiSubNet AG failover re-connection using SQL JDBC driver 4. Details given below.
SETUP:
We have a three node 2012 Windows Server Cluster, on top it we have 2012 SQL Sever AlwaysOn Availability Group.
Two nodes are in one subnet and other in a different subnet to make this as a multisubnet AlwaysOn AG.
An AG Listener is configured with a DNS name and two VIP assigned (For two subnet) to it. We were able to failover from one subnet to other using the SQL Studio successfully.
NEED:
We have a java application which will be connected to AG Listener name. In case of failover, automatic re-connection to DB/AG Listener name should happen.
For this we use "sqljdbc4.jar" and added
'multiSubnetFailover=true' in our connection string. The connection String is given below.
cURL="jdbc:sqlserver://testsqlag:1433;databaseName=SalesDB;multiSubnetFailover=true;loginTimeout=200;applicationName=MyApp";
THE PROBLEM:
In case of AG failover, driver is not trying to re-connect to the AG Listener name. Not sure how to make it work.
Is this supported in SQL Server 2012 ?
Thanks,
Krishna.

Hi Sean,
Thanks for your answer.
I looked at the link earlier, but it was not very clear that, whether the mssql jdbc driver will automatically re-connect to AG Listener name in case of failure of Primary replica which will result in Multisubnet failover. Pasted the confusing statements
from the link
http://msdn.microsoft.com/en-us/library/gg558121(v=sql.110).aspx.
Also, because a connection can fail because of an availability group failover, you should implement connection retry logic, retrying a failed connection until it reconnects.
Connecting With MultiSubnetFailover :
During a multi-subnet failover, the client will attempt connections in parallel. During a subnet failover, the Microsoft JDBC Driver for SQL Server will aggressively retry the TCP connection.
Thanks,
Krishna.

AlwaysOn Cluster reboot due to file share witness unavailability

Hi Team,
Anyone came across this scenario in AlwaysOn Availability Group (two node), file share witness times out and RHS terminate and cause the cluster node to reboot. File share witness is for continuous
failover and if the resource is unavailable my expectation was that it should go offline and should not impact Server or Sql Server. But its rebooting the cluster node to rectify the issue.
Configuration
Windows Server 2012 R2 (VMs) - two node, file share witness (nfs)
Sql Server 2012 SP2
Errors
A component on the server did not respond in a timely fashion. This caused the cluster resource 'File Share Witness' (resource type 'File Share Witness', DLL 'clusres2.dll') to
exceed its time-out threshold. As part of cluster health detection, recovery actions will be taken. The cluster will try to automatically recover by terminating and restarting the Resource Hosting Subsystem (RHS) process that is running this resource. Verify
that the underlying infrastructure (such as storage, networking, or services) that are associated with the resource are functioning correctly.
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.
Thanks,
-SreejitG

Thanks Elden, We were using DFS name for the file share! We gave the actual file share name and looks good now.
Few interesting facts, the failure happens exactly between window 12:30 PM to 1:30 AM and it never recorded any error specific to DFS! Not sure if there was any daily maintenance or task happens during the window pertaining to DFS.
+ DFS is not supported or recommended by Microsoft
Do not use a file share that is part of a Distributed File System (DFS) Namespace.
https://technet.microsoft.com/en-us/library/cc770620%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396
Thanks,
-SreejitG

Exchange Server CCR 2007 unable to see the File Share Witness resulting in mailbox failover ?

Hi people,
Here's my Exchange Server 2007 SP3 in the ideal and normal situation:
Mailbox Server (CCR – Stretched Cluster) Nodes
PRODEXMBX01-VM (Active Mailbox, Quorum) – 10.1.1.53
DREXMBX01-VM (Passive mailbox) – 192.168.1.88
Hub Transport and Client Access Server Nodes
PRODEXHTCAS02-VM – 10.1.1.54
PRODEXHTCAS03-VM (FSW holder) – 10.1.1.55
DREXHTCAS02-VM – 192.168.1.89
Saturday early morning, for some unknown reason the Active Mailbox Server (PRODEXMBX01-VM)
cannot access or see the FSW on the HT server PRODEXHTCAS03-VM, thus
the mailbox gets failover to the DR Mailbox server (DREXMBX01-VM).
Here’s the Events logged:
Log
Name:      System
Source:        Microsoft-Windows-FailoverClustering
Event ID:      1564
Task Category: File Share Witness Resource
Level:Critical
User:          SYSTEM
Computer:      PRODEXMBX01-VM.domain.com
Description:
File
share witness resource 'File Share Witness (\\PRODEXHTCAS03-VM \FSM_DIR_ExMbxCluster01)'
failed to arbitrate for the file share '\\ PRODEXHTCAS03-VM \FSM_DIR_ExMbxCluster01'.
Please ensure that file share '\\ PRODEXHTCAS03-VM \FSM_DIR_ExMbxCluster01'
exists and is accessible by the cluster.
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Event ID:      1177
Task Category: None
Level:       Critical
User:     SYSTEM
Computer:PRODEXMBX01-VM.domain.com
Description:
The Cluster service is shutting down because quorum was lost.
This could be due to the loss of network connectivity between some or all nodes
in the cluster, or a failover of the witness disk.
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 adapter. Also check for failures in any other network components to
which the node is connected such as hubs, switches, or bridges.
So I had to perform manual failover back from DR to production so that both Active mailbox and the Quorum
are held by the Production Mailbox server (PRODEXMBX01-VM).
On Sunday Morning, the Event ID Critical 1564 occurred again thus causing only the quorum only to failover
to the DR mailbox server (DREXMBX01-VM) but the Active mailbox role is still held by the Production Exchange server (PRODEXMBX01-VM).
So now the situation is like the following:
Mailbox Server (CCR – Stretched Cluster) Nodes
PRODEXMBX01-VM (Active Mailbox) – 10.1.1.53
DREXMBX01-VM (Passive mailbox, Quorum) – 192.168.1.88
Hub Transport and Client Access Server Nodes
PRODEXHTCAS02-VM – 10.1.1.54
PRODEXHTCAS03-VM (FSW holder) – 10.1.1.55
DREXHTCAS02-VM – 192.168.1.89
So what causing the mailbox servers unable to contact the File Share Witness?
/* Server Support Specialist */

Did you check the blog above?
The account used in the clustered machine should have access to
\\PRODEXHTCAS03-VM\FSM_DIR_ExMbxCluster01. Please check the permissions. Try giving full permission to admins as well (just to try)
MAS
I've followed this (http://technet.microsoft.com/en-us/library/bb124922(v=exchg.80).aspx) instruction and there is no mentioning other than the Cluster Service Account.
/* Server Support Specialist */

Can I Load Balace a file share witness?

Hi,
I got AlwaysOn Availability Group working with a file share witness.
The file share reside on a server in my network, hence it's a single point of failure.
Can I put a load balancer endpoint for the file share path when configuring the quorum? (After the configuration I will manually copy the files from file share A to file share B, so they will be the same).
My concern is that I don't know if the quorum configuration changes(making the file shares not the same) without me initiating that change(failover or some other event).
Thank You!
(Originally I posted that question in "SQL Server High Availability and Disaster Recovery", but I was asked to move it to here.)

David,
on one hand you say that it is not a single point of failure, but on the other hand you say "or if you have other nodes fail in addition to the FSW". That means that if the FSW is offline I can't have automatic failover, a thing which puts my application
in danger since I relay on automatic failover.
For me not having automatic failover is very bad.
My network is in Azure, the FSW is on one of my web servers(web servers and the database cluster are on different cloud services), since I'm using availability sets I know that at least one web server will be up at any given time. It is possible
that Microsoft will do maintenance or there will be a failure on the infrastructure and the FSW plus one of my sql nodes will be down, I won't have automatic failover in that case.
If you got a solution for me I will be happy to implement it.
Thank You.

Quorum location for Failover cluster file share witness

So, I've done quite a bit of searching for what I'm about to propose and I've been able to find nothing.
I currently have a multi site failover cluster hosting separate 2-node SQL clusters at each site connected through an Availability Group. For the failover cluster I am using a file share witness hosted on a server at the primary site. Both sites
are built entirely on vSphere 5.5 and have full replication for the production servers. If the primary site goes down (disaster), I'll need to force quorum in the secondary site to a new file share witness.
Well, I got to thinking...
Why not just replicate the server hosting the file share? I completely understand the reasoning behind not putting the file share witness on DFS, but a replicated virtual server, why not? If the primary site fails, the replicated server hosting
the file share witness is brought online with the rest of the production servers in the DR site. In that case, the only thing that changes is the server IP address, but ultimately, the server name and share where quorum is hosted all stays the same.
Ultimately this prevents needing to find a 3rd geographical/cloud location to host a quorum/witness at. I can't imagine it's this "simple", but maybe it is. If this is possible, and there's not something I'm missing, this essentially
makes the quorum file share witness site agnostic, meaning it could live or be moved anywhere that replication is allowed.
Ideas, thoughts? Am I missing something?
Thanks!
Chris Miller

Most likely it would be better to put this question to the High Availability forum -
https://social.technet.microsoft.com/Forums/en-US/home?forum=winserverClustering
But, might need a more complete definition of your environment. Are you saying that you have multiple 2-node clusters, each with one node in the primary and the second node in the DR site? And you have a single file share server located in primary that
is used to host the file share witnesses for all these clusters? You want to use VMware to replicate the file share server to the DR site so that it can be made available should the primary site fail?
It should work, but it will not be automatic. After all, the replicated VM will need to be brought online at the DR site so the SQL cluster will recognize it. That is not an automatic process. So the cluster will be down until
you bring the file share server online so it can be recognized. Not a whole lot different that simply forcing the DR SQL host to run without quorum.
. : | : . : | : . tim

Configuring quorum file share witness access denied

in failover cluster administrator, when I try to configure the quorum for file share witness, it keeps coming up and say access denied.
any idea? I created the share as a domain admin and I am running the failover cluster admin as a domain admin

Hi JonDoe321,
From the error information It must the file share folder don’t meet the permission requirement, For the folder that the file share uses, make sure that the administrator has
Full Control share and NTFS permissions, grant the CNO on the file share with full control right, you can refer the following KB to realize the detail requirement.
Failover Cluster Step-by-Step Guide: Configuring the Quorum in a Failover Cluster
http://technet.microsoft.com/zh-cn/library/cc770620(v=ws.10).aspx#BKMK_requirements
More related third party article:
How to configure a Node and File Share Majority quorum
http://www.howtonetworking.com/server/cluster12.htm
I’m glad to be of help to you!
*** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control
these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the
use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. ***
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

File Share Witness Resouces Errors in a SQL 2012 Alwayson Availability Group Environment

Similar Messages

Maybe you are looking for