SQL Server Always on Three node Cluster We have two data centers DC1 and DC2


The distance between two DC's are about 200 miles.  
DC1 - has two nodes  
DC2 - has 1 node with SQL 2012 Always-On AG and windows 2008R2
Node majority cluster
Two nodes on DC1 are primary.  
Failovers are always between the two nodes on DC1. 
DC2 is only for backups.


There is intermittent network issue between two DC1 and DC2, whenever there is network glitch causes the databases on DC2 to restart which kills the full backup job that was running.  

One of our DBA suggesting to create a file share witness and remove vote to the node on DC2, then change quorum settings from node majority to node and file share majority.

My Question is..

If we create file share witness and change quorum setting will fix our backup issue? I am not clear how the full backup job continue running when there is network glitch and the all the nodes are in cluster
Can any one advise how do i over come from this situation. Network team said they do not have any fix from their end.

I researched on this and found below link which looks similar but i can not correlate with my issue.

SQL Server Always On Node and File Share Majority
Regardless of the quorum model, if a SQL Server 2012 secondary becomes disconnected, it will go offline.

This was changed in SQL Server 2014.


  When disconnected from the primary replica or during cluster quorum
  loss, readable secondary replicas now remain available for read
  workloads.


What's New for SQL Server 2014