February 5, 2013 at 6:54 am
Hi All
Imagine the following set up for an AlwaysOn availability group using FCI.
I have 3 nodes ServerA, ServerB, ServerC
Each server has the following local drive storage.
C: = 80GB
In addition, ServerA and ServerB have the following shared LUNs attached from a SAN - For Database files
M: = 500GB
N: = 500GB
I create a windows cluster titled Cluster1 and each server is joined to this cluster.
I install a clustered SQL Server instance using virtual network name SQLCluster1 on the 2 nodes ServerA, ServerB.
I install a non clustered instance of SQL Server on ServerC
I am planning on setting up an AG between SQLCluster1 and ServerC
My Question: Server1 and ServerB have Shared Storage, how do I prevent ServerC from seeing that storage. When I run the validation, won't the cluster try to failover that storage to ServerC?
Thanks
February 5, 2013 at 7:59 am
Firstly, read my article at this link[/url] for more info on AO groups and FCI's
SQLSACT (2/5/2013)
My Question: Server1 and ServerB have Shared Storage, how do I prevent ServerC from seeing that storage.
Don't present the storage to server C!
SQLSACT (2/5/2013)
When I run the validation, won't the cluster try to failover that storage to ServerC?Thanks
Skip the storage tests, this is valid with AO groups and FCIs
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 5, 2013 at 10:08 am
Perry Whittle (2/5/2013)
Firstly, read my article at this link[/url] for more info on AO groups and FCI'sSQLSACT (2/5/2013)
My Question: Server1 and ServerB have Shared Storage, how do I prevent ServerC from seeing that storage.Don't present the storage to server C!
SQLSACT (2/5/2013)
When I run the validation, won't the cluster try to failover that storage to ServerC?Thanks
Skip the storage tests, this is valid with AO groups and FCIs
Thanks Perry
Is my order of steps correct?
February 7, 2013 at 1:41 am
Hi Perry
I want to make sure that I approach this the correct way
In your opinionm what is the best way to configure the cluster:
>> First create a 2 node cluster and then add the 3rd node
>> Or...Create a 3 node cluster right off the bat?
Also, I've never skipped the storage tests when validating my cluster config - Excluding the storage tests won't bring my SQL installation to a halt?
Thanks
February 12, 2013 at 12:53 pm
Hi
You can create a 2 node cluster and then add the Third one. While adding the Third one to the cluster please uncheck the option to "Add the eligible storage" option in the Add node wizard.
Regards
Srikanth Reddy Kundur
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply