Heartbeat for CCR of Exchange 2007 RRS feed

  • 問題

  • We are using two servers to implement CCR of Exchange 2007.

    Currently, we are using 1Gbps network for data and 10Mbps for heartbeat (via a switch).

    In order to get rid of dependency on the switch, we want to use 1Gbps network for Heartbeat using straight cable connecting both servers as I know that straight cable of 1Gbps can form a network.

    Also, we also want to use two cables instead of one to have redundancy.

    I wonder if what is the best practice on heartbeat of CCR.

    2008年8月14日 上午 04:30


  • Dear customer:


    All networks that are used to replicate transaction logs must provide adequate bandwidth and sufficiently low latency to copy the log files in a timely manner, so that whenever possible, there is no backlog of log files.


    It is important that the networks used for client and cluster communications are configured correctly. In addition, you must make sure that the network connection order is configured correctly for the cluster. Consider the following when designing the network infrastructure for your CCR environment:


    • Each node must have at least two network adapters available for Windows Clustering. Clients and other servers only have to be able to access the nodes from one of the two network adapters. The other network adapters are used for intra-cluster communication. The recommended configuration is to have the private network dedicated to internal cluster communications and the public network designated as mixed.

    • The cluster public network should provide connectivity to other Exchange servers and other services, such as Active Directory and DNS. You can prevent this from being a single point of failure by using network adapter teaming or similar technology.

    • A separate cluster private network must be provided. The private network is used for the cluster heartbeat. The private network does not require DNS.

    • Heartbeat requirements may not be the most stringent public network bandwidth and latency requirement for a two datacenter configuration. You must evaluate the total network load, which includes client access, Active Directory, transport, continuous replication, and other application traffic, to determine the necessary network requirements for your environment.

    • We recommend that you use Gigabit Ethernet for CCR environments to maximize reseed time.

    • In Exchange 2007 RTM, a resource group that contains a clustered mailbox server can only have one Network Name resource. Having more than one Network Name resource in a resource group that contains a clustered mailbox server is not supported in Exchange 2007 RTM. However, this limitation does not exist in Exchange 2007 SP1. When the clustered mailbox server has been upgraded to Exchange 2007 SP1, more than one Network Name resource can exist in the resource group that contains the clustered mailbox server.

    For more information about Network Requirements for Cluster Continuous Replication, please refer to “Network Requirements for Cluster Continuous Replication” section in the following documents:

    Planning for Cluster Continuous Replication



    Hope it helps.

    Rock Wang - MSFT

    2008年8月14日 上午 11:20