Topic Last Modified: 2010-11-12

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
Sample Interval	600
Server Role	Ex14. Mailbox
Warning Threshold	500
Rule Path	Microsoft Exchange Server/Exchange 2010/Mailbox/Database Copy Corruption
Rule Name	The database copy is experiencing an unusually high log generation checkpoint depth for a sustained period of at least 15 minutes.

Explanation

The Log Generation Checkpoint Depth performance counter reports the number of transaction log files that have not yet been saved to the database. This number represents the number of transaction log files that must be replayed to the database if the Microsoft Exchange Information Store service process (Store.exe) stops and has to be restarted. As the log file generation depth increases, the Exchange Information Store startup time increases.

This alert indicates that the checkpoint depth is unusually high. The transaction log file depth may grow during periods in which the server is busy. However, large values typically occur when a backup fails or when there is some other process failure.

User Action

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

Check whether a failure has occurred, or whether any application is causing the Exchange Information Store to fail. Resolve the cause of the failure so that the checkpoint depth starts to decrease.
Check whether a backup process has failed.

If the issue persists, contact Microsoft Product Support Services. For information about how to contact support, visit the Contact Us page of the Microsoft Help and Support Web site.

Note:
If you are not already doing so, consider running the Microsoft Exchange tools that help administrators analyze and troubleshoot an Exchange environment. These tools can help you keep your configuration 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. To run these tools, open the Toolbox node of the Exchange Management Console. For more information about how to use these tools, see Toolbox in Microsoft Exchange Server 2007 Help.

Note:

If you are not already doing so, consider running the Microsoft Exchange tools that help administrators analyze and troubleshoot an Exchange environment. These tools can help you keep your configuration 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. To run these tools, open the Toolbox node of the Exchange Management Console. For more information about how to use these tools, see Toolbox in Microsoft Exchange Server 2007 Help.

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.