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

  • ID:  SMSv4_Perf_Threshold__MP_DDR_Backlog__10000_over_3_hours_17_Rule.AdvancedAlertCriteriaMonitor
  • Description:   
  • Target:  ConfigMgr Server
  • Enabled:  Yes

Operational States

Name State Description
AlertLevelSuccess Success  
AlertLevelWarning Warning  
AlertLevelError Error  

Overridable Parameters

Parameter Name Default Value Description Override
ErrorThreshold 10000  
WarningThreshold 5000  

Alert Details

Monitor State Message Priority Severity Auto Resolution
  (Warning) ConfigMgr 2007 Perf Threshold: MP DDR Backlog > 10,000 over 3 hours Medium Match Monitor Health Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

The total number of queued data discovery records (DDRs) on the management point has exceeded the standard operational threshold. This condition will increase unless it is resolved. If the queued management point DDR count keeps going beyond the threshold, discovered information will not be reflected in the Configuration Manager site database in a timely manner, and collections and reports may 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 incoming rate of DDRs.

  • 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 with the 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 site.

  • Determine whether the increased 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 may 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 longer interval for DDRs to be processed.

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

External References

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

For information about Configuration Manager Backup, see Planning for Backup and Recovery at the Configuration Manager Documentation Library Web page.

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

See Also for System Center Configuration Manager Management Pack


Downloads for System Center Configuration Manager Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED