Hi All,

first of all, sorry if this kind of question has already been done,
but I'm not able to find it (may be I used wrong keywords): I always
found topics with correct backup scenarios.

I had a failure on a Active\Passive Win2k and SQL Server 2000 Cluster:
NODEA crashed and I only have the backup of the SQL Databases, not the
System State.

I would like to know what is the correct procedure to reinstall the
server, and to rejoin it to the cluster.

I thought this procedure, but I don't know if it is correct:

- Evict the crashed node from the cluster
- Reinstall the node with Windows 2000
- Join it to the domain
- Install Cluster Service and configure it to join to the cluster
- Install SQL Server on the crashed node
- Try to move the groups

Is this correct? What about reinstalling MSDTC? And is it correct to
reinstall SQL Server? Do I have to apply SQL Service Pack? And so on..

Thank you very much for you help!

You may need to reconfigure the new node for MSDTC.

You will need to run the SQL installer and remove the failed node from the
SQL installation, ESPECIALLY if you are reusing the original node name.

The SQL reinstall is actually maintaing the failover cluster after a
failure. BOL has instructions on how to recover. It is important to
distinguish the maintenance of the clustered SQL instance from installing
SQL instance.


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


"T_M_P" <claudio.toldi (AT) gmail (DOT) com> wrote

You may need to reconfigure the new node for MSDTC.

You will need to run the SQL installer and remove the failed node from the
SQL installation, ESPECIALLY if you are reusing the original node name.

The SQL reinstall is actually maintaing the failover cluster after a
failure. BOL has instructions on how to recover. It is important to
distinguish the maintenance of the clustered SQL instance from installing
SQL instance.


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


"T_M_P" <claudio.toldi (AT) gmail (DOT) com> wrote

You may need to reconfigure the new node for MSDTC.

You will need to run the SQL installer and remove the failed node from the
SQL installation, ESPECIALLY if you are reusing the original node name.

The SQL reinstall is actually maintaing the failover cluster after a
failure. BOL has instructions on how to recover. It is important to
distinguish the maintenance of the clustered SQL instance from installing
SQL instance.


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


"T_M_P" <claudio.toldi (AT) gmail (DOT) com> wrote

You may need to reconfigure the new node for MSDTC.

You will need to run the SQL installer and remove the failed node from the
SQL installation, ESPECIALLY if you are reusing the original node name.

The SQL reinstall is actually maintaing the failover cluster after a
failure. BOL has instructions on how to recover. It is important to
distinguish the maintenance of the clustered SQL instance from installing
SQL instance.


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


"T_M_P" <claudio.toldi (AT) gmail (DOT) com> wrote

You may need to reconfigure the new node for MSDTC.

You will need to run the SQL installer and remove the failed node from the
SQL installation, ESPECIALLY if you are reusing the original node name.

The SQL reinstall is actually maintaing the failover cluster after a
failure. BOL has instructions on how to recover. It is important to
distinguish the maintenance of the clustered SQL instance from installing
SQL instance.


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


"T_M_P" <claudio.toldi (AT) gmail (DOT) com> wrote

You may need to reconfigure the new node for MSDTC.

You will need to run the SQL installer and remove the failed node from the
SQL installation, ESPECIALLY if you are reusing the original node name.

The SQL reinstall is actually maintaing the failover cluster after a
failure. BOL has instructions on how to recover. It is important to
distinguish the maintenance of the clustered SQL instance from installing
SQL instance.


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


"T_M_P" <claudio.toldi (AT) gmail (DOT) com> wrote

You may need to reconfigure the new node for MSDTC.

You will need to run the SQL installer and remove the failed node from the
SQL installation, ESPECIALLY if you are reusing the original node name.

The SQL reinstall is actually maintaing the failover cluster after a
failure. BOL has instructions on how to recover. It is important to
distinguish the maintenance of the clustered SQL instance from installing
SQL instance.


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


"T_M_P" <claudio.toldi (AT) gmail (DOT) com> wrote

You may need to reconfigure the new node for MSDTC.

You will need to run the SQL installer and remove the failed node from the
SQL installation, ESPECIALLY if you are reusing the original node name.

The SQL reinstall is actually maintaing the failover cluster after a
failure. BOL has instructions on how to recover. It is important to
distinguish the maintenance of the clustered SQL instance from installing
SQL instance.


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


"T_M_P" <claudio.toldi (AT) gmail (DOT) com> wrote

You may need to reconfigure the new node for MSDTC.

You will need to run the SQL installer and remove the failed node from the
SQL installation, ESPECIALLY if you are reusing the original node name.

The SQL reinstall is actually maintaing the failover cluster after a
failure. BOL has instructions on how to recover. It is important to
distinguish the maintenance of the clustered SQL instance from installing
SQL instance.


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


"T_M_P" <claudio.toldi (AT) gmail (DOT) com> wrote