Repairing damaged SQL physical node

#21

BOL has instructions. Look up Failover Clustering in the index for a set of
step by step instructions. Personally, I would evict the damaged node, test
and repair the hardware if necessary, then reload the OS and re-add it to
the cluster and re-install SQL. Finally, you can re-install the service
pack. If you have to reinstall a hotfix, there are additional steps that
are not completely documented. I blogged about how to work around this
here:

http://weblogs.sqlteam.com/geoffh/ar...Breakable.aspx

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

"Bill Bradley" <BillBradley (AT) discussions (DOT) microsoft.com> wrote

Quote:

We have a 2-node Server 2003 SP1 cluster with SQL 2005 SP1. We had a
series
of power outages, and, the "B" node was damaged and won't run the cluster
service. In addition, it looks like the \BIN file under SQL is missing,
so,
SQL won't start on that node, either. A node is fine, runs cluster and
databases are up.

What to do to repair the B node. Unsure if we should evict the node and
just nuke and reload server 2003 and SQL (if we do, it wouldn't load as
clustered?). We tried reloading/repairing SQL on that node, and, it
wouldn't
as "it's already installed".

Searched MS and Google, and, didn't really come up with any documentation
on
how to repair or proceed.

Any ideas?

Thanks!

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Repairing damaged SQL physical node

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering

Re: Repairing damaged SQL physical node - 04-18-2008 , 11:30 AM