December 18, 2014 at 2:54 am
Hi all I would like to know whether you can configure
HAGAlwayson without wfc shared storage???
what quorum type setting is needed???
December 18, 2014 at 3:13 am
Depends
Are you talking about Always On Windows Clustering or Always On Availability Groups?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 18, 2014 at 5:00 am
sej2008 (12/18/2014)
Hi all I would like to know whether you can configureHAGAlwayson without wfc shared storage???
what quorum type setting is needed???
To configure a Windows Server Failover Cluster using a disk based quorum, you will need shared storage. You could use either a fileshare witness or majority node set, which will remove the need for a disk based quorum.
To setup and configure an AlwaysOn Availability group does not require SQL Server instances that are clustered and using shared storage, in fact, exactly the opposite. AO groups are designed to remove the dependency on shared storage.
See more in my stairway series starting at this link[/url]
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
December 19, 2014 at 12:04 am
i am talking abt Sql 2012 High Availability group that requires
wfc.
December 19, 2014 at 12:07 am
I did configure WFC on win 2008 R2(2 nodes) without any Quorum setting
(by default it took Node Majority) and Cluster gave different errors...
December 19, 2014 at 1:38 am
sej2008 (12/19/2014)
i am talking abt Sql 2012 High Availability group that requireswfc.
SQL Server failover clustering or Always On Availability Groups? Your posts are not clear as to which you're using. Both are HA, both use WFC but other than that are very different
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 19, 2014 at 4:54 am
sej2008 (12/19/2014)
i am talking abt Sql 2012 High Availability group that requireswfc.
If you're planning AlwaysOn availability groups, why are you concerned with shared storage, it's not required and in fact i wouldnt recommend it at this stage.
Let's start at the beginning
How many nodes are in the cluster?
how many standalone instances do you have installed and to which nodes?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
December 19, 2014 at 11:49 am
I am learning both simultaneously actually.
December 19, 2014 at 11:55 am
Well to start with I have three nodes once acts as DC and other two for cluster.
I have stand alone Sql on the both nodes which are participating in wfc.
December 19, 2014 at 11:59 am
sej2008 (12/19/2014)
I am learning both simultaneously actually.
That'll get you a whole lot confused, start with this[/url] and this[/url] and this[/url]
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
December 19, 2014 at 11:20 pm
Hi again.
Well Thanks for your answer again.
But I feel I am not able to make my point clear.we are beating round the bush.
I am learning Sql Clustering and new concept of Always on also.
Both requires proper configuration of windows failover cluster.
The question is I am not able to configure windows Failover
cluster properly using ISCSItarget software with shared storage that is disk witness.
From your post I understand I need to configure ISCSI network,how to do that?????
I went through links given by you but it does not give any steps to configure ISCSI network adapter.:w00t:
I have also used two NIC on nodes but still getting error of single point failure,how cluster will automatically understand the ISCSI network config.....somewhere my network config is going wrong and not a network person at all............
I have config public and private NIC and given you my config in earlier post..pls tell me abt ISCSI NIC config????
Another concept I am learning is Always ON that uses Windows failover clustering but with fileshare storage...that steps I tried to do but again with error:w00t:
I am not using starwind...
so I am like back to square one though I am trying hard on it...
December 21, 2014 at 2:58 am
sorry the link you have given is much in depth but
very confusing...
when you AO in sql 2012 does not use ant SAN storage
the article is still using file share as a storage...
December 21, 2014 at 4:36 am
you're the only one who finds it confusing!!
As I said, learn to walk before you run, if you check those links they are all part of a multi part article.
This[/url] details how to use the iSCSI initiator, scroll down to the section "Attaching the iSCSI LUNs"
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
December 21, 2014 at 4:42 am
sej2008 (12/19/2014)
The question is I am not able to configure windows Failovercluster properly using ISCSItarget software with shared storage that is disk witness.
From your post I understand I need to configure ISCSI network,how to do that?????
One of the links shows you how to use a fileshare witness, which does not require shared storage
sej2008 (12/19/2014)
I went through links given by you but it does not give any steps to configure ISCSI network adapter.:w00t:
Read through all the related links too, they're all multi part articles. This[/url] may help too
sej2008 (12/19/2014)
I have also used two NIC on nodes but still getting error of single point failure,how cluster will automatically understand the ISCSI network config.....somewhere my network config is going wrong and not a network person at all............I have config public and private NIC and given you my config in earlier post..pls tell me abt ISCSI NIC config????
iSCSI traffic should be pushed down a separate network. When disabling NetBIOS resolution and dns registration the cluster service will identify the NIC as not suitable for cluster communication.
sej2008 (12/19/2014)
Another concept I am learning is Always ON that uses Windows failover clustering but with fileshare storage...that steps I tried to do but again with error:w00t:I am not using starwind...
so I am like back to square one though I am trying hard on it...
Fileshare witness is covered in the links I have posted
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply