How to Configure Tolerance Settings for Missed Cluster Heartbeats

Exchange 2007

Microsoft Exchange Server 2007 will reach end of support on April 11, 2017. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.


Applies to: Exchange Server 2007, Exchange Server 2007 SP1, Exchange Server 2007 SP2, Exchange Server 2007 SP3

Topic Last Modified: 2007-08-23

This topic explains how to use Cluster.exe to configure tolerance settings for missed cluster heartbeats when using cluster continuous replication (CCR).

To perform this procedure, the account you use must be delegated full control administrative permissions on the cluster.

For more information about permissions, delegating roles, and the rights that are required to administer Exchange Server 2007, see Permission Considerations.

The following procedure includes making changes to the cluster's configuration and then stopping and restarting the Microsoft Windows Server Cluster service on each node, one at a time. When you perform the following procedure, restart the Cluster service only on passive nodes. This action means that you will move all cluster resource groups from the active node to a passive node. If a clustered mailbox server exists, make sure that you move it and the default cluster group to a passive node (thereby making the passive node an active node and the previously active node a passive node) before stopping and restarting the Cluster service. Restarting the Cluster service on an active node will cause a failover of all resource groups that are hosted on the active node. If you are using a file share witness, make sure that the file share host is continuously available while this procedure is being performed. If the file share witness is not available, quorum will be lost and the cluster will remain offline.

  1. Verify that all nodes in the cluster are online. To do this, run the following command:

    cluster ClusterName Node
  2. Examine the output of the preceding command and verify that the Status for each node is Up.

  3. Configure the number of missed heartbeats for all private and mixed interfaces on all nodes. To do this, run the following command:

    cluster ClusterName /priv HeartBeatLostInterfaceTicks=10:DWORD 
    cluster ClusterName /priv HeartBeatLostNodeTicks=10:DWORD
    You must specify the DWORD string when you set private properties.
  4. An error message will appear (System error 3011). This is normal and expected. Stop, and then restart the Cluster service on each node in the cluster, one at a time, after first verifying that the node is a passive node. You run the following commands on each node to restart the Cluster service:

    net stop clussvc
    net start clussvc