RE: SQL 2000 Cluster Recovery Procedures

From: Fany Vargas [MSFT] (fanyv_at_online.microsoft.com)
Date: 12/29/04 

Date: Wed, 29 Dec 2004 15:26:25 GMT

For some reason, my entire message was not sent. Below is the rest of my
message:

Here are the steps necessary to rebuild the nodes, one at a time with
minimum down time.
1) Have all resources running on the good node Then take the following
steps on the node you want to rebuild.
2) Run SQL 2000 Setup. Type in your Virtual Server Name . It will give
you an option to maintain an existing virtual server. In there it will
allow you to remove a node from the virtual server. Remove the node you
want to rebuild from the Virtual Server Once you have done that you
should have SQL running on a one node virtual server.
3) Evict the Node from the windows Cluster.
4) Rebuild the node
5) Join the Node back to the Windows Cluster
6) Run SQL2000 Setup again to add the node back to the virtual server
7) IF the SQL installation was on a Service Pack Run that SQL Server
Service Pack installation from the newly rebuilt node. It will update
the binaries on that node to the correct Service Pack level e.g. If SQL
is on SP2, then run the SP2 setup
8) Once Service Pack completes successfully , then failover all resources
to that node . Make sure everything is running fine.
9) Repeat the above steps for the other node if you need to rebuild it

Documentation of this process can be found in:
SQL Books Online topic: Maintaining a Failover Cluster
SQL Books Online topic: Recovering from Failover Cluster Failure
SQL Server 2000 Clustering Whitepaper
<http://www.microsoft.com/technet/prodtechnol/sql/deploy/confeat/failclus.as
p>

Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.

Relevant Pages

  • Re: Default or named instances??
    ... this with SRV records, i didnt see a _sql records, lots of other types.. ... I've setup the cluster and tried to install the second instance as ... For each instance I need a virtual server name and an instance name ... The second named instance is accessible by the new virtal servers' name ...
    (microsoft.public.sqlserver.clustering)
  • Re: Default or named instances??
    ... The SQL alias name becomes the service name. ... It has to be a named instance. ... I will have to disagree with the analogy you gave though about treating the cluster as a single system and that's exactly what I'm trying to resolve here. ... According to your explanation about the relationship between SQL instance and virtual server I would change the analogy to say I could treat the VIRTUAL SERVER as I would a single system. ...
    (microsoft.public.sqlserver.clustering)
  • Re: about another instance of virtual server on sql2000 cluster
    ... Multiple instances on a cluster look and act just like multiple ... Microsoft SQL Server MVP ... > the new instance of sql virtual server is myclustersql02\myclustersql02 ... You can specify the same path, and the install will create a ...
    (microsoft.public.sqlserver.clustering)
  • RE: SQL 2000 Cluster Recovery Procedures
    ... > steps on the node you want to rebuild. ... > you an option to maintain an existing virtual server. ... > 5) Join the Node back to the Windows Cluster ... > 7) IF the SQL installation was on a Service Pack Run that SQL Server ...
    (microsoft.public.sqlserver.setup)
  • Re: Default or named instances??
    ... I've setup the cluster and tried to install the second instance as default ... According to your explanation about the relationship between SQL instance ... and virtual server I would change the analogy to say I could treat the ...
    (microsoft.public.sqlserver.clustering)
Quantcast