1
00:00:07,000 --> 00:00:15,830
The intro site topology generator or I S T G create the replication topology between sides.

2
00:00:15,860 --> 00:00:24,520
The T G uses the knowledge consistency checker but also adds an additional level of complexity when

3
00:00:24,520 --> 00:00:26,420
managing multiple sides.

4
00:00:26,440 --> 00:00:35,650
The IIS G is an active directory a process that defines the replication between sides on a network aided

5
00:00:35,890 --> 00:00:45,830
is automatically designates a single domain controller in each side to act as the I S T G because this

6
00:00:45,830 --> 00:00:53,830
section euros automatically you do not have to perform any actions to determine their replication topology

7
00:00:54,190 --> 00:00:56,730
and bridgehead server rows.

8
00:00:56,740 --> 00:01:03,940
So when you configure multiple sites there knowledge consistency checker on one domain controller in

9
00:01:03,940 --> 00:01:07,570
each side is designated other sites.

10
00:01:07,570 --> 00:01:09,190
I S T G.

11
00:01:09,250 --> 00:01:12,190
There is only one i s to Jeepers side.

12
00:01:12,490 --> 00:01:21,040
Regardless of how many domains or all the directory partitions The site includes I the Jews are responsible

13
00:01:21,280 --> 00:01:28,080
for calculating the site's ideal replication topology a gross site links.

14
00:01:28,210 --> 00:01:36,070
When you add a new site to the forest each sites IIS to g determines which director politicians are

15
00:01:36,070 --> 00:01:41,100
represented or are present in the new site.

16
00:01:41,110 --> 00:01:49,300
The IIS to G then calculates how many new connection objects are necessary to replicate the new sites

17
00:01:49,310 --> 00:01:52,360
required information in some networks.

18
00:01:52,360 --> 00:02:00,960
You might want to specify that only certain domain controllers are responsible for inter site replication.

19
00:02:00,970 --> 00:02:09,340
You can do this by specifying breach had servers breach hurt servers are responsible for all the replication

20
00:02:09,430 --> 00:02:19,420
into and out of the site I to create the required connection agreement and its director and this information

21
00:02:19,420 --> 00:02:26,950
and then replicate it to the bridgehead server the bridgehead server then creates a replication connection

22
00:02:27,250 --> 00:02:33,360
with a bridgehead server in the remote site and replication begins.

23
00:02:33,400 --> 00:02:42,130
If a replication partner becomes unavailable the IIS to g select another domain controller automatically

24
00:02:42,460 --> 00:02:43,310
if possible.

25
00:02:43,600 --> 00:02:51,100
If breach had breach breach had servers were assigned manually and if they become in no way liable I

26
00:02:51,100 --> 00:03:00,030
asked 2G will not automatically select other servers so please consider this information when designing

27
00:03:00,040 --> 00:03:01,090
your sites.

28
00:03:01,180 --> 00:03:09,190
As I have mentioned the IIS to g select breach had servers automatically and create the entire site

29
00:03:09,190 --> 00:03:17,500
replication topology to ensure the changes replicate effectively between bridgehead servers that share

30
00:03:17,500 --> 00:03:25,270
a sideline bridgehead servers are selected for partition so it is possible that one domain controller

31
00:03:25,270 --> 00:03:33,180
on a site might be the breach at Sora for the schema while another is for the configuration.

32
00:03:33,220 --> 00:03:41,020
However you usually will find that one domain controller is the bridgehead server for all partitions

33
00:03:41,080 --> 00:03:48,820
in a site unless there are domain controllers from other domains or application directory partitions.

34
00:03:48,820 --> 00:03:56,920
In this scenario breach head servers will be chosen for those partitions designated bridgehead servers

35
00:03:57,220 --> 00:04:05,950
are also useful when you have firewalls between sites that only allow replication between specific domain

36
00:04:05,950 --> 00:04:06,910
controllers.