MSExchange Replication: CopyQueueLength - sustained for 5 minutes - Red(>15)
Topic Last Modified: 2007-11-16
The Microsoft Exchange Server 2007 Management Pack for Operations Manager includes a performance data collection engine that is used to query performance counter objects on computers that are running Exchange Server 2007. For this Operations Manager rule, data is collected using the performance counter specified in the Details table.
To review the value of the performance counter that generated this alert, in the Operator Console, select this alert, and then click the Properties tab.
Details
Product Name |
Exchange |
Product Version |
8.0 (Exchange Server 2007) |
Event Source |
MSExchange Replication |
Counter Name |
CopyQueueLength |
Instance Name |
<All> |
Sample Interval (in seconds) |
60 |
Server Role |
Ex. Mailbox |
Critical Error Threshold |
>15 |
MOM Rule Path |
Microsoft Exchange Server/Exchange 2007/Mailbox/Continuous Replication |
MOM Rule Name |
MSExchange Replication: CopyQueueLength - sustained for 5 minutes - Red(>15). |
Explanation
The CopyQueueLength performance counter shows the number of transaction log files per storage group that are queued to be copied to the passive node in a clustered mailbox server.
Cluster continuous replication (CCR) is a high availability feature of Microsoft Exchange Server 2007 that combines the asynchronous log shipping and replay technology built into Exchange 2007 with the failover and management features provided by the Cluster service. CCR uses the database failure recovery functionality in Exchange 2007 to enable the continuous and asynchronous updating of a second copy of a database with the changes that have been made to the active copy of the database. To learn more about CCR, see Cluster Continuous Replication.
This alert indicates that 15 or more transaction logs are waiting to be copied to the passive node for 5 minutes. Server reboots, service restarts, network problems, and mailbox moves can cause the copy queue to grow.
User Action
To resolve this error, do one or more of the following:
Verify the health of the storage group copies using the Get-StorageGroupCopyStatus cmdlet. For detailed steps about verifying the health of the storage group copies, see How to View the Status of a Cluster Continuous Replication Copy Using the Exchange Management Shell.
Verify that the replication service is started on both nodes of the cluster.
Verify network connectivity between the active node and the passive node.
If you are having difficulty resolving the issue, contact Microsoft Product Support. For information about contacting support, visit the Contact Us page of the Microsoft Help and Support Web site.
If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.
For More Information
To learn more about cluster continuous replication, see Cluster Continuous Replication.
For more information about managing cluster continuous replication, Managing Cluster Continuous Replication.
For detailed steps about verifying storage group copies, see How to View the Status of a Cluster Continuous Replication Copy Using the Exchange Management Shell.
For detailed steps about verifying a cluster continuous replication copy using Exchange Server Database Utilities (Eseutil.exe), see How to Verify a Cluster Continuous Replication Copy Using ESEUTIL.
To search the Microsoft Knowledge Base articles based on criteria that generated this alert, visit the Microsoft Help and Support Web site.