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


SQL 2008 R2 Cluster Setup: Easy? Not So Much.


SQL 2008 R2 Cluster Setup: Easy? Not So Much.

Author
Message
Fabrizio Faleni
Fabrizio Faleni
SSC Veteran
SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)

Group: General Forum Members
Points: 283 Visits: 456
Comments posted to this topic are about the item SQL 2008 R2 Cluster Setup: Easy? Not So Much.

MCITP Database administrator 2008
MCTS SQL Server 2008 Implementation and maintenance
MCTS Sharepoint configuration
MCP Designing Deploying and Managing a Network Solution for the Small and Medium-sized Business
ITIL V3 Foundation

prowlermax
prowlermax
SSC Rookie
SSC Rookie (38 reputation)SSC Rookie (38 reputation)SSC Rookie (38 reputation)SSC Rookie (38 reputation)SSC Rookie (38 reputation)SSC Rookie (38 reputation)SSC Rookie (38 reputation)SSC Rookie (38 reputation)

Group: General Forum Members
Points: 38 Visits: 85
Very informative. Thank you.
I do have a question. I am planning to upgrade a two-node cluster from SQL 2008 to SQL 2008 R2.
My plan was to tear upgrade the passive node, failover, upgrade the 2nd node. I have not come across the problem you described, but I am assuming that there would be certain pitfalls to my approach. Have you had any experience with a similar situation?
Thanks!!
Elliott Whitlow
Elliott Whitlow
SSC-Insane
SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)

Group: General Forum Members
Points: 23910 Visits: 5314
I don't think your upgrade path will work as described. As I read it you are doing a version upgrade of an existing instance on the passive node then failing over to do the previous active node. I don't think this is supported. You could add another instance to the passive node of the new SQL Version but it would have a different name and you would have some trickiness with the database files..

CEWII
Fabrizio Faleni
Fabrizio Faleni
SSC Veteran
SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)

Group: General Forum Members
Points: 283 Visits: 456
@Prowlermax,
I have not upgraded a Cluster to SQL2008R2 yet. I should upgrade a SQL 2005 to SQL 2008R2 in the next two months and my plan is to:
1.Full system backup backup of the passive node
2.Upgrade SQL in the passive node
3.Take a last Full backup of databases in their 2005 version
4.Failover from SQL 2005 (active) node to upgraded SQL2008R2 node
5.DBA Check / User Acceptance Checks
6.Upgrade the now passive SQL2005 Node
7.Take a full backup of the databases
8.Failover to the newly upgraded node
9.DBA Check / User Acceptance Checks

MCITP Database administrator 2008
MCTS SQL Server 2008 Implementation and maintenance
MCTS Sharepoint configuration
MCP Designing Deploying and Managing a Network Solution for the Small and Medium-sized Business
ITIL V3 Foundation

calvo
calvo
Hall of Fame
Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)

Group: General Forum Members
Points: 3280 Visits: 4018
Thanks for the information, great to have all those tips and resources in one article.

______________________________________________________________________________________________
Forum posting etiquette. Get your answers faster.
Fabrizio Faleni
Fabrizio Faleni
SSC Veteran
SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)

Group: General Forum Members
Points: 283 Visits: 456
Thanks Calvo! The goal was to share an experience and try to easy someone's life if they should get into these issues. I'll try to share some more in the next weeks.

MCITP Database administrator 2008
MCTS SQL Server 2008 Implementation and maintenance
MCTS Sharepoint configuration
MCP Designing Deploying and Managing a Network Solution for the Small and Medium-sized Business
ITIL V3 Foundation

Chris Houghton
Chris Houghton
SSC Eights!
SSC Eights! (892 reputation)SSC Eights! (892 reputation)SSC Eights! (892 reputation)SSC Eights! (892 reputation)SSC Eights! (892 reputation)SSC Eights! (892 reputation)SSC Eights! (892 reputation)SSC Eights! (892 reputation)

Group: General Forum Members
Points: 892 Visits: 1710
Nice post, thanks for sharing.
forsqlserver
forsqlserver
SSCarpal Tunnel
SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)

Group: General Forum Members
Points: 4538 Visits: 2060
I want to a create 3 node cluster.Two node is easy to create but how will I add 3rd node.
Please explain in detail.

Thanks
Fabrizio Faleni
Fabrizio Faleni
SSC Veteran
SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)SSC Veteran (283 reputation)

Group: General Forum Members
Points: 283 Visits: 456
@forsqlserver
From a cluster/SQL setup point of view, adding a third node is not very complicated: you join the new node to the existing cluster and you add a SQL Server instance to an existing cluster. So it's more or less just like adding a second node again.

If you want to create a 3 node cluster it is probably because you want to spare some money in hardware and to have two active nodes that might both failover on the third node. This a correct solution if your SLA states that in case of failover of both active nodes you may have degraded performance.

The challenge here is to define carefully how to share the resources (RAM + CPU) in case you find yourself with, let's say five OLTP instances and two OLAP instances, suddenly running on the same box called Node 3. In the normal situation the 5 OLTP run on Node 1 and you defined how they should share 64GB RAM + 8 cores between them; the two OLAP instances usually run on Node 2 and share (even if it is more difficult to define memory allocation in SSAS) 64GB and 8 cores.

When all that stuff fails over node 3 and there are less than 128GB + 16 cores available on that box, you may have some resource contention problems, right?

In addition to this you might want to prepare all possible scenarios, like all nodes failing on node 1, etc.

The more active nodes you add, the more complexity you get.

MCITP Database administrator 2008
MCTS SQL Server 2008 Implementation and maintenance
MCTS Sharepoint configuration
MCP Designing Deploying and Managing a Network Solution for the Small and Medium-sized Business
ITIL V3 Foundation

forsqlserver
forsqlserver
SSCarpal Tunnel
SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)

Group: General Forum Members
Points: 4538 Visits: 2060
Thanks Faeni..

Thanks
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