Re: Adding 3 nodes to a cluster

First you use the cluster admin tool to add the machines as nodes to the cluster. Then you run the SQL installer to install binaries on the newly added nodes and allow the new nodes to host the existing instances.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP




"AJ" <AJ@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:86752A13-2600-44F6-81D6-A72E44218ABC@xxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8DF2A873-233A-4F1A-BC6F-8183CE7EF02E@xxxxxxxxxxxxxxxx
> 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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:F4D0B931-1383-4906-A73B-0157440E74CA@xxxxxxxxxxxxxxxx
>> >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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> >> news:F722B90A-87D0-4D99-8CAD-88BFFE746FDF@xxxxxxxxxxxxxxxx
>> >> > 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?
>> >>
>> >>
>>
>>



.

Relevant Pages

  • Re: Adding 3 nodes to a cluster
    ... 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. ... Senior SQL Infrastructure Consultant ... servers acting as a failover in case one of the servers fails. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Setup Failed to Perform Reqd operations on CLuster Nodes
    ... Windows Client network tools. ... then you cannot build a SQL cluster. ... SQL Installer relies on this functionality to copy installation files to ...
    (microsoft.public.sqlserver.clustering)
  • Re: applying SQL patch
    ... SQL hotfixes are cluster-aware, just like a SQL service pack. ... You must start the hotfix installer from the node that currently ... You may have to reboot the cluster host nodes ...
    (microsoft.public.sqlserver.clustering)
  • Re: Damaged Cluster Node
    ... The SQL 2000 SP4 installer is a cluster-wide installer and will re-apply the SP to all nodes. ... from both SQLand the cluster. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Adding 3 nodes to a cluster
    ... 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. ... Senior SQL Infrastructure Consultant ... servers acting as a failover in case one of the servers fails. ...
    (microsoft.public.sqlserver.clustering)