Fail over policies in Cluster 2012

if the clustered role fails more than the maximum time period specified, it will be left in failed state.

What is this settings? I don't want cluster group to go into failed into state rather than I want to move into Passive node.

Problem Now:

One of my resource is failing and my cluster group goes into PENDING state instead of moving into passive node.

Any solution guys?

July 30th, 2015 11:20am

It sounds like there is an issue with your cluster. By default, the cluster will first try to restart the application on the current node. If it can't do that, it will automatically try to start it on another node in the cluster. Have you looked at the event log to see what is preventing it from starting on the second node? My hunch is that it is trying, but it is failing there. Since it fails, it shuts the process down.
Free Windows Admin Tool Kit Click here and download it now
July 30th, 2015 5:47pm

You mean, if application shuts down on the current node and there is no way to get up on the passive node?

Regards,

Karthikeyan R

July 31st, 2015 3:25am

Hi Karthik,

Please check if passive node is set as possible owner for the resources. It could be that, as Tim mentioned, it may be failing because of that. Also, you can try to do manual failover and see if it fails in other node. If it fails, there must be something wrong either in the passive node or with configuration. Check in event logs for any clues.

-Umesh.S.K

Free Windows Admin Tool Kit Click here and download it now
July 31st, 2015 3:39am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics