Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

cluster group won't move to primary node Expand / Collapse
Author
Message
Posted Saturday, March 15, 2008 12:13 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 8:38 AM
Points: 198, Visits: 412
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.
Post #469785
Posted Saturday, March 15, 2008 5:21 PM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Thursday, July 31, 2014 7:04 PM
Points: 724, Visits: 1,002
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.
Post #469915
Posted Saturday, March 15, 2008 7:10 PM


SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: General Forum Members
Last Login: Thursday, June 5, 2014 10:54 AM
Points: 9,294, Visits: 9,480
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.

-- RBarryYoung, (302)375-0451 blog: MovingSQL.com, Twitter: @RBarryYoung
Proactive Performance Solutions, Inc.
"Performance is our middle name."
Post #469932
Posted Saturday, March 15, 2008 7:15 PM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Thursday, July 31, 2014 7:04 PM
Points: 724, Visits: 1,002
Thats the word dependencies could not think without looking at it.

Look at the cluster.log (may give you some reason here).
Post #469934
Posted Monday, March 17, 2008 6:32 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 8:38 AM
Points: 198, Visits: 412
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!
Post #470177
Posted Monday, March 17, 2008 6:49 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Thursday, July 31, 2014 7:04 PM
Points: 724, Visits: 1,002
Thats great.
Post #470189
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse