Troubleshooting

Migrating Exchange 2010 To Dell Advanced Infrastructure Manager Environment
Page 24
Figure 8. Exchange 2010 active database latencies
Figure 9. Exchange 2010 passive database latencies
The average write latency for an active copy should be less than 20 ms, and indicates the time it takes
to write to a database file. Latencies on passive copies are typically higher since the IO size is larger.
Note that higher passive copy latencies will have no impact on end-user experience and functionality.
There is an increase in the passive database read latency when using personas in trunk mode but these
values were well within the 200 ms threshold provided by Microsoft. The database page fault stalls/sec
counter indicates the number of page faults that cannot be serviced because there are no pages
available in the database cache. This value is 0 as desired.