Question on Quorum : Windows Server 2012 R2 + SQL 2014 AlwaysOn AG

os on nodes : windows server 2012 r2

sql on nodes : sql server 2014 cu2

2 cluster nodes in primary data center , alwayson ag doing sync transfer between these nodes auto failover.

2 cluster nodes in dr data center(different subnet) , alwayson ag doing async transfer between primary replica , these nodes manual failover.

as multi sub-net cluster giving dr nodes 0 vote. 2 nodes on primary dc has votes , file share on primary dc has vote.

if primary dc gone,then should re-assign node votes 2 nodes in dr site , again manually configure file share witness , give vote?

whats best strategy here? recommendation highly appreciated.

thank you,

anup,

think if have network issues between primary dc , dr dc. dr node might think…hey, i’m 1 running now. can take resources. not want nodes in secondary site contribute decision take cluster offline when there nothing wrong primary site. mean dynamic quorum smart enough handle situation?

is smart enough on it's own? no. that's why has determine site want stay up.

if you're using dynamic quorum, new property introduced called "lowerquorumprioritynodeid" set @ cluster level. give node of 1 , 1 of secondary site servers. set fileshare witness (if possible) odd vote , make sure both sites can see equally well. set property on cluster node on secondary site.

http://technet.microsoft.com/en-us/library/dn265972.aspx#bkmk_tiebreak

assume fileshare goes down , have 2 nodes @ local site , 2 nodes @ dr site. suddenly, communicates between 2 severed. if have dynamic quorum set , property mentioned above, secondary site shut down , local site stay secondary site set lower precedence.

please note, reason brought because you're on windows server 2012r2 when first introduced.

-sean

---

sean gallardy | blog | microsoft certified master

Windows Server  >  High Availability (Clustering)