Unable to fail over to new node

I recently added an additional node to a 2 node cluster hopeing to achieve N+1

I am running win2k3SP1, SQL2000SP3.

I can fail over clustering and MSDTC to the new node, but am unable to get
the existing virtual SQL servers to fail over to my new node.

I can list the new node in the "possible owners" resource option for the SQL
virtuals.

I see that there is no refrence to the SQL virtuals in the services on the
new nodes OS... this seems to be a concern, as well, I notice that there are
no refrences to the other virtual instances in the server network utility.

It is acting like the existing SQL virtual instance are unaware of the new
node.

I have tried configuring the MSDTC to allow network connections, and have
verified that the remote registry service is running.

All services are using the same domain admin credentials.

Did I set something up wrong? The one virtual instance I created when I
installed the new node seems to be working fine.
--

Thanks for taking the time to read this, even more thanks for trying to help.
Brian L

It is acting like SQL is unaware of the new node precisely because SQL is
unaware of the new node.

You need to run the setup program and choose "Maintain a Failover Cluster".
You can then add the new node. Note that you have to do this for each
instance separately. Plus, you need to rerun any service packs for each
instance to update the executables on the new node.

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




"Brian L" wrote in message

>I recently added an additional node to a 2 node cluster hopeing to achieve
>N+1
>
> I am running win2k3SP1, SQL2000SP3.
>
> I can fail over clustering and MSDTC to the new node, but am unable to get
> the existing virtual SQL servers to fail over to my new node.
>
> I can list the new node in the "possible owners" resource option for the
> SQL
> virtuals.
>
> I see that there is no refrence to the SQL virtuals in the services on the
> new nodes OS... this seems to be a concern, as well, I notice that there
> are
> no refrences to the other virtual instances in the server network utility.
>
> It is acting like the existing SQL virtual instance are unaware of the new
> node.
>
> I have tried configuring the MSDTC to allow network connections, and have
> verified that the remote registry service is running.
>
> All services are using the same domain admin credentials.
>
> Did I set something up wrong? The one virtual instance I created when I
> installed the new node seems to be working fine.
> --
>
> Thanks for taking the time to read this, even more thanks for trying to
> help.
> Brian L
>