1 00:00:06,410 --> 00:00:12,060 And this lesson will be talking about characteristics of ADT as her application. 2 00:00:12,130 --> 00:00:14,960 And here it's brief overview. 3 00:00:15,040 --> 00:00:23,040 We'll take a look at multiple master replication Pooler application store and forward to application 4 00:00:23,380 --> 00:00:31,570 then will review data store partition and attribute level replication and some words about collision 5 00:00:31,570 --> 00:00:33,650 detection and management. 6 00:00:33,670 --> 00:00:41,500 Now it's important that you understand that you can make changes from any domain controller in the domain 7 00:00:41,830 --> 00:00:51,060 except for read only domain controllers and that those changes can replicate to all other domain controllers. 8 00:00:51,070 --> 00:00:57,970 Also it's important that you could compare this with a single master replication model in which you 9 00:00:57,970 --> 00:01:06,840 can make changes on one domain controller only think of benefits and disadvantages result from using 10 00:01:06,850 --> 00:01:10,060 a multiple master replication model. 11 00:01:10,060 --> 00:01:17,890 You should know that this model results in a more complicated replication process than the single master 12 00:01:17,890 --> 00:01:23,200 model but it provides more redundancy and scalability. 13 00:01:23,380 --> 00:01:31,840 An effective edit is replication design ensures that each partition on a domain controller is consistent 14 00:01:32,140 --> 00:01:41,320 with the replicas of that partition that are hosted on other domain controllers typically not all domain 15 00:01:41,320 --> 00:01:49,970 controllers have exactly the same information in their replicas at any particular moment because change 16 00:01:50,000 --> 00:01:59,200 is secure to the partition constantly however aided yes replication ensures that all changes to a partition 17 00:01:59,500 --> 00:02:09,760 transfer to all the replicas of the partition aided is replication balances accuracy or integrity and 18 00:02:09,760 --> 00:02:14,770 consistency or convergence with performance. 19 00:02:14,770 --> 00:02:18,760 This keeps replication traffic to a reasonable level. 20 00:02:18,770 --> 00:02:26,290 Now let's see the key characteristics of aided yes replication multiple master replication and a domain 21 00:02:26,290 --> 00:02:31,710 controller accept and rotate seek and initiate and commit a change to. 22 00:02:31,730 --> 00:02:39,190 Edit Is this poor whites fault tolerance and eliminates dependency on a single domain controller to 23 00:02:39,190 --> 00:02:43,000 maintain the directory store separations. 24 00:02:43,040 --> 00:02:51,460 Another characteristic is Boola replication a domain controller requests or pools changes from other 25 00:02:51,460 --> 00:02:59,260 domain controllers a domain controller cannot defy its replication partners that it has changes to the 26 00:02:59,260 --> 00:03:05,670 director or asks its partners to see if they have changes to the directory. 27 00:03:05,950 --> 00:03:13,030 However ultimately the target domain controller requests and pulls the changes itself. 28 00:03:13,030 --> 00:03:20,350 Next stop is store and forward replication a domain controller can bool changes from one replication 29 00:03:20,350 --> 00:03:26,650 partner and then make those changes available to another replication partner. 30 00:03:26,650 --> 00:03:35,030 For example domain controller B can pull changes initiated by domain controller a then domain controller 31 00:03:35,050 --> 00:03:39,280 C can pull the changes from domain controller B. 32 00:03:39,280 --> 00:03:46,450 This helps balance the application load for domains that contain several domain controllers. 33 00:03:46,510 --> 00:03:54,490 Then we have data stored partitioning our domains domain controllers host the domain name in context 34 00:03:54,760 --> 00:04:02,530 for their domains which helps minimize replication particulary in multiple domain forests. 35 00:04:02,590 --> 00:04:09,700 The Domain Controller is also host corpus of schema and configuration partitions which are replicated 36 00:04:09,700 --> 00:04:11,170 forest wide. 37 00:04:11,170 --> 00:04:19,630 However changes in configuration and schema partitions are much less frequent than in the domain partition 38 00:04:19,930 --> 00:04:20,860 by default. 39 00:04:20,860 --> 00:04:29,320 Other data include an application directory partitions and the partial attributes set which is the global 40 00:04:29,320 --> 00:04:35,020 catalogue do not replicate to every domain controller in the forest. 41 00:04:35,050 --> 00:04:42,370 You can enable replication to be universal by configuring all the domain controllers in a forest as 42 00:04:42,370 --> 00:04:44,380 global catalog servers. 43 00:04:44,380 --> 00:04:52,920 Next up is automatic generation of an efficient and robust replication topology by default aided is 44 00:04:52,930 --> 00:05:01,600 configure as an effective multi directional replication topology so that the loss of one domain controller 45 00:05:01,870 --> 00:05:11,140 does not embed or corrupt replication aid is automatically updates this topology as domain controller 46 00:05:11,140 --> 00:05:15,310 of SA read it removed or moved between sites. 47 00:05:15,310 --> 00:05:18,590 Next up is attribute level replication. 48 00:05:18,700 --> 00:05:27,490 When an objects attribute changes only that attribute and minimal method data describe and that attribute 49 00:05:27,850 --> 00:05:36,640 replicates the entire object does not replicate except on this initial creation for multi well you'd 50 00:05:36,730 --> 00:05:45,070 attribute such as account names in the member of attribute of a group account only changes to actual 51 00:05:45,070 --> 00:05:53,650 names replicate and not the entire list of names and other key characteristics of active directory application 52 00:05:53,650 --> 00:05:58,300 as distinct control of interest site replication. 53 00:05:58,300 --> 00:06:01,570 You can control a replication between sites. 54 00:06:01,570 --> 00:06:05,350 Next stop is collision detection and management. 55 00:06:05,350 --> 00:06:12,220 It's possible to modify an attribute on two different domain controllers within a single replication 56 00:06:12,220 --> 00:06:15,900 window thereby creating a conflict. 57 00:06:15,910 --> 00:06:18,220 However this is rare. 58 00:06:18,220 --> 00:06:27,760 If this secures you must reconcile the two changes aided yes US has the resolution algorithms that satisfy 59 00:06:27,760 --> 00:06:30,040 most all scenarios.