Have an 2 node A/P EX2003 SP2 cluster constantly failing over from one node to other. Sounds like a cliche but suddenly started happening yesterday at 3:15 nothing changed since put in 3 months ago. Anyone any idea's as to where to start trouble shooting?
System event log and cluster log should give some clues. "nicholspr" wrote in message news:FFFD48EA-FA4F-4A04-BE93-8EA9FEECF436@microsoft.com... > Have an 2 node A/P EX2003 SP2 cluster constantly failing over from one > node > to other. > Sounds like a cliche but suddenly started happening yesterday at 3:15 > nothing changed since put in 3 months ago. > Anyone any idea's as to where to start trouble shooting?
Wich resource is failing? "nicholspr" wrote: > Have an 2 node A/P EX2003 SP2 cluster constantly failing over from one node > to other. > Sounds like a cliche but suddenly started happening yesterday at 3:15 > nothing changed since put in 3 months ago. > Anyone any idea's as to where to start trouble shooting?
Find the resource that is failing like David mentioned, if it is not a critical resource (ie. POP3 or IMAP) set the properties to not affect the group. If it is a critical resource after trying some of other ideas (and going through your logs like John mentioned), you may want to think about rebuildig that resource. Look at your settings for how many times the resources are allowed to fail over and how long they are set to try to bring online before initiating a failure on the resource to eliminate the potential endless loop of flipping back and forth. You may also want to consider taking the resource group offline to stop it from failing over. Reboot your passive (2nd) node, then bring the resources backonline and let them fail over to the passive node, see if that stops the flipping. If it does, reboot your 1st node and see if you can move resources back cleanly. "David Figueiredo" wrote in message news:534F4AA6-279E-447F-9DD3-95248088A695@microsoft.com... > Wich resource is failing? > > "nicholspr" wrote: > >> Have an 2 node A/P EX2003 SP2 cluster constantly failing over from one >> node >> to other. >> Sounds like a cliche but suddenly started happening yesterday at 3:15 >> nothing changed since put in 3 months ago. >> Anyone any idea's as to where to start trouble shooting?
