SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


multiple instance sql cluster with different windows configuration


multiple instance sql cluster with different windows configuration

Author
Message
deep_kkumar
deep_kkumar
SSC Veteran
SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)

Group: General Forum Members
Points: 263 Visits: 756
We have a two node cluster. In order to utilize the max resources we are planning to add more instances to this cluster by adding few more nodes. Let us assume--

server A - cluster node--100 GB ram and 24 core cpu (active)
server B - cluster node--100 GB ram and 24 core cpu( active)
server C - new node -- 50 GB ram and 12 core cpu( passive)
server D - new node -- 50 GB ram and 12 core cpu (passive)

What we are planning to do is to run sql instance of server C and D on server B and make use of the resources. When server A fails we need it to failover to server B and if this happens we can manually failover the two instances running on server B to node C and node D respective. Is this possible? I know in cluster all the nodes should have same resources. Need suggestions?
muth_51
muth_51
SSC Eights!
SSC Eights! (933 reputation)SSC Eights! (933 reputation)SSC Eights! (933 reputation)SSC Eights! (933 reputation)SSC Eights! (933 reputation)SSC Eights! (933 reputation)SSC Eights! (933 reputation)SSC Eights! (933 reputation)

Group: General Forum Members
Points: 933 Visits: 2905
Not sure. Wait for Perry's reply.
Sailorking
Sailorking
SSC Rookie
SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)

Group: General Forum Members
Points: 27 Visits: 126
SQL Cluster 2008 need not the exact same hardware but rather compatible hardware. I'm currently running a 2 node cluster with Node A (64proc, 256GB) the primary and Node B (24proc, 128GB) as the passive. Now where this becomes a problem is if Node A crashes can Node B handle the load? In our environment it can but queries do become slower and its okay for us because it is only temporary until we get Node A back up.

It all depends on your load and can the weakest link (Node in this case) hold all your resources?

-king
Perry Whittle
Perry Whittle
SSCoach
SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)

Group: General Forum Members
Points: 19704 Visits: 17239
deep_kkumar (4/1/2013)
We have a two node cluster. In order to utilize the max resources we are planning to add more instances to this cluster by adding few more nodes. Let us assume--

server A - cluster node--100 GB ram and 24 core cpu (active)
server B - cluster node--100 GB ram and 24 core cpu( active)
server C - new node -- 50 GB ram and 12 core cpu( passive)
server D - new node -- 50 GB ram and 12 core cpu (passive)

What we are planning to do is to run sql instance of server C and D on server B and make use of the resources. When server A fails we need it to failover to server B and if this happens we can manually failover the two instances running on server B to node C and node D respective. Is this possible? I know in cluster all the nodes should have same resources. Need suggestions?

In theory, yes all nodes should have the same configuration. This is especially important to the following

CPU family
Base hardware (i.e. server model)
Patch level
Network configuration (including the NIC type)

Now, in my current role we actually have a 6 node cluster that has 2 "high spec" nodes and 4 lower spec nodes (but all 4 the same). The key to remember here is how the clustered instances will be distributed, just because you install a clustered instance into a multi node cluster it doesn't mean you should then install it across all the cluster nodes.
Only install the instance across nodes where you want the resources to be highly available.

So, having 2 nodes that are slightly lower spec does not present an issue but you should abide by the above regarding CPU family, network configuration and more importantly the patch level. The software version and level are the most important here.


muthyala_51 (4/2/2013)
Not sure. Wait for Perry's reply.

Lol, thank you

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
deep_kkumar
deep_kkumar
SSC Veteran
SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)SSC Veteran (263 reputation)

Group: General Forum Members
Points: 263 Visits: 756
Thanks Sailorking and Perry!
sql-lover
sql-lover
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1571 Visits: 1930
Dropping my 2 cents here.

This may not be true for 2+ node Cluster, but I always try to put more RAM on server than the total amount of SQL instances I have if, hypothetical scenario, I need to run those on one node only.

For instance:

RAM on Server A: X GB
RAM on Server B: Y GB

So... RAM Instance C + RAM Instance D < X + Y

That's in order to avoid the situation that two instances have more allocated RAM than actual server's RAM.
muth_51
muth_51
SSC Eights!
SSC Eights! (933 reputation)SSC Eights! (933 reputation)SSC Eights! (933 reputation)SSC Eights! (933 reputation)SSC Eights! (933 reputation)SSC Eights! (933 reputation)SSC Eights! (933 reputation)SSC Eights! (933 reputation)

Group: General Forum Members
Points: 933 Visits: 2905
Perry,

I was not able to follow this statement, can you please elaborate--

The key to remember here is how the clustered instances will be distributed, just because you install a clustered instance into a multi node cluster it doesn't mean you should then install it across all the cluster nodes.
Only install the instance across nodes where you want the resources to be highly available.

Perry Whittle
Perry Whittle
SSCoach
SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)

Group: General Forum Members
Points: 19704 Visits: 17239
muthyala_51 (4/4/2013)
Perry,

I was not able to follow this statement, can you please elaborate--

The key to remember here is how the clustered instances will be distributed, just because you install a clustered instance into a multi node cluster it doesn't mean you should then install it across all the cluster nodes.
Only install the instance across nodes where you want the resources to be highly available.

Say you have a cluster with 4 nodes ServerA, ServerB, ServerC and ServerD. You install a clustered instance to ServerA, you don't necessarily install it to the remaining 3 nodes.

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
dan-572483
dan-572483
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1312 Visits: 1983
What is the purpose of additional server nodes if you're not going to extend the SQL cluster there? If the servers with SQL go down, you're down. (Unless the server is being used for other things, like a network fileshare.)
Perry Whittle
Perry Whittle
SSCoach
SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)

Group: General Forum Members
Points: 19704 Visits: 17239
dan-572483 (4/10/2013)
What is the purpose of additional server nodes if you're not going to extend the SQL cluster there?

The whole idea of creating a multi node cluster is to make cluster administration easier. One 6 node cluster is easier to manage and uses less network name and IP resources than 3 x 2 node clusters.

Just because you have 6 nodes you do not necessarily want to extend your instance across all of the nodes, you'd generally leave at least one or as passive failover partners on hot standby for key instances.


dan-572483 (4/10/2013)
If the servers with SQL go down, you're down. (Unless the server is being used for other things, like a network fileshare.)


If i have 6 nodes with standard quorum setup of node majority with witness and 4 nodes fail then the cluster will be offline anyway. Whats the likelihood of 4 servers failing all at once, are they on a separate geographic site. you have to factor all this into your cluster design. Also, install 12 instances across 6 nodes and see how long the SP installer takes to run ;-)


The SQL Server installation quotes the following

Installing a SQL Server 2008 R2 Failover Cluster
Then, you run Setup again for each node you want to add to the cluster.


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search