• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 482
  • Last Modified:

installing sql server 2008 r2 in a cluster

I have a couple of questions about installing SQL Server 2008 R2 Standard in a 2 node active\passive cluster

First, a little background. The Admin guys have not Clustered Windows yet. The hardware is due in next week so I'm just trying to get my notes together for the SQL install once the Cluster is available.

From what I'm reading, Failover clustering setup has a whole new work flow in SQL Server 2008.

These are the (very high level) steps as a see them to be:

- Run setup on the Active Node of the Cluster using the New Server Server Failover Cluster option
- Failover the resources and run set on the second (now active) Node using the Add Node to a SQL server Failover Cluster option

Is that correct?

Also, I'm not clear about how you would patch the installation and add Instances.

Would you run Service Packs and Cummulative Updates against both nodes? if so, in what order?

In order to add an Instance (I'll be adding 2 Named Instances), What setup option would you use? Would you run set up on the Active Node then failover and run it again to add an Instance?
Also about Named Instances... If I have a simple Active\Passive Cluster with one set of cluster resources and multiple instances, do I need seperate IP addresses for each Instance?

I apologize if the questions seem elementary but this is our first time with SQL Server 2008 and Clustering!

Any help or guidance would be greatly appreciated.
  • 2
  • 2
1 Solution
Microsoft information that answer some questions:
itsonlyme4Author Commented:
Thank you.   that was one of the docs I read that actually prompted my questions.
Something to keep in mind, you will need 2 host names and IP addresses as you want to install 2 separate instances on the cluster.  The other thing to think about is MSDTC.  You will need 2 separate instances of MSDTC, which will require 2 more hostnames and IP addresses.  (HINT:  You'll probably want to create all Objects in Active Directory and DNS first)

Secondly, you are correct.  You would create a new clustered node.  After setup finishes, you would go to the secondary node, it doesn't have to be the active node, and add a node to a cluster in sql setup.  What this actually does is not only install SQL, but also goes out to the cluster and gives this node access to the clustered resources.  The clustered resources would be disks, services, SQL hostname/IP, etc....  If you want to have 2 instances, then you would just repeat the process.

As far as patching, you would patch on the active node, then fail over and patch the other node.


itsonlyme4Author Commented:
Thank you.  That clarifies things a bit.   I thought I had read though that the patching was always done on the 'passive' node first!!??     I can't find anythign definnitive as far as instructions for patching SQL in a the cluster on the Microsoft site.
OK, as far as updates go, again, you are correct.


Installing on an active node can induce downtime.  Therefore, install updates on the passive node.  My appologies.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now