 | |
Adding 3 nodes to a cluster
microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering
 |
| | Thread Tools | Display Modes |
#81
 
| |||
| |||
|
Re: Adding 3 nodes to a cluster -
04-16-2008
, 03:38 PM
|
These are new nodes. Should the first step (after adding the new nodes to the cluster) be adding them to cluster to manage they already installed instances? Or should I proceed and install the new instance? Or does it even matter which comes first? "Geoff N. Hiten" wrote: If the new nodes are using the same names as old nodes, you have to uninstall then reinstall to those nodes. -- Geoff N. Hiten Senior SQL Infrastructure Consultant Microsoft SQL Server MVP "AJ" <AJ (AT) discussions (DOT) microsoft.com> wrote in message news:8DF2A873-233A-4F1A-BC6F-8183CE7EF02E (AT) microsoft (DOT) com... Ok understood. But when I go to add the new nodes to the existing clustered instances (using the installer) the new nodes are already listed as configured nodes. Shouldn't they be listed as "available nodes"? "Geoff N. Hiten" wrote: Nodes are not instances. They are independent resources. Nodes are computers. Each instance has to be installed to each allowed node. The installer takes care of adding and removing nodes from instances. So you need to add the nodes to the cluster using the Cluster tool. Then extend the existing instance to the new nodes using the installer. Finally, add four new instances with all nodes as allowed hosts. Each virtual server can only host one instance so you will need new resources for each new instance. Don't forget to patch each instance after installing\modifying the node set. -- Geoff N. Hiten Senior SQL Infrastructure Consultant Microsoft SQL Server MVP "AJ" <AJ (AT) discussions (DOT) microsoft.com> wrote in message news:F4D0B931-1383-4906-A73B-0157440E74CA (AT) microsoft (DOT) com... I need to add these new servers as seperate instances in the SQL cluster. Basically what we are aiming for is a 5 active SQL cluster with each of the servers acting as a failover in case one of the servers fails. Is this possible even though the cluster is already established with two seperate instances? What we would like to do is add the 3 new nodes as seperate instances within the cluster. The plan is to basically seperate our 5 major databases onto their own server but maintain the failover feature. What we currently have is two seperate vitrual servers each running their own instance of sql. Any ideas are welcome. thx. "Geoff N. Hiten" wrote: The SQL installer allows you to add the new nodes as allowed hosts after you have joined the new nodes to the cluster. You must use the installer (SQL2000) to apply binaries to the new nodes and set the clustered properties correctly. Look up "maintaining a failover cluster" in BOL. -- Geoff N. Hiten Senior SQL Infrastructure Consultant Microsoft SQL Server MVP "AJ" <AJ (AT) discussions (DOT) microsoft.com> wrote in message news:F722B90A-87D0-4D99-8CAD-88BFFE746FDF (AT) microsoft (DOT) com... Hello, I'm attempting to add three nodes to a SQL 2000 two node cluster. All three servers have been added but I cannot failover the sql instances from the previous two node cluster to any of the new servers. I did notice that there were SQL services for the old instances missing on the new servers. I've added those missing registry entries but the fail over always fails when attempting to bring online the SQL server instance. Is there a way to manually correct this issue? |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.