1
00:00:07,000 --> 00:00:10,830
Let's talk about how replication works between sides.

2
00:00:10,840 --> 00:00:18,230
The main characteristics of replication within a site are as follows the network connection within a

3
00:00:18,230 --> 00:00:27,070
site are reliable and have sufficient available bandwidth replication traffic within a site is not compressed

4
00:00:27,340 --> 00:00:34,870
because a site assumes fast highly reliable network connections not compress and replication traffic

5
00:00:35,170 --> 00:00:40,510
helps reduce the process and load on demand controllers.

6
00:00:40,570 --> 00:00:45,170
However uncompressed traffic might increase network bandwidth.

7
00:00:45,250 --> 00:00:50,330
So these are the characteristics of replication within a site.

8
00:00:50,350 --> 00:00:58,960
Now the main characteristics of replication between sites are as follows the network links between sites

9
00:00:58,960 --> 00:01:07,720
have limited available bandwidth might have a higher cost and might not be reliable replication traffic

10
00:01:07,720 --> 00:01:15,610
between sites can be designed to optimize bandwidth by compressing all the application traffic replication

11
00:01:15,610 --> 00:01:25,540
traffic is compressed to 10 percent or 15 percent of its original size before it transmits although

12
00:01:25,570 --> 00:01:34,240
compression optimizes network bandwidth it imposes an additional process and load on domain controllers

13
00:01:34,540 --> 00:01:41,890
when it compresses and decompress its replication data and other characteristics of replication between

14
00:01:41,890 --> 00:01:51,640
sites is replication between sites of cures automatically after you define configurable well use such

15
00:01:51,640 --> 00:02:01,120
as a schedule or replication interval you can schedule a replication for inexpensive or off peak hours

16
00:02:01,300 --> 00:02:09,430
by default changes replicate between sites according to a schedule that you define and not according

17
00:02:09,430 --> 00:02:18,730
to when changes secure the intervals specifies how often domain controllers check for changes during

18
00:02:18,730 --> 00:02:21,460
the time that replication cannot cure.

19
00:02:21,490 --> 00:02:30,160
Now some words about change notifications between ADL sites by design changes in Ada deal sites replicate

20
00:02:30,160 --> 00:02:37,900
between domain controllers in different sites according to a defined replication schedule and not according

21
00:02:37,900 --> 00:02:46,000
to when change is secure such as with intra site replication because of this the replication latency

22
00:02:46,000 --> 00:02:54,280
in the forest can equal the sum of greatest replication latency is along the longest replication path

23
00:02:54,610 --> 00:02:58,700
of any director a partition in some certain areas.

24
00:02:58,750 --> 00:03:03,280
This can be inefficient to avoid replication latency.

25
00:03:03,370 --> 00:03:11,050
You can configure change notifications on connections between sides by modifying the site link object

26
00:03:11,320 --> 00:03:19,840
you can enable change notification between sites for all connections that cure all or that link because

27
00:03:19,840 --> 00:03:27,550
the replication partner across the site receives notification of changes that enter a site replication

28
00:03:27,600 --> 00:03:35,650
interval is effectively ignored the originating domain controller notifies the domain controller in

29
00:03:35,650 --> 00:03:44,830
the other site that it has a change just as it does with a single site for changes such as account lock

30
00:03:44,830 --> 00:03:53,740
out or a similar security related changes immediate replication is crucial in these situations urgent

31
00:03:53,750 --> 00:04:03,190
replication is used urgent replication bypasses the notification delay and processes change notifications

32
00:04:03,310 --> 00:04:04,500
immediately.

33
00:04:04,510 --> 00:04:12,730
This only affects change notifications if you do not enable change notifications between sides replication

34
00:04:12,730 --> 00:04:17,820
steel onerous their application into a wall on the side limb.

35
00:04:18,100 --> 00:04:25,360
Please know that when a user response for a changes immediate replication is initiated to the primary

36
00:04:25,360 --> 00:04:33,730
domain controller emulator operations master list differs from urgent replication because it took years

37
00:04:33,730 --> 00:04:38,920
immediately without regard for the interim site replication interval.