dbTalk Databases Forums  

Unable to fail over to new node

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering


Discuss Unable to fail over to new node in the microsoft.public.sqlserver.clustering forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Brian L
 
Posts: n/a

Default Unable to fail over to new node - 11-29-2007 , 10:15 AM






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


Reply With Quote
  #2  
Old   
Geoff N. Hiten
 
Posts: n/a

Default Re: Unable to fail over to new node - 11-29-2007 , 11:10 AM






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" <BrianL (AT) discussions (DOT) microsoft.com> wrote

Quote:
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



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.