1 00:00:00,470 --> 00:00:02,240 In this section, we're going to discuss 2 00:00:02,240 --> 00:00:04,350 the importance of planning for the worst. 3 00:00:04,350 --> 00:00:06,210 We're going to do this by conducting redundancy 4 00:00:06,210 --> 00:00:08,050 and disaster recovery planning. 5 00:00:08,050 --> 00:00:10,180 But what exactly is redundancy? 6 00:00:10,180 --> 00:00:12,280 Well, redundancy is a term that usually refers 7 00:00:12,280 --> 00:00:14,530 to something that's extra or unnecessary. 8 00:00:14,530 --> 00:00:16,610 For example, if I'm sitting at a restaurant 9 00:00:16,610 --> 00:00:18,670 and my waitress brings me over two glasses of water 10 00:00:18,670 --> 00:00:21,760 instead of one, well, one of those glasses is redundant 11 00:00:21,760 --> 00:00:24,550 because I can only drink from one glass at a time. 12 00:00:24,550 --> 00:00:27,480 Now, in the IT world though, we love redundancy. 13 00:00:27,480 --> 00:00:29,610 Redundancy is a great thing. 14 00:00:29,610 --> 00:00:30,930 Let's say I have one server 15 00:00:30,930 --> 00:00:32,900 that I need to run a domain controller. 16 00:00:32,900 --> 00:00:34,860 Well, it's probably a better idea for me to have 17 00:00:34,860 --> 00:00:36,620 two servers to run that domain controller. 18 00:00:36,620 --> 00:00:38,990 One is a primary and one is a backup, 19 00:00:38,990 --> 00:00:41,040 in case that primary fails. 20 00:00:41,040 --> 00:00:43,480 Also if I have a connection to the Internet, 21 00:00:43,480 --> 00:00:44,400 wouldn't it be better if I had 22 00:00:44,400 --> 00:00:46,615 two connections to the Internet? 23 00:00:46,615 --> 00:00:47,448 Your cell phone knows this is true 24 00:00:47,448 --> 00:00:49,210 and that's why you have two different ways to connect. 25 00:00:49,210 --> 00:00:50,750 You have a cellular modem in there 26 00:00:50,750 --> 00:00:52,270 that connects to the cellular network, 27 00:00:52,270 --> 00:00:53,960 and you have wireless access, 28 00:00:53,960 --> 00:00:55,640 where you can connect to your Wi-Fi. 29 00:00:55,640 --> 00:00:57,890 That's the same idea, you have two different methods, 30 00:00:57,890 --> 00:01:00,990 which give you the same features and they are redundant. 31 00:01:00,990 --> 00:01:03,330 So I think you understand the concept of redundancy 32 00:01:03,330 --> 00:01:06,060 and why it may be a good thing inside of IT. 33 00:01:06,060 --> 00:01:07,810 So, when we do redundancy planning, 34 00:01:07,810 --> 00:01:09,710 we're looking at our networks, our servers, 35 00:01:09,710 --> 00:01:12,510 and our systems to make sure that they're fault-tolerant, 36 00:01:12,510 --> 00:01:13,410 and we want to make sure that they can 37 00:01:13,410 --> 00:01:16,030 continue to provide us services 24 hours a day, 38 00:01:16,030 --> 00:01:19,400 seven days a week, 365 days a year. 39 00:01:19,400 --> 00:01:22,260 To do this, we have to identify any single points of failure 40 00:01:22,260 --> 00:01:24,250 inside of our networks and our systems, 41 00:01:24,250 --> 00:01:25,830 and those single points of failure 42 00:01:25,830 --> 00:01:28,700 are those individual elements, objects, or parts 43 00:01:28,700 --> 00:01:30,720 that could cause a system to fail 44 00:01:30,720 --> 00:01:32,320 and if one of those components fails, 45 00:01:32,320 --> 00:01:34,830 it'll take down the entire system with it. 46 00:01:34,830 --> 00:01:37,580 Now, if we can identify those single points of failure, 47 00:01:37,580 --> 00:01:39,820 then we can design backup and redundant systems 48 00:01:39,820 --> 00:01:42,560 around them to eliminate them or mitigate them. 49 00:01:42,560 --> 00:01:43,810 And this way, we're going to be able 50 00:01:43,810 --> 00:01:46,750 to increase our availability and increase our uptime. 51 00:01:46,750 --> 00:01:48,670 The reality is, though, that when we plan 52 00:01:48,670 --> 00:01:52,070 for everything to go right, sometimes things still go wrong, 53 00:01:52,070 --> 00:01:54,710 and this is where disaster recovery comes into play. 54 00:01:54,710 --> 00:01:56,670 We're going to do disaster recovery to figure out 55 00:01:56,670 --> 00:01:58,070 how we're going to do our backup systems 56 00:01:58,070 --> 00:01:59,570 and how they're designed, and how we're going 57 00:01:59,570 --> 00:02:01,070 to conduct disaster recovery planning 58 00:02:01,070 --> 00:02:02,650 in case our building catches on fire, 59 00:02:02,650 --> 00:02:04,320 or we have floods, or earthquakes, 60 00:02:04,320 --> 00:02:06,800 or any of a myriad of other things that can happen 61 00:02:06,800 --> 00:02:09,750 and how we're going to overcome them and get back to business.