Partial Replication May Take a Long Time with Very Large Groups (238191)
The information in this article applies to:
- Microsoft Windows NT Server 4.0
This article was previously published under Q238191 SYMPTOMS
The following symptoms may occur on a domain with very large groups containing thousands of users that are changed frequently:
- On the primary domain controller (PDC), there is a large number (up to several events per minute) of 5711 events for each backup domain controller (BDC):
Event Id 5711 - Source: NETLOGON
Description: The partial synchronization request from the server BDC completed successfully. X changes(s) has (have) been returned to the caller.
- On the BDC, there is only one 5715 event between two replications:
Event Id 5715 - Source: NETLOGON
The partial synchronization replication of the SAM database from the
primary domain controller PDC completed successfully. X change(s) is (are) applied to the database.
- The partial replication could take a very long time.
- The amount of data that goes across the wire for a single replication to a given BDC may be very large, and even larger than the size of the SAM
on the PDC. (Use the command "NBTSTAT -S" to monitor the amount of data sent to each BDC.)
- The CPU on the PDC may remain at 100 percent usage during the replication.
RESOLUTION
You should not make too many changes to very large groups that contain thousands of users. If you do have to make large SAM modifications and have to modify the members of very large groups, you can:
- Make all the changes on the PDC.
- Force a full replication for all BDCs (issue the NLTEST/SYNC command on each BDC).
Modification Type: | Major | Last Reviewed: | 8/6/2002 |
---|
Keywords: | kbenv kberrmsg kbprb KB238191 |
---|
|