Article ID: 950306 - View products that this article applies to.
In large Microsoft Systems Management Server (SMS) 2003 hierarchies that have many sites, site-to-site replication slows down.
The volume of files may be larger than you expect in the following folders on a site server:
Note The baseline is defined here as some historical measure of the volume of files in the Inboxes folder structure.
The following conditions can cause backlog scenarios:
When the SMS Scheduler component is processing large quantities of active jobs and send requests, the throughput of the Scheduler component begins to slow. This behavior occurs because of a corresponding increase in processing overhead for the increased quantities of objects.
In some instances, if a large enough queue of data is formed, it can take days or even weeks to be completely processed. The time that is required to process the queued data depends on the many variables that affect replication performance in the hierarchy and in the environment. These variables include disk I/O performance, network speeds, bandwidth restrictions, size of queued data, and object count. When a large queue of backlogged replication data has been formed, adding additional loads increases the time that is required for all data to be processed.
In most cases, the appropriate action for a large backlog of replication data is to first correct any issue that may be preventing processing of replication data. Next, you may have to reduce the quantity of site-to-site replication traffic. Finally, make sure that the SMS_EXECUTIVE service can run uninterrupted to complete processing in a timely manner. Service restarts can add significant overhead. Limiting SMS_EXECUTIVE service restarts is important because the initialization work for the SMS Scheduler component is proportional to the number of jobs, send requests, and routing requests that are currently queued for processing.
Note The SMS_EXECUTIVE service hosts the SMS Replication Manager, SMS Scheduler, and SMS Sender components.
Service Pack InformationTo resolve this problem, obtain the latest service pack for Microsoft System Center Configuration Manager 2007, available from this Microsoft web site: http://www.microsoft.com/downloads/details.aspx?FamilyID=3318741a-c038-4ab1-852a-e9c13f8a8140
Hotfix informationA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Systems Management Server 2003 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
PrerequisitesYou must have SMS 2003 Service Pack 2 (SP2) or SMS 2003 Service Pack 3 (SP3) installed before you apply this hotfix.
Note This hotfix should be applied on all sites in the hierarchy.
Restart requirementYou do not have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix includes several previous hotfixes. These hotfixes include 917435, 927723, and 905751 for SMS 2003 Service Pack 2 (SP2) and 907311 for SMS 2003 Service Pack 3 (SP3).
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
SMS 2003 Service Pack 2
Collapse this tableExpand this table
SMS 2003 Service Pack 3
Collapse this tableExpand this table
This hotfix does not directly eliminate or prevent backlogs. Instead, this hotfix improves the performance of the SMS Scheduler component when a large amount of work is outstanding. After you install this hotfix, you should expect some reduction in the time that is required to recover from a large backlog of replication data. The changes are designed specifically to improve the performance of the SMS Scheduler component by helping it recover more quickly from large backlogs of data. No noticeable performance or throughput increase is expected for sites that are not experiencing a heavy load in the SMS Scheduler component.
Changes include the following:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Contact us for more help
Connect with Answer Desk for expert help.