The Transport queue database is experiencing an unusually high log generation checkpoint depth over last 15 min - Yellow(>400)
Applies to: Operations Manager Management Pack for Exchange 2010
Topic Last Modified: 2011-08-02
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.
Details
Product Name |
Exchange |
Product Version |
14.0 (Exchange 2010) |
Object Name |
MSExchange Database ==> Instances |
Counter Name |
Log Generation Checkpoint Depth |
Instance Name |
EdgeTransport/Transport Mail Database |
Sample Interval |
300 |
Server Role |
Ex14. Common |
Warning Threshold |
400 |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Common Components/Hub Transport and Edge Transport/Transport |
Rule Name |
The Transport queue database is experiencing an unusually high log generation checkpoint depth over last 15 min - Yellow(>400). |
Explanation
The Log Generation Checkpoint Depth performance counter provides a count of log files that represents the database file changes that would have to be redone or undone if the process crashes.
This Warning event indicates that the Log Generation Checkpoint Depth has been greater than 400 for the past 15 minutes.
User Action
To resolve this problem, do one or more of the following:
Run the Microsoft Exchange Mail Flow Troubleshooter. To access the Mail Flow Troubleshooter, click Toolbox in the Exchange Management Console.
If you believe that an application is accessing or placing locks on the transaction log files, stop running the suspected application to determine whether that is the cause of the problem. Additionally, consider configuring the application so that it does not access the Microsoft Exchange folder and all the folder's subfolders. The Microsoft Exchange Transport service does not start if another application locks the queue database file, mail.que. After the Microsoft Exchange Transport service starts, no other application can access or lock mail.que. However, the log files can be accessed and locked by other applications.
Evaluate disk I/O performance. For information about how to monitor disk performance by using Performance Monitor, see Performance and Reliability Monitoring Step-by-Step Guide for Windows Server 2008.
If disk performance is the issue, and if other storage is available, consider moving the transport mail.que file and your transaction log files to a different location.
For More Information
If you are not already doing so, consider running the Exchange tools, which have been 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 and improve mail flow. 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.