The intro site topology generator or I S T G create the replication topology between sides.
The T G uses the knowledge consistency checker but also adds an additional level of complexity when
managing multiple sides.
The IIS G is an active directory a process that defines the replication between sides on a network aided
is automatically designates a single domain controller in each side to act as the I S T G because this
section euros automatically you do not have to perform any actions to determine their replication topology
and bridgehead server rows.
So when you configure multiple sites there knowledge consistency checker on one domain controller in
each side is designated other sites.
I S T G.
There is only one i s to Jeepers side.
Regardless of how many domains or all the directory partitions The site includes I the Jews are responsible
for calculating the site's ideal replication topology a gross site links.
When you add a new site to the forest each sites IIS to g determines which director politicians are
represented or are present in the new site.
The IIS to G then calculates how many new connection objects are necessary to replicate the new sites
required information in some networks.
You might want to specify that only certain domain controllers are responsible for inter site replication.
You can do this by specifying breach had servers breach hurt servers are responsible for all the replication
into and out of the site I to create the required connection agreement and its director and this information
and then replicate it to the bridgehead server the bridgehead server then creates a replication connection
with a bridgehead server in the remote site and replication begins.
If a replication partner becomes unavailable the IIS to g select another domain controller automatically
if possible.
If breach had breach breach had servers were assigned manually and if they become in no way liable I
asked 2G will not automatically select other servers so please consider this information when designing
your sites.
As I have mentioned the IIS to g select breach had servers automatically and create the entire site
replication topology to ensure the changes replicate effectively between bridgehead servers that share
a sideline bridgehead servers are selected for partition so it is possible that one domain controller
on a site might be the breach at Sora for the schema while another is for the configuration.
However you usually will find that one domain controller is the bridgehead server for all partitions
in a site unless there are domain controllers from other domains or application directory partitions.
In this scenario breach head servers will be chosen for those partitions designated bridgehead servers
are also useful when you have firewalls between sites that only allow replication between specific domain
controllers.