The total number of queued data discovery records (DDRs) on the site server has exceeded the standard operational threshold. This condition will increase unless it is resolved. If the queued site server DDR count keeps going beyond the threshold, discovered information will not be reflected in the SMS site database in a timely manner, and collections and reports may not accurately represent the devices on the network.
The total number of queued DDRs can exceed the threshold because:
The SMS Executive service is stopped or not responding on the site server.
Discovery Data Manager could be processing changes to site boundaries or the parent site, or it could be sending inventory details to a new parent site. These changes take priority over normal DDR processing, which is suspended until they are processed.
The site server DDR processing rate is slower than the incoming rate of DDRs.
The site server has insufficient resources such as CPU, memory, or disk space.
The SMS site database has no more space.
A large number of clients has recently been discovered.
The site server may have lost connectivity with the SMS site database server.
To resolve this issue and lower the number of queued DDR files:
Verify that the threshold for this alert is not too low and is beyond the standard operating threshold for this specific SMS site.
Verify that the SMS Executive service is running on the site server. If it is stopped or not responding, restart the service.
Verify that the SMS site database is performing properly.
Determine whether the increased load is due to an infrequent influx of new data discovery records, or whether the DDR load remains relatively constant. If the load is constant, update the SMS infrastructure to achieve zero processing backlogs. If the load is due to a large number of newly discovered client machines, the issue may resolve itself if there are sufficient resources to process pending DDRs in addition to the standard DDR load.
Verify that the SMS site database has sufficient space. If the database is set to autogrow, verify that there is sufficient disk space for the database to expand.
Plan the type and frequency of your discovery methods carefully. Conduct performance testing to verify the infrastructure can accommodate the discovery load. Adjust the frequency of discovery to allow for longer interval for DDRs to be processed.
Modify the discovery configuration to discover fewer resources.
Verify that the site server can connect to the SMS site database server.
For more information about server sizing, see Scenarios and Procedures for Microsoft Systems Management Server 2003: Planning and Deployment at the Systems Management Server 2003 Product Documentation Web page.
For more information about backlogs and site maintenance, see Scenarios and Procedures for Microsoft Systems Management Server 2003: Maintenance, Backup and Recovery at the Systems Management Server 2003 Product Documentation Web page.
For more information about troubleshooting discovery data processing, see Troubleshooting Flowcharts at the Systems Management Server 2003 Product Documentation Web page.
For more assistance, a list of additional support options is available in the support section of the SMS Web site at Support for Systems Management Server.
If this alert is generating too many false positives, you can modify the threshold tab of the rule properties to designate values more appropriate for your environment.
To view a graph that plots the trend in processing rates for DDRs on site servers:
In the Operations Manager 2007 Operations Console, select Monitoring and then expand Microsoft Systems Management Server (SMS) 2003, expand Performance, expand Processing Rates, and then click Site Servers.
Click DDRs/minute in the last 24 hours.
Processing rates will not show on the graph unless the corresponding performance measure is enabled first. To enable the performance measure for DDR backlog:
In the Operations Manager 2007 Operations Console, select Authoring and then Rules.
In the details pane, expand Microsoft SMS 2003 Site Servers Installation right-click Site Server DDR Backlog, and then click Enable.
This alert is best handled by SMS administrators.
Related Events
You can also look for alerts relating to the SMS Executive service being stopped or the site server 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 site server are also increasing and corresponding alerts are occurring.
| Target | Microsoft.SMS.2003.SMS_Server_Class | ||
| Parent Monitor | SS | ||
| Category | StateCollection | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | MatchMonitorHealth | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | System.Mom.BackwardCompatibility.PerformanceThreshold.ThreeStateMonitorType | ||
| Remotable | True | ||
| Accessibility | Internal | ||
| Alert Message |
| ||
| RunAs | Default | ||
| Comment | Mom2005ID='{C111F0C8-0495-4AF9-B159-7E76D4B99759}' |
Home
ENU <UnitMonitor ID="SMS_2003_Perf_Threshold__Site_Server_DDR_Backlog__10000_over_3_hours_4_Rule.AdvancedAlertCriteriaMonitor" TypeID="MomBackwardCompatibility!System.Mom.BackwardCompatibility.PerformanceThreshold.ThreeStateMonitorType" Accessibility="Internal" Target="Microsoft.SMS.2003.SMS_Server_Class" Enabled="true" ParentMonitorID="SS" Comment="Mom2005ID='{C111F0C8-0495-4AF9-B159-7E76D4B99759}'">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="SMS_2003_Perf_Threshold__Site_Server_DDR_Backlog__10000_over_3_hours_4_Rule.AdvancedAlertCriteriaMonitor.StringResource">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/Name$</AlertParameter1>
<AlertParameter2>$Data/Context/Description$</AlertParameter2>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState HealthState="Success" MonitorTypeStateID="Success" ID="AlertLevelSuccess"/>
<OperationalState HealthState="Warning" MonitorTypeStateID="Warning" ID="AlertLevelWarning"/>
<OperationalState HealthState="Error" MonitorTypeStateID="Error" ID="AlertLevelError"/>
</OperationalStates>
<Configuration>
<ServerRole>SMS Server</ServerRole>
<Component>SS</Component>
<ServerRoleInstance>$Target/Property[Type="Microsoft.SMS.2003.SMS_Server_Class"]/Name_1$</ServerRoleInstance>
<RuleId>$MPElement[Name="SMS_2003_Perf_Threshold__Site_Server_DDR_Backlog__10000_over_3_hours_4_Rule"]$</RuleId>
<ErrorThreshold>10000</ErrorThreshold>
<ErrorOperator>Greater</ErrorOperator>
<WarningThreshold>5000</WarningThreshold>
<WarningOperator>Greater</WarningOperator>
</Configuration>
</UnitMonitor>