I have a 2 node cluster with 2 instances of SQL 2000 SP4, Node one failed
on the cluster and I had to reinstalled the OS.

I got the OS installed and the joined the existing cluster. No problem
there. The problem is I need to reinstall the SQL software on the newly
reinstalled node, but when I run the reinstall the only option for each
instance is to remove SQL. The cluster is setup as active/passive and the
SQL is production so uninstalling the SQL from the cluster and reinstalling
SQL back on the the cluster is not an option.

Currently all instances are running on the second node. What I would like
to do is install SQL and then fail the existing group back over.

Any suggestions?

Thanks,
Alex

If you reused the original node name, then this can get confusing.

You do need to uninstall SQL from the failed node. This step tells SQL that
it is no longer installed to the failed node. You will see some timeout
errors since it cannot find the original node or the installation.

Once SQL sees itself as being installed on one node, you can reinstall it to
the other node and patch it to match.

See "Maintaining a Failover Cluster" in BOL.

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



"Alex H" <alex (AT) sonance (DOT) com> wrote

If you reused the original node name, then this can get confusing.

You do need to uninstall SQL from the failed node. This step tells SQL that
it is no longer installed to the failed node. You will see some timeout
errors since it cannot find the original node or the installation.

Once SQL sees itself as being installed on one node, you can reinstall it to
the other node and patch it to match.

See "Maintaining a Failover Cluster" in BOL.

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



"Alex H" <alex (AT) sonance (DOT) com> wrote

If you reused the original node name, then this can get confusing.

You do need to uninstall SQL from the failed node. This step tells SQL that
it is no longer installed to the failed node. You will see some timeout
errors since it cannot find the original node or the installation.

Once SQL sees itself as being installed on one node, you can reinstall it to
the other node and patch it to match.

See "Maintaining a Failover Cluster" in BOL.

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



"Alex H" <alex (AT) sonance (DOT) com> wrote

If you reused the original node name, then this can get confusing.

You do need to uninstall SQL from the failed node. This step tells SQL that
it is no longer installed to the failed node. You will see some timeout
errors since it cannot find the original node or the installation.

Once SQL sees itself as being installed on one node, you can reinstall it to
the other node and patch it to match.

See "Maintaining a Failover Cluster" in BOL.

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



"Alex H" <alex (AT) sonance (DOT) com> wrote

If you reused the original node name, then this can get confusing.

You do need to uninstall SQL from the failed node. This step tells SQL that
it is no longer installed to the failed node. You will see some timeout
errors since it cannot find the original node or the installation.

Once SQL sees itself as being installed on one node, you can reinstall it to
the other node and patch it to match.

See "Maintaining a Failover Cluster" in BOL.

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



"Alex H" <alex (AT) sonance (DOT) com> wrote

If you reused the original node name, then this can get confusing.

You do need to uninstall SQL from the failed node. This step tells SQL that
it is no longer installed to the failed node. You will see some timeout
errors since it cannot find the original node or the installation.

Once SQL sees itself as being installed on one node, you can reinstall it to
the other node and patch it to match.

See "Maintaining a Failover Cluster" in BOL.

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



"Alex H" <alex (AT) sonance (DOT) com> wrote

If you reused the original node name, then this can get confusing.

You do need to uninstall SQL from the failed node. This step tells SQL that
it is no longer installed to the failed node. You will see some timeout
errors since it cannot find the original node or the installation.

Once SQL sees itself as being installed on one node, you can reinstall it to
the other node and patch it to match.

See "Maintaining a Failover Cluster" in BOL.

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



"Alex H" <alex (AT) sonance (DOT) com> wrote

If you reused the original node name, then this can get confusing.

You do need to uninstall SQL from the failed node. This step tells SQL that
it is no longer installed to the failed node. You will see some timeout
errors since it cannot find the original node or the installation.

Once SQL sees itself as being installed on one node, you can reinstall it to
the other node and patch it to match.

See "Maintaining a Failover Cluster" in BOL.

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



"Alex H" <alex (AT) sonance (DOT) com> wrote

If you reused the original node name, then this can get confusing.

You do need to uninstall SQL from the failed node. This step tells SQL that
it is no longer installed to the failed node. You will see some timeout
errors since it cannot find the original node or the installation.

Once SQL sees itself as being installed on one node, you can reinstall it to
the other node and patch it to match.

See "Maintaining a Failover Cluster" in BOL.

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



"Alex H" <alex (AT) sonance (DOT) com> wrote