March 15, 2008 at 12:13 am
Does anyone have any ideas about why the cluster group will not move to the primary node when selected to? The group failed over to the secondary node and is running fine there. But when I tried to move it to the primary node, it just goes back online on the secondary node again. No error messages.
I don't see anything obviousy wrong on the primary server.
Any ideas what I should look for?
Thanks very much.
March 15, 2008 at 5:21 pm
Can you click on the cluster group your trying to move and see what node it has set in here to move to...lets say you have CL1 and CL2 and now CL1 is on CL2
can you click on CL1 and see if the parameter is set for CL2 (i cannot remember exact names in the cluster her doing from memory).
Also look for the cluster.log i believe this is on the windows systems and see what the errors are saying.
Failing this you could take offline completely then bring back online.
March 15, 2008 at 7:10 pm
Check your dependencies; see if any of them are failing to come up on the primary node. For instance, if a disk volume that SQL is dependent on cannot be mounted on the Primary, then SQL will not come up on it.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
March 15, 2008 at 7:15 pm
Thats the word dependencies could not think without looking at it.
Look at the cluster.log (may give you some reason here).
March 17, 2008 at 6:32 am
I did find a couple error messages. It looked like node one couldn't see the SAN where the data files are. We rebooted node one and that solved the problem. The cluster group did move to one. Thanks for your help!
March 17, 2008 at 6:49 am
Thats great.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply