1 00:00:07,000 --> 00:00:15,130 After you create site links and the Ayers degenerates connection objects to replicate partitions between 2 00:00:15,130 --> 00:00:23,320 domain controllers that share a site link your work might be complete in many environments particularly 3 00:00:23,590 --> 00:00:27,450 those with straightforward network apologies. 4 00:00:27,490 --> 00:00:32,380 Cycling should be sufficient to manage inter site replication. 5 00:00:32,440 --> 00:00:40,690 However in more complex networks you should configure additional components and replication properties 6 00:00:40,900 --> 00:00:44,260 by default all site links are breached. 7 00:00:44,260 --> 00:00:52,840 For example if the Amsterdam and headquarter sites are linked and if the headquarter or sound CO2 sites 8 00:00:52,900 --> 00:00:59,310 are linked then Amsterdam and Seattle are linked with a combined cost. 9 00:00:59,410 --> 00:01:08,350 Theoretically this means that the T G could create a connection object directly between a domain controller 10 00:01:08,350 --> 00:01:12,960 in Seattle and a domain controller in Amsterdam. 11 00:01:13,000 --> 00:01:19,150 If a domain controller were not available for replication at the headquarters. 12 00:01:19,150 --> 00:01:25,330 This secures by working around the hub and spoke network topology. 13 00:01:25,390 --> 00:01:34,650 You can disable automatic Seidlin region by opening the properties of the IP transport in the interest 14 00:01:34,650 --> 00:01:43,070 side transport container and then clearing the breach all site links checkbox. 15 00:01:43,090 --> 00:01:51,520 Now some words about site link bridges a startling breach connects two or more site links in a way that 16 00:01:51,790 --> 00:01:54,230 creates a transitive link. 17 00:01:54,280 --> 00:02:00,830 Cycling bridges are necessary only when you are clear in the bridge. 18 00:02:00,880 --> 00:02:05,110 All sites links check box for the transport protocol. 19 00:02:05,110 --> 00:02:13,540 Remember that automatic cycling region is enabled by default which means that cycling bridges are not 20 00:02:13,540 --> 00:02:14,350 required. 21 00:02:14,680 --> 00:02:23,050 However you can keep automatic cycling region enabled for the majority of sites but also configure a 22 00:02:23,050 --> 00:02:27,270 cycling breach within in between costs. 23 00:02:27,280 --> 00:02:36,820 For example suppose you have many sites but branches A and B are both directly connected to the corporate 24 00:02:36,820 --> 00:02:41,320 headquarters with a default cost of 100. 25 00:02:41,350 --> 00:02:50,530 The corporate headquarters has a backup data data center HQ does AJ which is also connected with a cost 26 00:02:50,530 --> 00:02:59,470 of one hundred between the corporate headquarters and to the side A and side B locations in the event 27 00:02:59,830 --> 00:03:05,640 that not all domain controller Sara Whalen Bell and HQ does a J. 28 00:03:05,710 --> 00:03:10,750 You want to ensure that site a can go to Side B. 29 00:03:10,750 --> 00:03:18,730 This enables you to keep site linked by region on but to configure a site link bridge with a cost of 30 00:03:19,060 --> 00:03:23,180 one hundred and fifty for a side and side B. 31 00:03:23,290 --> 00:03:31,390 This is greater than the cost of one hundred for either side to HQ dash a J. 32 00:03:31,510 --> 00:03:39,820 But less than the cost without the cycling breach that cost would be two hundred to one hundred from 33 00:03:39,820 --> 00:03:43,070 side day to HQ this -- AJ. 34 00:03:43,180 --> 00:03:48,670 Plus the cost of one hundred to HQ dash a share to Side B. 35 00:03:48,670 --> 00:03:55,480 This makes the cycling breach cost of one hundred and fifty and T in between cost. 36 00:03:55,480 --> 00:04:02,650 The figure on the slide illustrates how you can use a cycling breach in a forest in which automatic 37 00:04:02,650 --> 00:04:07,550 cycling region is disabled by creating the cycling breach. 38 00:04:07,720 --> 00:04:19,950 A mass dash HQ dash CAA which includes the HQ dash a mass and HQ dash S.A. side links those two sides. 39 00:04:20,110 --> 00:04:23,920 Links become transitive or breached. 40 00:04:24,070 --> 00:04:32,140 Therefore application connection can be made between a domain controller in Amsterdam and a domain controller 41 00:04:32,140 --> 00:04:33,060 in Seattle.