ConfigMgr 2007 Perf Threshold: MP DDR Backlog > 10,000 over 3 hours

Summary

The total number of queued data discovery records (DDRs) on the management point has exceeded the standard operational threshold. This condition increases unless it is resolved. If the queued management point DDR count continues beyond the threshold, discovered information is not reflected in the Configuration Manager site database in a timely manner, and collections and reports might not accurately represent the devices on the network.

Causes

The management point DDR backlog can exceed the threshold because:

• The SMS Agent Host service (CCMexec) is not running.

• The management point DDR processing rate is slower than the DDR incoming rate.

• The management point has insufficient resources, such as CPU, memory, or disk space.

• A large number of clients has recently been discovered.

• A remote management point has lost connectivity to the Configuration Manager site database server.

Resolutions

To resolve this issue and lower the number of queued management point DDRs:

• Verify that the SMS Agent Host service (CCMexec) is running. If it is stopped, start it. If you encounter errors when starting it, make sure logging is enabled for the service and examine the CCMexec.log file.

• Verify that the threshold for this alert is not too low and is beyond the standard operating threshold for this specific Configuration Manager site.

• Determine whether the increased DDR load is due to an infrequent influx of new discovery records, or whether the DDR load remains relatively constant. If the load is constant, update the Configuration Manager infrastructure to achieve zero processing backlogs. If the load is due to a large number of newly discovered computers, the issue can resolve itself if there are sufficient resources to process pending DDRs in addition to the standard DDR load. To verify the DDR processing rate trend, see the "Other Information" section later in this article for the procedure to enable the counters and view the graph.

• Plan the type and frequency of your discovery methods carefully. Conduct performance testing to verify that the infrastructure can accommodate the discovery load. Adjust the frequency of discovery to allow for a longer interval for DDRs to be processed.

• If the management point is a remote management point, verify that it can connect to the Configuration Manager site database server.

Additional

This alert is best handled by Configuration Manager administrators.

If this alert is generating too many false positives, you can modify the threshold tab of the rule properties to designate values that are more appropriate for your environment.

Related Events:

You can also look for alerts that relate to the SMS_Executive service being stopped or the management point having insufficient resources (such as CPU, memory). These alerts are the potential cause of the DDR alert. Depending on the cause, it is likely that other types of backlogs (hardware inventory, software inventory, software metering) on the management point are also increasing and corresponding alerts are occurring.

External

For more information about server sizing, see Planning and Deploying the Server Infrastructure for Configuration Manager 2007 in the Configuration Manager Product Documentation Web page.

For more assistance, see the list of additional support options in the support section of the Configuration Manager Web site at Support for Configuration Manager.