Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Clustering / December 2005

Tip: Looking for answers? Try searching our database.

SQL 2000 cluster help - Urgent

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Sandeep - 28 Dec 2005 02:41 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
Michael Hotek - 30 Dec 2005 00:21 GMT
That doesn't make any sense.  If the node adds successfully into the cluster
and you can fail the cluster resources over to it without any error
messages, there shouldn't be any reason that SQL Server setup will not allow
you to add the node in.  The only thing I can think of is that there might
be a pending reboot.  Also, do you have MSDTC configured into the cluster?

Signature

Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com

> Hi,
>
[quoted text clipped - 32 lines]
> Regards,
> Sandeep
Sandeep - 30 Dec 2005 02:23 GMT
The problem is fixed. The cluster Group failover was okay but somehow the new
node entry was not in some SQL group dependencies. Bit strange as Cluster
setup does that automatically. After I added manually the second node in
appropriate resource dependencies, everything went smooth.

Regards,
Sandeep

> That doesn't make any sense.  If the node adds successfully into the cluster
> and you can fail the cluster resources over to it without any error
[quoted text clipped - 38 lines]
> > Regards,
> > Sandeep
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.