The "Test-Replicationhealth" cmdlet fails on a stretched cluster in an Exchange Server 2007 SP3 CCR environment


In a Microsoft Exchange Server 2007 SP3 cluster continuous replication (CCR) environment, you stretch the cluster to have nodes that are located in different physical sites. However, when you run the Test-Replicationhealth cmdlet, the first check (ClusterNetwork) fails. Additionally, you receive an error message that resembles the following:

Node '<cluster node name>' has HostName '<host name>' configured for log file copying over network '<network name>', but no other node in the cluster has a HostName configured on this network. Log file copying cannot occur over network '<network name>' until another node also has a HostName configured.

Additionally, when you use System Center Operations Manager (SCOM) to monitor the health status of the cluster, the SCOM task also fails on the first check. Therefore, you cannot obtain more information about the remaining checks, such as QuorumGroup, FileShareQuorum and CmsGroup.

Note Stretched clusters are also known as geographically dispersed clusters or extended clusters. They can provide failover if there is a site loss because of power issues, natural disasters or other unforeseen events.


To resolve this issue, install the following update rollup:

2530488 Description of Update Rollup 3 for Exchange Server 2007 Service Pack 3


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information about cluster continuous replication, visit the following Microsoft website:

Cluster Continuous Replication

For more information about the Test-ReplicationHealth cmdlet, visit the following Microsoft website:


For more information about how to configure clustering in Exchange Server 2007, visit the following Microsoft website:

Configuring Clustering in Exchange Server 2007