When a domain controller writes a change to its local copy of the Active Directory, a timer is started that determines when the domain controller's replication partners should be notified of the change. By default, this interval is 15 seconds in Windows Server and later versions. When this interval elapses, the domain controller initiates a notification to each intra-site replication partner that it has changes that need to be propagated.
Another configurable parameter determines the number of seconds to pause between notification. This parameter prevents simultaneous replies by the replication partners. By default, this interval is 3 seconds in Windows Server and later versions, when the forest functional level is Windows Server or a higher functional level. Click the Cancel button for the Properties window. If the replication interval and replication available properties do not allow daily replication, then this is a finding.
Timely replication makes certain that directory service data is consistent across all servers that support the same scope of data for their clients. Load commands, advanced database properties, cluster statistics, and the Server Health Monitor. You can schedule server-to-server replication to happen at specific times, or you can specify a time range with a repeat interval. By scheduling replication for a time range, you ensure that the servers exchange information several times a day.
After the server makes a successful connection, it waits the amount of time specified in the Repeat interval of field on the Connection document before calling the other server again. Be sure to consider time zones when you schedule replication between servers in different countries.
You want to replicate the documents created during each time zone's peak business hours and schedule replication for an off-peak time. The default replication time setting is 8 AM to 10 PM, with a repeat interval of minutes. You can use staggered schedules on hub-and-spoke topology.
You can create a simple round-robin schedule for a hub server and its spokes, repeating as often as is practical. This process spreads all data within a hub's sphere of influence quickly. Use a specific time when you schedule replication of low priority databases, when daily updates of databases are sufficient, or when you're certain that attempts by the server to connect are successful after just a few retries -- for example, on different networks at the same site.
You might want to replicate low-priority databases at night when the rates are less expensive or there is less load on the system. The server calls and attempts to connect at the exact time you specified. If unsuccessful, the server tries to connect for an hour. Whether or not the connection succeeds, the next call does not occur until 8 AM the next morning.
Use a list of times to schedule replication for medium and low priority databases and for when a few daily updates of databases are sufficient or when you're certain that connection attempts will be successful after just a few retries -- for example, for a connection on different networks at the same site. The server calls at the first time specified, 8 AM.
If unsuccessful, the server retries for up to an hour, until 9 AM. Whether or not the call succeeds, the next call occurs at the next scheduled time, 1 PM. If unsuccessful, the server retries for up to an hour, until 2 PM. This process continues for each specific time you specify. If the first call is unsuccessful, the server retries periodically until it successfully establishes a connection and replicates. If the server cannot connect, it keeps trying until the end of the time range.
If the server successfully replicates, it calls again at the specified repeat interval after the previous call ended. Use a time range without a repeat interval for medium and low-priority databases. Also use a time range without a repeat interval when daily updates of a database are sufficient or when you know that a long retry period is necessary -- for example, if you have a slow connection and you know it will take several attempts to make the connection.
The server attempts the first call at the start of the time range. If unsuccessful, the server tries again and again. For example, if replication occurs between New York and Washington, D.
For example, if the maximum latency between Seattle and its satellite site in Los Angeles is one day, the maximum replication latency for this set of links Washington, D. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy. Skip to main content. This browser is no longer supported.
0コメント