Good news and bad news:
Good news is that Microsoft has thought about this and has handy
instructions on how to fix the issue.
The bad news is that the instructions are wrong.
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/3d151d0c-e841-4325-8606-c094de37d7d1.htm
They omit a critical step. You need to go to add/remove programs, run the
SQL Server setup (change, not remove) and remove the failed node from the
configuration before you evict it from the cluster. This will ensure there
is no confusion when you reuse the node name and IP address. Also, you will
need to remove the machine entries from DNS and Active Directory.
Once you have "cleaned out" the leftover information about the old node,
you can proceed with the instructions on installing a new node.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
[quoted text, click to view] "Structured Chaos" <jeffery_tyree@yahoo.com> wrote in message
news:%23pMfK1N6HHA.464@TK2MSFTNGP02.phx.gbl...
> The nightmare has happened... The passive node of a 2-node Active/Passive
> SQL2K5 cluster had a critical drive failure and there is no recovery disk
> or backup to restore from. At this moment only the Active node is running
> (and running fine). I have a server with a clean OS install which I can
> use to replace the failed Passive node but am unsure how to go about this.
> I have not touched any of the current cluster settings/definitions. Any
> help is greatly appreciated.
>
> TIA.
>