third node will not join cluster
- From: wpb999@xxxxxxxxx
- Date: 2 Feb 2007 06:02:37 -0800
We did this before so we know the process works. The background info
is we have a massive active/active
(2 node) sql cluster running Datacenter 2000. We need to upgrade
hardware and OS. migrating DB's is not an option due to huge numbers.
We created two new servers with Datacenter 2003_R2. Added first node
ok, took cluster resoruces offline, moved them to new node, stopped
cluster services on both old nodes, added the next node, (now a quad
cluster) restarted cluster services on first two nodes (original W2000
Datacenter) turned resources online and tested failover between nodes.
Everything worked, testing results good, etc. Evicted old nodes.
Tried to do this again on another 2 node active/active cluster running
Datacenter 2000. this time the new servers were installed with 2003 R2
Enterprise. We get the following errors in ClCfgSrv.log when we try to
add first node.
2007-02-01 06:44:08.447 [INFO] [BC-ClusDB-Create] Error 0x0006d1
returned from JoinAddNode4. Sponser must be Windows 2000.
2007-02-01 06:44:08.510 [INFO] [BC-ClusDB-Create] Error 0x000573
returned from JoinAddNodeN.
2007-02-01 06:44:08.557 [INFO] [BC-ClusDB-Create] Error 0x000573
occurred trying to add this node to the sponsor cluster
2007-02-02 07:58:59.998 [INFO] [BC-ClusDB-Create] Error 0x0006d1
returned from JoinAddNode4. Sponser must be Windows 2000.
2007-02-02 07:59:00.045 [INFO] [BC-ClusDB-Create] Error 0x000573
returned from JoinAddNodeN.
2007-02-02 07:59:00.092 [INFO] [BC-ClusDB-Create] Error 0x000573
occurred trying to add this node to the sponsor cluster
We have tried the "Cluster Node (nodename) /forcecleanup" but cannot
get new nodes in. The process
we used gets around "Sponser must be Windows 2000."
.
- Follow-Ups:
- Re: third node will not join cluster
- From: Rodney R. Fournier [MVP]
- Re: third node will not join cluster
- Prev by Date: Re: Side-by-side upgrade - moving master, msdb and model
- Next by Date: Re: Side-by-side upgrade - moving master, msdb and model
- Previous by thread: Re: client can't connect when instance on one particular node
- Next by thread: Re: third node will not join cluster
- Index(es):
Relevant Pages
|
Loading