1
00:00:06,430 --> 00:00:14,410
I'd like to highlight that most organizations that have managed a tedious change controlled process

2
00:00:14,710 --> 00:00:19,630
do not experience the application conflicts in most organizations.

3
00:00:19,630 --> 00:00:27,850
Only one group is likely to make changes to the same objects in a tedious and that group should have

4
00:00:27,850 --> 00:00:33,360
a communication process that ensures that conflicts do not happen.

5
00:00:33,370 --> 00:00:39,530
Now let's review the information about how aid ideas resolves replication conflicts.

6
00:00:39,670 --> 00:00:48,610
When it comes about attribute numbers timestamps and several global unique identifiers these situations

7
00:00:48,910 --> 00:00:52,210
can all this result in conflict resolution.

8
00:00:52,210 --> 00:00:59,990
Now because ADF supports a multiple master replication modal replication conflicts might a cure.

9
00:01:00,070 --> 00:01:08,830
Typically three types of replication conflicts might a cure in aid it is the first one is when simultaneously

10
00:01:08,870 --> 00:01:15,580
modifying the same attribute value of the same object on two domain controllers.

11
00:01:15,580 --> 00:01:22,600
The second situation is when adding or modifying the same object on one domain controller at the same

12
00:01:22,600 --> 00:01:31,120
time let the container object for the object is deleted on another domain controller and the third situation

13
00:01:31,120 --> 00:01:38,800
is when adding objects with the same relative distinguish name into the same container on different

14
00:01:38,800 --> 00:01:43,950
domain controllers simultaneously to help minimize conflicts.

15
00:01:44,020 --> 00:01:52,630
All domain controllers in the forest record and replicate object changes and the attribute or well your

16
00:01:52,630 --> 00:01:55,960
level rather than at the object level.

17
00:01:55,960 --> 00:02:05,200
Therefore changes to two different object attributes such as user is password and postal code do not

18
00:02:05,200 --> 00:02:07,150
cause a conflict.

19
00:02:07,150 --> 00:02:11,250
Even if you change them at the same time from different locations.

20
00:02:11,320 --> 00:02:20,890
When an organization update is applied to a domain controller a stamp is created that travels with the

21
00:02:20,890 --> 00:02:25,150
update as it replicates to other domain controllers.

22
00:02:25,150 --> 00:02:28,790
This term contains the following component.

23
00:02:28,840 --> 00:02:38,230
It contains version number timestamp and server globally unique identifier the version number of starts

24
00:02:38,230 --> 00:02:47,140
at 1 for each object attribute and increases by one for each update when performing an originate and

25
00:02:47,140 --> 00:02:55,360
update their version of the updated attribute is one number higher than the version of the attribute

26
00:02:55,450 --> 00:02:57,700
that is being overwritten.

27
00:02:57,730 --> 00:03:06,100
As for timestamp the timestamp is the updates originating time and date in the year of Universal Time

28
00:03:06,100 --> 00:03:11,950
zone according to the system clock of the Domain Controller where the change a cure.

29
00:03:12,160 --> 00:03:20,590
And lastly server global a unique identifier or greed the server or grid identifies the domain controller

30
00:03:20,620 --> 00:03:24,350
that performed the originate originating update.

31
00:03:24,350 --> 00:03:32,860
Now let's review common replication conflicts and how it is resolved these issues the conflict could

32
00:03:32,860 --> 00:03:35,140
a cure with attribute value.

33
00:03:35,230 --> 00:03:43,570
Even the version number Well it is the same but they attribute well you defers it is evaluate the timestamp

34
00:03:43,900 --> 00:03:51,820
the update operation that has the higher or stamp well you replaces the attribute value of the Update

35
00:03:51,910 --> 00:03:54,930
operation with a lower stamp.

36
00:03:54,940 --> 00:04:02,980
Well you edit is update certain mall to well you attribute such as a well you in a groups member of

37
00:04:03,100 --> 00:04:10,930
attribute and process has them as separate replicable events and other type of conflict that could a

38
00:04:11,100 --> 00:04:20,030
curious add in or move in under a deleted container object or the deletion of a container object it

39
00:04:20,080 --> 00:04:29,710
is resolved sees such issue as follows After resolution a cure set all the replicas aided it is deletes

40
00:04:29,800 --> 00:04:37,680
the container object and the Leaf object is made a child of the Lost and Found container.

41
00:04:37,690 --> 00:04:41,160
This resolution does not involve stamps.

42
00:04:41,210 --> 00:04:48,670
Another issue could a cure with add an object with the same relative distinguished name the object with

43
00:04:48,670 --> 00:04:56,320
the later stamp keeps the relative distinguished name 80 days assigns the symbol an object a unique

44
00:04:56,320 --> 00:05:05,420
name the name assignment is the relative distinguished name plus CnF plus a reserved character which

45
00:05:05,420 --> 00:05:14,490
is an asterisk plus the objects grid this name assignment ensures that the generated name does not conflict

46
00:05:14,790 --> 00:05:16,590
with any other objects.

47
00:05:16,590 --> 00:05:17,010
Name.