The following table shows passive database copy I/O latency requirements counters.
When these values are exceeded, the database copy may lag by not replaying logs to the passive database copy fast enough. The following table shows a replay log I/O latency requirements counter.
This topic describes performance and scalability counters relevant to the Mailbox server role in Microsoft Exchange Server 2010.
You can use Performance Monitor (perfmon.exe) to monitor these counters.
For example, users may experience slow system performance and message delivery delays.
The following table shows active log I/O latency requirements counters.
For more information, see Performance Monitor Getting Started Guide.
For information about other counters relevant to Exchange 2010, see Performance and Scalability Counters and Thresholds.
For information about how clients are affected when overall server RPC averaged latencies increase, see Understanding Client Throttling Policies.The following table shows active database copy input/output (I/O) latency requirements counters.When these values are exceeded, the client experience degrades.If this counter is nonzero for a long period of time, the log buffer size may be a bottleneck.
If checkpoint depth increases continually for a sustained period, this indicates either a long-running transaction, (which will impact the version store), or a bottleneck involving the database disks.Shows the number of log records that can't be added to the log buffers per second because the log buffers are full.