Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
itsonlyme4
Posting Yak Master
109 Posts |
 Posted - 2012-09-07 : 14:35:46
|
| I have a couple of questions about installing SQL Server 2008 R2 Standard in a 2 node active\passive clusterFirst, 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 optionIs 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. |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2012-09-07 : 15:41:11
|
| You run Setup on 1 of the nodes and select "Install New Failover Cluster". Once that completes, you run Setup on the other node, and select "Add Failover Cluster Node".The process is the same for new instances, for each instance, you install a new failover cluster, and add a node.For Service Packs, you install the SP on the passive node, then failover to the patched node, and patch the unpatched node.-Chad |
 |
|
|
itsonlyme4
Posting Yak Master
109 Posts |
Posted - 2012-09-08 : 05:26:36
|
| Thank you for the clarification!!!! I am a little confused still on the patching... it doesn't seem logical that you would be able to patch the passive node first because all of the services are down and the shared cluster resources are owned by the other node which means that the sytem databases aren't present.. can't wrap my brain around that part of it. I am so used to doing System DB backups before running any SPs or CUs - how does that work? Also, when installing the 2nd and 3rd instances - do they each get their own IP address and\or listening port???? |
|
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2012-09-08 : 12:59:46
|
| It upgrades the binaries on the passive node, and when you failover, it will run upgrade scripts on all of the databases...This will effect your failover time as DBs will take a little longer to become available. Yes, each instance will have it's own Newtork Name and IP Address.-Chad |
|
|
|
itsonlyme4
Posting Yak Master
109 Posts |
Posted - 2012-09-09 : 07:55:42
|
| SO very helpfull!! I can't wait to get our Dev cluster built so see how it all works!! One more point of clarification. I understand that each each instance has it's own network name AND IP address so does that mean the listening port is different for each? |
|
|
|
|
|
|
|
|
First time installing SQL Server 2008 in a Cluster