Let's talk about how replication works between sides.
The main characteristics of replication within a site are as follows the network connection within a
site are reliable and have sufficient available bandwidth replication traffic within a site is not compressed
because a site assumes fast highly reliable network connections not compress and replication traffic
helps reduce the process and load on demand controllers.
However uncompressed traffic might increase network bandwidth.
So these are the characteristics of replication within a site.
Now the main characteristics of replication between sites are as follows the network links between sites
have limited available bandwidth might have a higher cost and might not be reliable replication traffic
between sites can be designed to optimize bandwidth by compressing all the application traffic replication
traffic is compressed to 10 percent or 15 percent of its original size before it transmits although
compression optimizes network bandwidth it imposes an additional process and load on domain controllers
when it compresses and decompress its replication data and other characteristics of replication between
sites is replication between sites of cures automatically after you define configurable well use such
as a schedule or replication interval you can schedule a replication for inexpensive or off peak hours
by default changes replicate between sites according to a schedule that you define and not according
to when changes secure the intervals specifies how often domain controllers check for changes during
the time that replication cannot cure.
Now some words about change notifications between ADL sites by design changes in Ada deal sites replicate
between domain controllers in different sites according to a defined replication schedule and not according
to when change is secure such as with intra site replication because of this the replication latency
in the forest can equal the sum of greatest replication latency is along the longest replication path
of any director a partition in some certain areas.
This can be inefficient to avoid replication latency.
You can configure change notifications on connections between sides by modifying the site link object
you can enable change notification between sites for all connections that cure all or that link because
the replication partner across the site receives notification of changes that enter a site replication
interval is effectively ignored the originating domain controller notifies the domain controller in
the other site that it has a change just as it does with a single site for changes such as account lock
out or a similar security related changes immediate replication is crucial in these situations urgent
replication is used urgent replication bypasses the notification delay and processes change notifications
immediately.
This only affects change notifications if you do not enable change notifications between sides replication
steel onerous their application into a wall on the side limb.
Please know that when a user response for a changes immediate replication is initiated to the primary
domain controller emulator operations master list differs from urgent replication because it took years
immediately without regard for the interim site replication interval.