Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am testing the failover policies of our test failover cluster system. When I shutdown the node who is currently controlling the cluster (NODE1), it takes about 2 mins and 40 seconds before the next node on the preferred list (NODE2) takes control of the cluster.

I tried changing the looksAlive and isAlive interval to 5000ms to all resources, but that didn't help. Looking at the Event Viewer of the remaining nodes, it shows that it was almost instantly detected that NODE1 was down. But it took another ~2:40 minutes for it to be removed from the live cluster list and for NODE2 to take over.

Is there anyway of changing or shortening this "failover delay"? This is the setup of the cluster:

  • (1) One ClusterDC connected to the public network
  • (3) Three nodes running Win2003 with a quorum type of MNS
  • Private network is connected to network hub
                   ________________                       _________________
(ClusterDC)=------=|              |=------=(Node1)=------=|               |  
                   |Public Network|=------=(Node2)=------=|Private Network|
                   |   (Switch)   |=------=(Node3)=------=|     (Hub)     |
                   ----------------                       -----------------
share|improve this question

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.