SQL CLUSTER Urgent help

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Sandeep Figer - 28 Dec 2005 02:38 GMT

Hi,

I need urgent help on SQL 2000 cluster based on Windows 2003 SP1. I have
SQl 2000 cluster with one virtual server on Windows 2003 connected to HP
EVA 5000 SAN. One of my node failed & did basic steps like Evict the
node & so on from exisitng setup. Later I built the node again with OS.
Later on configured the node for SAN to have access for shared resources
if needed. Later I run cluster service setup from the node which had
resources online & it successfully added the second node to the cluster.
I could failover Cluster Group from node 1 to 2 & vice versa but not the
sql group as it says node unavailable. I guess I have to add the new
node to Virtual server as well. I than tried to Run SQL 2000 setup to
add this second node to SQL virtual serverr. on the screen needed to add
this node name, I see my new node in the options for "unavailable node".
I can click next where it asks me clusteradmin account name but not sure
if that would be correct as I do not get option to a.s this new node.
Would appreciate if you could let me know what could be an issue. One of
the document on the net said the one needs to shutdown Active node first
before running cluster service setup so that the newly build node could
have access to quorum disk. I did not do that but still it could
identify all resources

Currently my sql server is one 1st node. I am not sure if I need to
install SQL server agin on the new node I built or just the service
pack. Please help..

Regards,
Sandeep

Reply to this Message

Geoff N. Hiten - 28 Dec 2005 15:12 GMT

When you remove a node from a SQL cluster, you need to run two processes.
First, you need to remove the node from teh SQL installation, then you need
to evict the node. You can run them in reverse order, but it takes longer
since the remote tasks have to time out. Here is how you get out of this
mess.

Evict the replaced node from the cluster.

Run SQL Setup on the existing node. Remove the failed node from SQL. This
will clean up all the registry and configuration information associated with
the failed node.

Re-add the replaced node to the cluster.

Run SQL Setup on the existing node. Add the newly replaced node to the SQL
installation.

Re-run any service packs and hotfixes that were on the original cluster to
update the binaries on the new node. Note: this step may take the SQL
instance offline.

Good luck,

Signature

Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP

> Hi,
>
[quoted text clipped - 26 lines]
>
> *** Sent via Developersdex http://www.developersdex.com ***

Reply to this Message