Re: Re-adding noded to cluster
- From: "Anthony Thomas" <ALThomas@xxxxxxxxx>
- Date: Sat, 18 Nov 2006 10:31:48 -0600
Surprising that you should ask that. On 10/27, I posted the following list
of instructions.
Good luck.
Anthony Thomas
It is easy to evict a cluster node, repair or rebuild, and, perhaps even
upgrade it; however, on many occasions, we have had considerable trouble
reintroducing that newly built node back into the cluster configuration.
The following represents the cleanest solution we have come up with to date:
Here's the sequence of events.
1. Run SQL Server setup to manage the virtual server configuration and add
the new node to this configuration. This installs the RTM binaries to the
new node. It also installs the dreaded SCM (Service Control Manager), but
also the Cluster Network utility. (KB295589)
2. Log into the new node and remove the SCM from the system tray and startup
group. (Service Pack Read Me docs).
3. On both nodes, create Client Side Aliases using Named Pipe for the
virtual server instance. (KB815431)
4. Reboot the added node.
5. Apply SP3a (this was the prior headache). If you do not, because of the
3-digit Build number versus the SP4 4-digit build number, that stupid Win2K3
security dialog about only supporting SS2K if SP3 or later will launch on
the
unattended remote installation in interactive mode, which hangs. (KB905286)
(KB902955) (KB329329)
6. Reboot the added node.
7. Apply SP4.
8. Reboot the added node.
9. Apply HF 2187.
10. Reboot the added node.
11. On both nodes, switch the Client Side aliases to TCP protocol.
12. Now, here's the new error. When attempting to run the instance on the
newly added node, the cluster log will report that it could not start the
sqlsrvres and fail with error 435.
What this means is that the registry still contains the default out of box
registry keys. Primarily, the Named Pipe default pipe and the TCP default
port, as well as the default Start Up parameters. If any of these have been
modified from default, services will start up but fail on the newly added
node.
The fix is to log into the new node and use regedit to connect to the other
node. Export the following keys and save them to the local node.
HKLM\Cluster
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server
HKLM\SOFTWARE\Microsoft\MSSQLSERVER
Then merge these exports to the new node (local registry).
This last one is undocumented. If anyone kind find a KB reference, it would
be appreciated.
Sincerely,
Anthony Thomas
--
"Joe E O" <josephobrien@xxxxxxxxxxx> wrote in message
news:1163777568.605425.238240@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Running Sql Server 2000 SP3a on a two node cluster with one instance
running on the active node (Active/Passive)
We have to replace one of the physical nodes (repeated hw failures) -
how do I go about replacing the node within SQL Server. The NT guys
are telling me - that have to install from scratch the OS and bring it
up to the same OS patch levels of the remaining stable node.
So, once I the new node has been re-added to the phsical cluster...how
do i get SQL Server 2000 installed and how do I get it upgraded to SPS
3A
Joe E O
.
- References:
- Re-adding noded to cluster
- From: Joe E O
- Re-adding noded to cluster
- Prev by Date: Re: Move Clustered SQL 2000 database to stand alone server
- Next by Date: Re: Building high available and high performance web sites with MS
- Previous by thread: Re-adding noded to cluster
- Next by thread: Move Clustered SQL 2000 database to stand alone server
- Index(es):
Relevant Pages
|
Loading
