Topic Last Modified: 2010-08-15

The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager includes a performance data collection engine that is used to query performance counter objects on computers running Exchange 2010. For this Operations Manager rule, data is collected by using the performance counter specified in the Details table.

To review the value of the performance counter that generated this alert, in Operations Manager, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.


Product Name


Product Version

14.0 (Exchange 2010)

Object Name

MSExchange Database ==> Instances

Counter Name

IO Log Read Average Latency

Sample Interval


Server Role

Ex14. Mailbox

Critical Error Threshold


Rule Path

Microsoft Exchange Server/Exchange 2010/Mailbox/Database Copy Log Logical Disk Performance

Rule Name

The passive database copy is experiencing a critically high log file read latency. The rate is sustained for at least 5 minutes.


This alert indicates that a performance issue may affect the passive mailbox database copy in a particular Microsoft Exchange Server 2010 database availability group (DAG).

Exchange 2010  uses continuous replication to create and maintain database copies. To maintain a synchronized copy of a mailbox database, transaction log files from the active mailbox server are copied to the passive Mailbox server in the DAG, and then replayed into the passive database. This provides high availability and resiliency in the Exchange environment.

A database availability group (DAG) is a set of Mailbox servers that provide automatic recovery from failures that affect individual databases. Any server in a DAG can host a copy of a mailbox database from any other server in the DAG. When a server is added to a DAG, it works with the other servers in the DAG to provide automatic recovery from failures that affect mailbox databases.

A failover cluster is automatically created when you add a server to a DAG. You can add additional mailbox servers to the DAG up to a maximum of 16. These servers become part of the failover cluster and are monitored for network or server failures. The failover cluster heartbeat mechanism and cluster database are used to track and manage information about the DAG, such as database mount status, replication status, and last mounted location.

System Center Operations Manager monitors the database copy process to determine whether it is experiencing log file read latency. As a general guideline, a problem may exist when the average time to read from the database log file copy location is more than 60 milliseconds (ms) over a 5-minute period.

In this scenario, you may experience delays that affect the replication process. If log files are not copied to the passive Mailbox server in a timely manner, they may not be played into the passive database copy. Therefore, the passive database may no longer be synchronized with the active Mailbox database.

User Action

To resolve this error, do one or more of the following:

  • Review the Application log and System log on your Exchange 2010 servers for related events. For example, events that occur immediately before and after this event may provide more information about the root cause of this error.

  • Review the Operations Console in Operations Manager for detailed information about the cause of this problem. For more information, see the "Introduction" section in this article.

  • Check the following performance counter by using Windows Reliability and Performance Monitor:

    • Object: MSExchange Database Instances

  • Examine the network topology between the Mailbox server and any connected storage resources.

  • Examine the System log to determine whether any issues are affecting the disk subsystem.

  • Examine the memory and CPU usage on the passive mailbox server to determine whether a memory bottleneck is causing additional disk I/O latency.

  • Examine the current replication status for each replica database. To do this, use the Get-MailboxDatabaseCopyStatus cmdlet. This cmdlet returns information about all copies of a particular database, information about a specific copy of a database on a specific server, or information about all database copies on a server.

For more information, see the following topics in Exchange 2010 Help:

  • Understanding Mailbox Database Copies

  • Understanding Database Availability Groups

For More Information

If you are not already doing so, consider running the Exchange tools created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.