For two sides to exchange replication data a site link must connect them a site link is a logical path
that the knowledge consistency checker and I S T G use to establish replication between sites.
When you create additional sites you must select at least one site link that will connect the new site
to an existing site unless a site link is in place.
The knowledge consistency checker cannot make connections between computers at different sites nor can
replication or cure between sites.
It is important to remember that a site link represents an away label path for replication.
A single site link does not control the network crowds that are used.
When you create a site link and add sites to it you tell it it is that it can replicate between any
of the sites that are associated with a sidling the IRS to g create connection objects and those objects
will determine the actual replication path.
Although their application topology that the IRS T.J. builds does replicate the ideas effectively.
It might not be efficient with your network topology to understand this concept better.
Consider the following example when you create a forest one site link object is created which is default
IP site link by default.
Each new site that you add is associated with default IP site link.
This site link and any other existing site links have a default cost of 100 and a default replication
period of 1 8 minutes.
Consider the example of an organization with three branch offices and a data center or the head quarters.
The three branch offices each connect to the data center with a dedicated link.
You create sites for each branch office namely Seattle LCA Amsterdam air mass and Beijing.
Each of the sites including headquarters is associated with the default IP site link site link object
because all four sites are on the same side link your instructing aided Is that all four sides can replicate
with each other.
And that means that Seattle might replicate changes from Amsterdam Amsterdam might replicate changes
from Beijing and Beijing might replicate changes from the headquarters region dorm replicate changes
from Seattle in several of these replication paths replication traffic on the network flows through
the headquarters on its way from one branch to another with a single site link.
You do not create a hub and spoke replication topology even though your network topology is hub and
spoke to align your network topology is a tedious replication you must create specific side links that
is you can manually create side links and reflect your intended replication topology continuum.
The precedent example you would create three site links as follows headquarter of Amsterdam includes
their headquarters and Amsterdam sites HQ Sia includes their headquarters and Seattle sites and HQ by
June includes the headquarters and Beijing sites.
After you create site links there I asked a Jew uses the topology to build an entire site replication
topology that connects each site and then create connection objects automatically to configure their
application path as a best practice.
You should configure your site topology correctly and avoid create and connection objects manually.