1
00:00:06,940 --> 00:00:13,030
And this lesson will be talking about how replication topology is generated on the slides.

2
00:00:13,030 --> 00:00:21,220
I'll show how the replication topology works for each directory partition because leg configuration

3
00:00:21,220 --> 00:00:26,080
and schema partitions replicate throughout the forest.

4
00:00:26,080 --> 00:00:32,740
The replication topology crosses the main boundaries on the second part of the slide.

5
00:00:32,740 --> 00:00:36,640
I'll describe global catalog replication.

6
00:00:36,740 --> 00:00:41,320
Although the global catalog is not a directory partition.

7
00:00:41,320 --> 00:00:44,610
It uses the same replication process.

8
00:00:44,650 --> 00:00:54,160
You could write the entity yes you deal baseless partition management backslash connect backslash list

9
00:00:54,160 --> 00:00:59,430
command to see the global Catholic politicians on the domain controllers.

10
00:00:59,510 --> 00:01:08,370
No replication topology is the road by which replication data travels through and network to create

11
00:01:08,370 --> 00:01:10,230
a replication topology.

12
00:01:10,250 --> 00:01:18,450
Edit The US must determine which domain controllers replicate data with other domain controllers aided

13
00:01:18,450 --> 00:01:27,680
yes creates a replication topology based on the information that HDD contains each aided is partition.

14
00:01:27,820 --> 00:01:36,220
My triplicate two different domain controllers in a side so the replication topology can differ from

15
00:01:36,630 --> 00:01:46,360
4 schema configuration domain and application partitions because all domain controllers within a forest

16
00:01:46,360 --> 00:01:54,730
share a schema and configuration partitions ADT s replicate schema and configuration partitions to all

17
00:01:54,730 --> 00:02:03,250
domain controllers domain controllers in the same domain also replicate the domain partition additionally

18
00:02:03,490 --> 00:02:11,410
domain controllers that host an application partition also replicate the application partition to optimize

19
00:02:11,420 --> 00:02:19,720
replication traffic at domain controller might have several replication partners for different partitions

20
00:02:19,960 --> 00:02:26,450
in a single site the replication topology will be fault tolerant and redundant.

21
00:02:26,470 --> 00:02:33,850
This means that if the site contains more than 2 domain controllers e.g. domain controller we'll have

22
00:02:33,850 --> 00:02:39,090
at least two replication partners for each aided yes partition.

23
00:02:39,100 --> 00:02:46,270
Now some words about replication of the schema and configuration partitions schema configuration partition

24
00:02:46,600 --> 00:02:56,200
replication follows the same process as all other directories partitions however because these politicians

25
00:02:56,200 --> 00:03:05,200
are forest white rather than domain wide connection objects for these partitions might exist between

26
00:03:05,440 --> 00:03:10,640
any two domain controllers regardless of the domain controllers domain.

27
00:03:10,870 --> 00:03:18,340
Furthermore the replication topology for these partitions includes all domain controllers in the forest.

28
00:03:18,340 --> 00:03:23,250
Another point is how the global catalog affects replication.

29
00:03:23,380 --> 00:03:31,120
The configuration partition contains information about the site topology and other global data for all

30
00:03:31,120 --> 00:03:40,060
domains that are members of the forest ADT s replicates the configuration partition to all domain controllers

31
00:03:40,300 --> 00:03:49,750
through normal forest wide replication e.g. global catalog server obtains domain information by contacting

32
00:03:50,140 --> 00:03:58,660
a domain controller for that domain and obtain the bar to partial replica information.

33
00:03:58,660 --> 00:04:07,240
Each global catalogue server has full access to its own domains domain partition and therefore does

34
00:04:07,240 --> 00:04:13,380
not have to request a partial replication set of all this information.

35
00:04:13,450 --> 00:04:20,800
The configuration partition also provides domain controllers with a list of the forests global catalogue

36
00:04:20,800 --> 00:04:28,750
servers global catalogue servers registered DNS service records in the danger zone that corresponds

37
00:04:29,050 --> 00:04:31,150
to the forest through the domain.

38
00:04:31,150 --> 00:04:39,120
These are records which are registered only in the forest through DNS zone help clients and servers.

39
00:04:39,190 --> 00:04:46,570
Look kid global catalog Soros throughout the forest to provide clients logging services.