| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Inter-Site Replication == | == Inter-Site Replication == | ||
| − | AD uses the Knowledge Consistency Checker (KCC) to make decisions about replication. It generates a redundant link topology and also tries to preserve bandwidth by minimizing the frequency of replication. It does this by looking at costs assigned to site links. Inter-Site replication occurs every 180 min (3hrs) by default. You can modify the frequency and schedule to suite your needs. | + | AD uses the Knowledge Consistency Checker (KCC) to make decisions about replication. It generates a redundant link topology and also tries to preserve bandwidth by minimizing the frequency of replication. It does this by looking at costs assigned to site links. Inter-Site replication occurs every 180 min (3hrs) by default. You can modify the frequency and schedule to suite your needs. <br> |
https://technet.microsoft.com/en-us/library/cc759160(v=ws.10).aspx | https://technet.microsoft.com/en-us/library/cc759160(v=ws.10).aspx | ||
| Line 9: | Line 9: | ||
Where x = Link Speed in kbps. For example, link cost for a T1 (1.5mbps or 1536 kbps) would look like this: | Where x = Link Speed in kbps. For example, link cost for a T1 (1.5mbps or 1536 kbps) would look like this: | ||
1024/log(1536) = 321 (321.366 rounded down) | 1024/log(1536) = 321 (321.366 rounded down) | ||
| + | https://technet.microsoft.com/en-us/library/cc782827(v=ws.10).aspx | ||
== Intra-Site Replication == | == Intra-Site Replication == | ||
| − | Inter site replication works as follows, when a DC receives an update, it waits 15 sec, then sends out a "change notification" to its replication partner, if it has more than one replication partner, it waits an additional 3 sec, then sends a change notification to subsequent partners (at 3 sec intervals). When a DC received a change notification, it sends a "directory update request" to the source DC.<br> | + | Inter site replication works as follows, when a DC receives an update, it waits 15 sec, then sends out a "change notification" to its replication partner, if it has more than one replication partner, it waits an additional 3 sec, then sends a change notification to subsequent partners (at 3 sec intervals). When a DC received a change notification, it sends a "directory update request" to the source DC. <br> |
https://technet.microsoft.com/en-us/library/cc728010(v=ws.10).aspx | https://technet.microsoft.com/en-us/library/cc728010(v=ws.10).aspx | ||
Latest revision as of 19:26, 14 March 2016
Contents
Inter-Site Replication
AD uses the Knowledge Consistency Checker (KCC) to make decisions about replication. It generates a redundant link topology and also tries to preserve bandwidth by minimizing the frequency of replication. It does this by looking at costs assigned to site links. Inter-Site replication occurs every 180 min (3hrs) by default. You can modify the frequency and schedule to suite your needs.
https://technet.microsoft.com/en-us/library/cc759160(v=ws.10).aspx
Site Link Costs
Costing is an inverse weighting system. The higher the cumulative cost, the less likely the KCC will use that replication path (or inversly, the lower the cost, the more likely it is to use that path). You should assign site link costs using the following formula:
1024/log(x)
Where x = Link Speed in kbps. For example, link cost for a T1 (1.5mbps or 1536 kbps) would look like this:
1024/log(1536) = 321 (321.366 rounded down)
https://technet.microsoft.com/en-us/library/cc782827(v=ws.10).aspx
Intra-Site Replication
Inter site replication works as follows, when a DC receives an update, it waits 15 sec, then sends out a "change notification" to its replication partner, if it has more than one replication partner, it waits an additional 3 sec, then sends a change notification to subsequent partners (at 3 sec intervals). When a DC received a change notification, it sends a "directory update request" to the source DC.
https://technet.microsoft.com/en-us/library/cc728010(v=ws.10).aspx
Force (near) Instant Replication
- Open AD Sites and Services
- Select a IP Site Link (Under Inter-Site Transports)
- Right Click -> Properties -> Attribute Editor
- Change 'options' attribute to 1 (USE_NOTIFY)
This will cause replication across this site link to happen almost immediately (Like when DC's are in the same site, approximately 15 sec). Essentially when a DC receives a change, it broadcasts a change notification to the other DC, which then replicates the changes as soon as the notification is received.
Only for fast / low latency site links!
References
http://www.mdmarra.com/2013/07/making-active-directory-replication.html