![]() | |
![]() |
| | Thread Tools | Display Modes |
#41
| |||
| |||
|
|
You did exactly right. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "Alex H" <alex (AT) sonance (DOT) com> wrote in message news:8F99FF4B-21D1-4E89-B4B9-A1CA2C99F974 (AT) microsoft (DOT) com... Thanks for the response, I think I have it figured out. I did reuse the original node name. After playing around with the reinstalled node, I was able to run the setup using advanced instance maintenance and remove the failed node from the cluster resource, I then reran the setup instance maintenance and re-added the node. Once that was done I tested the fail over and it seems to work fine. Is there anything else that I should check. Also, for safe measure I reapplied the latest service pack and patches. Thanks, Alex "Geoff N. Hiten" <SQLCraftsman (AT) gmail (DOT) com> wrote in message news:ef0lf6VLJHA.728 (AT) TK2MSFTNGP03 (DOT) phx.gbl... 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 in message news:4E83F5D8-2D95-4F19-BB24-C0E8D20247DB (AT) microsoft (DOT) com... 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 |
![]() |
| Thread Tools | |
| Display Modes | |
| |