After you create site links and the Ayers degenerates connection objects to replicate partitions between
domain controllers that share a site link your work might be complete in many environments particularly
those with straightforward network apologies.
Cycling should be sufficient to manage inter site replication.
However in more complex networks you should configure additional components and replication properties
by default all site links are breached.
For example if the Amsterdam and headquarter sites are linked and if the headquarter or sound CO2 sites
are linked then Amsterdam and Seattle are linked with a combined cost.
Theoretically this means that the T G could create a connection object directly between a domain controller
in Seattle and a domain controller in Amsterdam.
If a domain controller were not available for replication at the headquarters.
This secures by working around the hub and spoke network topology.
You can disable automatic Seidlin region by opening the properties of the IP transport in the interest
side transport container and then clearing the breach all site links checkbox.
Now some words about site link bridges a startling breach connects two or more site links in a way that
creates a transitive link.
Cycling bridges are necessary only when you are clear in the bridge.
All sites links check box for the transport protocol.
Remember that automatic cycling region is enabled by default which means that cycling bridges are not
required.
However you can keep automatic cycling region enabled for the majority of sites but also configure a
cycling breach within in between costs.
For example suppose you have many sites but branches A and B are both directly connected to the corporate
headquarters with a default cost of 100.
The corporate headquarters has a backup data data center HQ does AJ which is also connected with a cost
of one hundred between the corporate headquarters and to the side A and side B locations in the event
that not all domain controller Sara Whalen Bell and HQ does a J.
You want to ensure that site a can go to Side B.
This enables you to keep site linked by region on but to configure a site link bridge with a cost of
one hundred and fifty for a side and side B.
This is greater than the cost of one hundred for either side to HQ dash a J.
But less than the cost without the cycling breach that cost would be two hundred to one hundred from
side day to HQ this -- AJ.
Plus the cost of one hundred to HQ dash a share to Side B.
This makes the cycling breach cost of one hundred and fifty and T in between cost.
The figure on the slide illustrates how you can use a cycling breach in a forest in which automatic
cycling region is disabled by creating the cycling breach.
A mass dash HQ dash CAA which includes the HQ dash a mass and HQ dash S.A. side links those two sides.
Links become transitive or breached.
Therefore application connection can be made between a domain controller in Amsterdam and a domain controller
in Seattle.