InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comFri, 24 May 2013 08:45:59 GMT20http://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspxThanks Dan, very much appreciatedThu, 08 Nov 2012 23:54:18 GMTgeoffrey.sturdyhttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspxYes it would. Just make sure to do the Clustered installation of SQL. If you do a non-clustered installation - even on a clustered OS - you'll have to start over.Thu, 08 Nov 2012 14:55:24 GMTdan-572483http://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspxAFternoon , Quick question on a related subjectWe are going to migrate our two-node SQL2008 clustered instances from a Windows 2003 environment to a WIndows 2008 environment. Our SQL servers are 2008 R2 SP1 Would it be possible to create new primary sql server node on the new cluster , patch to SP1 and migrate the databases in , and subsequently add a failover node to the new instance and patch that to the same level?ThanksThu, 08 Nov 2012 07:19:33 GMTgeoffrey.sturdyhttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspx[quote][b]davidwarner (10/9/2012)[/b][hr]I'm not good with AD but an issue i had was that during the install despite the domain service account used for the cluster having the right to create AD objects, something would happen where the objects wouldn't create in time during the install which would mean SQL would install with errors making installing updates fun.I think the issue was something to do with us having 30+ domain controllers and when the install created the logins it wouldn't replicate fast enough.[/quote]Well ... that's AD / Network design issues ... :-) ...not a Cluster problem itself.Of course, if the DC is not close enough or there is not a closer DC, or there are DNS or latency issues, replicating the AD objects will take time. That's why is so important to be sure everything is in place, including a good AD and Network design for the cluster.Wed, 10 Oct 2012 07:20:10 GMTsql-loverhttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspxI'm not good with AD but an issue i had was that during the install despite the domain service account used for the cluster having the right to create AD objects, something would happen where the objects wouldn't create in time during the install which would mean SQL would install with errors making installing updates fun.I think the issue was something to do with us having 30+ domain controllers and when the install created the logins it wouldn't replicate fast enough.Tue, 09 Oct 2012 22:45:01 GMTdavidwarnerhttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspx[quote][b]davidwarner (10/9/2012)[/b][hr]When you say that it's better to not create the AD/DNS accounts before setting up what draw backs specifically are you talking about? I have always setup Clusters creating the computer accounts in AD first.[/quote]It may be related to the AD object ownership and a clean installation.If the computer or service can generate its own AD object it's better to let it do it on its own, instead of manually create it. As a matter of fact, if the MS-SQL service has the proper rights, it will create whatever is required during the actual setup.Tue, 09 Oct 2012 21:56:50 GMTsql-loverhttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspxWhen you say that it's better to not create the AD/DNS accounts before setting up what draw backs specifically are you talking about? I have always setup Clusters creating the computer accounts in AD first.Tue, 09 Oct 2012 20:59:39 GMTdavidwarnerhttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspxyou're welcomeFri, 05 Oct 2012 05:52:09 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspxOnce again.. Thank you!!!!Fri, 05 Oct 2012 05:49:00 GMTJpotucekhttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspx[quote][b]Jpotucek (10/4/2012)[/b][hr]Another dumb question.[/quote]There are never dumb questions, only ever dumb answers ;-)[quote][b]Jpotucek (10/4/2012)[/b][hr] If each SQL Server Instance in the Cluster has it's own set of Cluster Resources: Network Name, IP address and Shared Disk, then that would all need to be setup in the Cluster Administrator at the OS level before you actually install each SQL Server Instance. [/quote]Mm, for the storage certainly but the ip and name are virtual, you specify them at the time of install, the rest is done for you. In fact it's better if they don't exist in DNS and AD from the start ;-)[quote][b]Jpotucek (10/4/2012)[/b][hr]All of the shared Resources should already be there and you would just choose them from a list - on the Cluster Disk selection screen during the SQL install????[/quote]As i said, for the storage only, yes.Thu, 04 Oct 2012 16:34:17 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspxAnother dumb question. If each SQL Server Instance in the Cluster has it's own set of Cluster Resources: Network Name, IP address and Shared Disk, then that would all need to be setup in the Cluster Administrator at the OS level before you actually install each SQL Server Instance. In other words, when get to the point that you are actually installing SQL Server, All of the shared Resources should already be there and you would just choose them from a list - on the Cluster Disk selection screen during the SQL install????Thu, 04 Oct 2012 13:43:56 GMTJpotucekhttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspxit's just so different from 2005 that the more I read .... I keep second guessing myself Thank you again for your patient guidance!!!Wed, 12 Sep 2012 08:51:09 GMTJpotucekhttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspx[quote][b]Jpotucek (9/12/2012)[/b][hr]one last point for clarification?? :blush:[/quote]tut tut tut, any more of this and you'll be incurring fees :-D[quote][b]Jpotucek (9/12/2012)[/b][hr]So (if I have this straight) There is one Quorum and one MSDTS and then multiple Instances would each have their own set of disks for Data, Logs, Tempdb, etc. [/quote]With Windows 2008 you can have more than 1 clustered MSDTC, but essentially yes, you are right[quote][b]Jpotucek (9/12/2012)[/b][hr]here is how I see the steps to install a Default Instance. 1) Setup 'New SQL Server Failover Cluster Installation" on Node 12) Go to the second Node (without failing over) and run set 'Add Node to a SQL Server failoverCluster'I should now have a fully functioning 2 Node Active Passive Cluster with a Default Instance. [/quote]What do you need me for? ;-)[quote][b]Jpotucek (9/12/2012)[/b][hr]For each SQL Server Instance that I want to add, would I repeat steps one AND two?[/quote]yes, that's correct.Wed, 12 Sep 2012 08:40:13 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspxone last point for clarification?? :blush:So (if I have this straight) There is one Quorum and one MSDTS and then multiple Instances would each have their own set of disks for Data, Logs, Tempdb, etc. here is how I see the steps to install a Default Instance. 1) Setup 'New SQL Server Failover Cluster Installation" on Node 12) Go to the second Node (without failing over) and run set 'Add Node to a SQL Server failoverCluster'I should now have a fully functioning 2 Node Active Passive Cluster with a Default Instance. ---For each SQL Server Instance that I want to add, would I repeat steps one AND two?Wed, 12 Sep 2012 07:57:09 GMTJpotucekhttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspxyou're welcome ;-)Mon, 10 Sep 2012 14:52:58 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspx[quote][b]Perry Whittle (9/10/2012)[/b][hr]See my 3 part guide starting at [url=http://www.sqlservercentral.com/articles/virtual/72682/][u][b]this link[/b][/u][/url] to deploy and configure the Windows cluster and the clustered SQL server instance. It covers virtual but applies to physical tooSee my guide at [url=http://www.sqlservercentral.com/articles/slipstream/71654/][u][b]this link[/b][/u][/url] for details how to slipstream service packs and\or cumulative updates[/quote]Thanks for sharing!Mon, 10 Sep 2012 14:15:35 GMTsql-loverhttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspx[quote][b]Jpotucek (9/10/2012)[/b][hr] why didn't I hire MS professional services for this!!!!!![/quote]No need to pay over the odds, You just merely need to hire a good contractor to design\install the system and provide onsite training.Mon, 10 Sep 2012 13:32:57 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspxThank you. that makes much more sense now. :-Dand also .. when I said this:"can anyone same MS Professional Services : )"I meant to say: "can anyone say MS Professional Services?" meaning.. :crying: why didn't I hire MS professional services for this!!!!!!Actually, I can't wait to dig into it! Thanks for all your guidance Perry!Mon, 10 Sep 2012 13:13:18 GMTJpotucekhttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspxYou dont have a quorum resource for each instance installed, the cluster as a whole at the windows level has one quorum resource.The resouce can be node majority for odd number of cluster nodes or disk or file share for even number of nodes.Mon, 10 Sep 2012 13:08:44 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspx"You only have one quorum resource for the windows cluster whether it be a disk or file share, etc."So my Disk config looks OK.. One quorum disk regarless of the # of Instances? and... Take a look a mount points? : )You da' bomb! Thanks for all your guidanceMon, 10 Sep 2012 09:29:56 GMTJpotucekhttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspx[quote][b]Jpotucek (9/10/2012)[/b][hr]can anyone same MS Professional Services : )[/quote]don't understand, what does this mean?[quote][b]Jpotucek (9/10/2012)[/b][hr]So speaking specifically how the drives would need to get carved out, I already have a 2 node active passive cluster on sql server 2005 and the drive configuration looks like this:C: Local to each node (for Biniaries) (50GB)D: Local to each node (for misc files) (85GB)Q: Quorum (1GB) M: MSTSC (1GB)F: Shared on the San (datafiles) (300GB)G: Shared On the San (Logfiles) (300GB) H: Shared on the San (TempDB) (50GB)____________________________________________________________My 2008R2 Cluster with 3 Instances, will would look like this: Default InstanceC: Local to each node (for Biniaries) (50GB)D: Local to each node (for misc files) (85GB)Q: Quorum (1GB) M: MSTSC (1GB)F: Shared on the San (datafiles) (100GB)G: Shared On the San (Logfiles) (100GB) H: Shared on the San (TempDB) (50GB)Named Instance 1I: Shared on the San (datafiles) (100GB)J: Shared On the San (Logfiles) (100GB) K: Shared on the San (TempDB) (50GB)Named Instance 2L: Shared on the San (datafiles) (100GB)M: Shared On the San (Logfiles) (100GB) N: Shared on the San (TempDB) (50GB)Named Instance 3R: Shared on the San (datafiles) (100GB)S: Shared On the San (Logfiles) (100GB) T: Shared on the San (TempDB) (50GB)Or does each install create a new Quorum Drive as well because you are actually adding a Node?[/quote]You only have one quorum resource for the windows cluster whether it be a disk or file share, etc.With the above configuration for your new cluster you may want to look at using mount points to cut down on the drive assignments and yep, you guessed it, [url=http://www.sqlservercentral.com/articles/mount+points/75855/][u][b]heres a link[/b][/u][/url] to my guide on this site :-D:cool:Mon, 10 Sep 2012 09:25:07 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspxAwesome stuff.. can anyone same MS Professional Services : )So speaking specifically how the drives would need to get carved out, I already have a 2 node active passive cluster on sql server 2005 and the drive configuration looks like this:C: Local to each node (for Biniaries) (50GB)D: Local to each node (for misc files) (85GB)Q: Quorum (1GB) M: MSTSC (1GB)F: Shared on the San (datafiles) (300GB)G: Shared On the San (Logfiles) (300GB) H: Shared on the San (TempDB) (50GB)____________________________________________________________My 2008R2 Cluster with 3 Instances, will would look like this: Default InstanceC: Local to each node (for Biniaries) (50GB)D: Local to each node (for misc files) (85GB)Q: Quorum (1GB) M: MSTSC (1GB)F: Shared on the San (datafiles) (100GB)G: Shared On the San (Logfiles) (100GB) H: Shared on the San (TempDB) (50GB)Named Instance 1I: Shared on the San (datafiles) (100GB)J: Shared On the San (Logfiles) (100GB) K: Shared on the San (TempDB) (50GB)Named Instance 2L: Shared on the San (datafiles) (100GB)M: Shared On the San (Logfiles) (100GB) N: Shared on the San (TempDB) (50GB)Named Instance 3R: Shared on the San (datafiles) (100GB)S: Shared On the San (Logfiles) (100GB) T: Shared on the San (TempDB) (50GB)Or does each install create a new Quorum Drive as well because you are actually adding a Node?Mon, 10 Sep 2012 08:45:20 GMTJpotucekhttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspx[quote][b]Jpotucek (9/10/2012)[/b][hr]awesome! Thank you Perry![/quote]You're welcome[quote][b]Jpotucek (9/10/2012)[/b][hr]IS it true that you you cannot share resources, including disk resources, between instances. You get one instance per "Service or Application"? [/quote]That's correct[quote][b]Jpotucek (9/10/2012)[/b][hr]For a second instance, I would need a [b]new set of Disks[/b], a new network name, and a new IP address? [/quote]Correct[quote][b]Jpotucek (9/10/2012)[/b][hr]So basically to add Named Instances after the default Instance is up and runnning in the Cluster, I would have to run BOTH the [b]New SQL Server Failover Cluster Installation [/b] setup [b]AND then switch over to the passive node and run the Add Node to a SQL Server Failover Cluster [/b] [/quote]Yes you would[quote][b]Jpotucek (9/10/2012)[/b][hr]Once again, I appoligize for the elementary questions, this will be alot easier once we have the DEV cluster built and can dig in. I am just trying to do some research and planning so I know how many IP addresses we need, how the SAN should be carved out, etc...[/quote]You'll need a virtual IP and networkname for the Windows cluster too ;-)So, if you have a 2 node cluster with 2 instances of SQL Server clustered you need 3 IPs and 3 networknamesMon, 10 Sep 2012 08:22:23 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspxawesome! Thank you Perry!IS it true that you you cannot share resources, including disk resources, between instances. You get one instance per "Service or Application"? For a second instance, I would need a [b]new set of Disks[/b], a new network name, and a new IP address? So basically to add Named Instances after the default Instance is up and runnning in the Cluster, I would have to run BOTH the [b]New SQL Server Failover Cluster Installation [/b] setup [b]AND then switch over to the passive node and run the Add Node to a SQL Server Failover Cluster [/b] Once again, I appoligize for the elementary questions, this will be alot easier once we have the DEV cluster built and can dig in. I am just trying to do some research and planning so I know how many IP addresses we need, how the SAN should be carved out, etc...Mon, 10 Sep 2012 08:14:11 GMTJpotucekhttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspx[url=http://www.sqlservercentral.com/articles/Clustering/73994/][u][b]part 3[/b][/u][/url]Mon, 10 Sep 2012 06:34:13 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspxThank you very much for the Helpful links! I will share with the Server guys as well !!!You wrote: [i]See my 3 part guide starting at this link to deploy and configure the Windows cluster and the clustered SQL server instance. [/i]Do you have a link to Part 3? all I can find are parts 1 and 2. Mon, 10 Sep 2012 06:16:09 GMTJpotucekhttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspx[quote][b]Jpotucek (9/7/2012)[/b][hr]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 [b]New Server Server Failover Cluster [/b]option- Failover the resources and run set on the second (now active) Node using the [b]Add Node to a SQL server Failover Cluster[/b] 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. [/quote]See my 3 part guide starting at [url=http://www.sqlservercentral.com/articles/virtual/72682/][u][b]this link[/b][/u][/url] to deploy and configure the Windows cluster and the clustered SQL server instance. It covers virtual but applies to physical tooSee my guide at [url=http://www.sqlservercentral.com/articles/slipstream/71654/][u][b]this link[/b][/u][/url] for details how to slipstream service packs and\or cumulative updatesMon, 10 Sep 2012 04:33:06 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspxThanks for your help. Believe me.. I've googled this and read and googled and read.. : )Until I can actually 'do it' it's hard to get my brain around the fact that you patch the passive node first.. or go to the passive node to add an instance. the cluster rsources are are not active on the passive node which means services are not started and the system databases not accessible.. I'm so used to having drilled into my head to backup system databases before you patch!! I guess that is not the case with 2008 in a cluster?Sat, 08 Sep 2012 19:21:37 GMTJpotucekhttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspxMore on the same,Remember, Google is your friend! ;-)[url=http://support.microsoft.com/kb/958734]SQL Server 2008 failover cluster rolling patch and service pack process[/url]Sat, 08 Sep 2012 17:57:26 GMTsql-loverhttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspxTo patch (MS-SQL)You failover or move the resources to other node, let's call it B. You run the service pack or whatever on Node A. At that point, A is fully patched.Now, you fail over to Node "A" which becomes active. And now you patch Node B. Now both nodes are fully patched.This was a major change from MS-SQL 2005 and MS-SQL2000, where you patch the virtual instance and the patch is being replicated over the network to other node. This caused some issues, because if network fails or something breaks, one of the nodes won't end fully patched ending in a non consistent state or different dll versions. Trust me, it was a pain when failed.Sat, 08 Sep 2012 17:53:41 GMTsql-loverhttp://www.sqlservercentral.com/Forums/Topic1356032-1549-1.aspxI 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 [b]New Server Server Failover Cluster [/b]option- Failover the resources and run set on the second (now active) Node using the [b]Add Node to a SQL server Failover Cluster[/b] 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. Fri, 07 Sep 2012 08:54:48 GMTJpotucek