December 10, 2014 at 12:00 am
Comments posted to this topic are about the item Stairway to Always On Level 4: Analyse and Deploy a Windows Server Failover Cluster
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 25, 2015 at 5:53 am
Started glancing over this Stairway as it popped up on the main page this morning.
I do have a question concerning creating the underlying FCI to support an Always-On group, though. If I want to create an automatic FCI using Windows Server 2008 R2, I'll HAVE to use either node-and-disk, or node-and-file share, so that the cluster can maintain a quorum, correct? With the obvious issue of either the disk failing and taking quorum with it, or the file share being inaccessible for some reason.
Is it possible, with Windows Server 2012, to have a two-node FCI maintain quorum using the "Dynamic Node Weight" feature? IE, Node1 has a weight of 1, Node2 has a weight of 0, so we have quorum and everything is happy?
Thanks for a great article!
Jason
March 25, 2015 at 6:51 am
OK, I think I may have found my answer to the Server 2012 two-node.
Either an odd-number of nodes, or a file-share or disk majority quorum is still recommended, so it sounds like my thought might now work as hoped. Something I'll have to test out on my home lab.
February 29, 2016 at 9:23 am
can either Jason or Perry confirm the preferred quorum for WFC supporting always on? (OS2012R2 SQL2012)
cheers
george
---------------------------------------------------------------------
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply