1 00:00:00,360 --> 00:00:04,800 This is the solution video for the SCD Back and Restore Lab. 2 00:00:07,310 --> 00:00:12,890 So for the first question, we have to find out the number of deployments that exist in this cluster. 3 00:00:15,880 --> 00:00:21,010 So let's try and still get deployment's, and as you can see, we have two deployments, one called 4 00:00:21,010 --> 00:00:22,310 blue and the other red. 5 00:00:22,990 --> 00:00:24,310 So the answer is to. 6 00:00:26,070 --> 00:00:31,730 What is the vision of a city which is running on the closer to the city part of the process? 7 00:00:31,740 --> 00:00:33,540 So let's inspect the city board. 8 00:00:34,020 --> 00:00:40,050 So if you remember from the lecture, it city is deploying as a port and it should be in the coop system 9 00:00:40,060 --> 00:00:40,670 namespace. 10 00:00:41,280 --> 00:00:44,970 And that's because this cluster has been deployed using Badme. 11 00:01:02,160 --> 00:01:07,380 And if you look at the image and you can see that it is running at three point four point nine. 12 00:01:09,660 --> 00:01:10,680 So let's look that. 13 00:01:13,540 --> 00:01:18,290 At what address do you raise the concern from your master or control plane load? 14 00:01:18,850 --> 00:01:25,870 So in this case, the CD is running as a part on the control plane known and to reach it from the same 15 00:01:25,870 --> 00:01:30,250 note, we can use the local horse and he put two three seven nine. 16 00:01:31,680 --> 00:01:37,860 So if you look at the list like you or else command, which is run within the FTC report, you can see 17 00:01:37,890 --> 00:01:45,810 that one of the address and the port combination where it is reachable as 127 DOT 0.01, which is localhost 18 00:01:45,960 --> 00:01:47,670 and they put us two three seven nine. 19 00:01:49,520 --> 00:01:56,630 As you can see, there's another option, which is SCDP is one twenty seven zero zero one and put two 20 00:01:56,630 --> 00:02:03,800 three eight zero, and that is responsible for other nodes to join the same cluster in case of a multi 21 00:02:03,800 --> 00:02:04,690 cluster scenario. 22 00:02:08,290 --> 00:02:15,190 But in this case, we are connecting to exit from the node so we can use two three seven nine. 23 00:02:18,670 --> 00:02:21,570 Where is the NCD silver certificate file located? 24 00:02:22,060 --> 00:02:29,040 So let's go back to the same command that we ran before, which is describe it to the control plane. 25 00:02:29,680 --> 00:02:37,130 And here we can see that this old file is located under a DC cabinet is speaking I it's KDDI. 26 00:02:37,300 --> 00:02:38,550 So we're not CRT. 27 00:02:41,720 --> 00:02:44,330 Where is the CDC certificate located? 28 00:02:51,410 --> 00:02:57,050 So if you look at the option for us to see a file, you can see that it is also located in the same 29 00:02:57,050 --> 00:03:03,470 directory, which is when it is at CD and the name of the certificate of CRT. 30 00:03:10,400 --> 00:03:16,100 All right, so the massive in August are planned for a regular maintenance reboot tonight, while we 31 00:03:16,100 --> 00:03:18,000 do not anticipate anything to go wrong. 32 00:03:18,020 --> 00:03:24,320 We are required to take the necessary backups, take this snapshot of its database using the CDC data, 33 00:03:24,740 --> 00:03:26,510 and we have to save it under the static. 34 00:03:26,540 --> 00:03:27,710 We would just slash obesity. 35 00:03:27,770 --> 00:03:32,660 And the name of the snapshot should be snapshot, dash, pre dash, blue dot DB. 36 00:03:33,600 --> 00:03:39,030 All right, so let's go back to the dome now and we're just going to clear the screen and to do this, 37 00:03:39,030 --> 00:03:43,470 we'll use the actual tool which is installed in the control node. 38 00:03:47,590 --> 00:03:51,550 And we'll make sure that we are using the CDC deal with the usual three. 39 00:03:55,910 --> 00:04:00,710 So you can see the client is three and the EPA as three point four. 40 00:04:05,740 --> 00:04:08,560 And the command that they're going to use as a snapshot, see? 41 00:04:10,740 --> 00:04:16,170 But here I'm using the dash dash help to see all the options which we need to make use of while running 42 00:04:16,170 --> 00:04:23,460 this command and the global options, you can see all the options that are required to connect to the 43 00:04:23,640 --> 00:04:26,790 CD, which is running on the controlled plane as a pod. 44 00:04:29,010 --> 00:04:32,130 The first thing that we have to add is the certificate file. 45 00:04:32,160 --> 00:04:34,950 We also have to pass on the certificate and the key. 46 00:04:38,990 --> 00:04:40,060 So let's do that now. 47 00:05:11,040 --> 00:05:16,710 I'm just going to commend this command and Lagann referred to the capacity of the scrub command that 48 00:05:16,800 --> 00:05:21,990 used earlier to find out all the body parts for the certificate's. 49 00:06:08,650 --> 00:06:15,250 Now, one thing to note here is that I'm not specifying the endpoint option, and that is because we 50 00:06:15,250 --> 00:06:20,020 are running this command on the same server where it is installed. 51 00:06:30,600 --> 00:06:32,790 In this case, the snapshot has been saved. 52 00:06:38,190 --> 00:06:40,140 Let's run snapshot status. 53 00:06:44,440 --> 00:06:48,130 And for running snapshot status, we do not need the certificates. 54 00:06:53,890 --> 00:06:55,500 Let's move on to the next question. 55 00:07:01,580 --> 00:07:04,760 All right, so let's wait for the maintenance window to finish. 56 00:07:07,380 --> 00:07:12,350 So for this next question, we have to find out what exactly went wrong during the upgrade process. 57 00:07:13,380 --> 00:07:14,650 So there are a few options here. 58 00:07:14,670 --> 00:07:18,680 Deployments are not prison services and our prisons, all of the above or pods are not prison. 59 00:07:18,690 --> 00:07:22,800 So let's go back to a terminal and check the status of these objects. 60 00:07:30,140 --> 00:07:36,590 So if you remember earlier, we had two deployments and now there are none, so let's also check if 61 00:07:36,590 --> 00:07:38,390 there are any services related to this. 62 00:07:39,240 --> 00:07:41,600 But there's just the default component of service. 63 00:07:42,080 --> 00:07:43,280 There's no deployment. 64 00:07:44,260 --> 00:07:45,520 Bovis or Pod? 65 00:07:50,230 --> 00:07:57,010 Luckily, we took a backup, so let's restore back, be closer to its original state to do this, really 66 00:07:57,050 --> 00:07:59,440 run the snapshot, restore calm on. 67 00:08:01,340 --> 00:08:04,430 And let's restore it to a different directory. 68 00:08:11,830 --> 00:08:17,230 So, again, we can make use of the dash dash help option to see all the possible options that we need 69 00:08:17,230 --> 00:08:18,280 to pass in along with this. 70 00:08:18,280 --> 00:08:18,610 Come on. 71 00:08:21,460 --> 00:08:28,420 So in this case, we just have to give the family and the where we want to restore the snapshots in 72 00:08:28,420 --> 00:08:30,640 this case file name as the snapshot file. 73 00:08:32,490 --> 00:08:35,040 And we have to provide the data that ACRI. 74 00:09:08,290 --> 00:09:10,810 So let's save this to a new directory. 75 00:09:12,950 --> 00:09:13,900 Or liber. 76 00:09:15,450 --> 00:09:16,080 KDDI. 77 00:09:19,350 --> 00:09:20,100 From back up. 78 00:09:22,140 --> 00:09:28,350 Now, before I run this command, I just want to quickly show you the contents of this factory and the 79 00:09:28,350 --> 00:09:29,870 original snapshot directly. 80 00:09:36,740 --> 00:09:39,800 So this doctor does not exist at this point in time. 81 00:09:42,370 --> 00:09:46,390 And what it is where it KDDI database is currently stored. 82 00:09:49,070 --> 00:09:50,470 So let's run this command again. 83 00:09:51,880 --> 00:09:58,060 And you'll notice that are not making use of the options for passing in the U.S. certificate. 84 00:09:58,120 --> 00:10:04,000 The silver certificate and the key, and that's because the snapshot is already created in OBD and we 85 00:10:04,000 --> 00:10:07,290 do not need to connect to the silver at this point in time. 86 00:10:13,760 --> 00:10:18,180 As you can see, this new directory has been created under its code from back up. 87 00:10:18,200 --> 00:10:20,300 This is where the snapshot has been restored to. 88 00:10:21,550 --> 00:10:27,520 However, our exit closer is still configured to connect to this directory, which is the original CD. 89 00:10:27,730 --> 00:10:28,840 So you'll have to change that. 90 00:10:29,200 --> 00:10:33,550 And to do that, we'll have to update the YAML file for the support for. 91 00:10:44,230 --> 00:10:47,480 So here is the YAML file for its KDDI. 92 00:10:48,820 --> 00:10:53,950 So if you look at the configuration for this container, you'll see that the dash dash data directory 93 00:10:54,160 --> 00:10:57,320 is currently pointing toward Liberty City and this is within the container. 94 00:10:58,360 --> 00:11:03,160 And if you scroll all the way to the bottom, so I'm pressing Shivji here so that I can scroll all the 95 00:11:03,160 --> 00:11:09,370 way to the end, you'll see that this is actually a volume. 96 00:11:13,800 --> 00:11:18,730 And this also makes use of the hotspot are live at KDDI, which is from the host. 97 00:11:19,110 --> 00:11:25,230 So in order to mount the newly created and the newly restored directory, which is one CD from backup, 98 00:11:25,470 --> 00:11:31,350 we can just make a change here and overwrite this directory to a CD from backup. 99 00:11:35,030 --> 00:11:41,750 So currently, we are making use of this data from the House to mount within our container. 100 00:11:45,110 --> 00:11:51,890 To this, but so as you can see, the name data, which is from this volume here and which makes use 101 00:11:51,890 --> 00:11:57,350 of the hotspot CD from backup, is mounted under Exelis on the container. 102 00:11:58,410 --> 00:12:05,250 So this means that once we see an exit, this file, the report will be recreated as it's a static port 103 00:12:05,250 --> 00:12:10,290 and it will make use of the new iPad or sighting of the database. 104 00:12:14,930 --> 00:12:21,140 So as you can see, the old container for the CD has been destroyed and will be recreated. 105 00:12:26,080 --> 00:12:27,710 There you go and has been recreated. 106 00:12:27,730 --> 00:12:31,110 So if you just copy the Docker container. 107 00:12:35,720 --> 00:12:40,030 And see that the server is now coming up as the static bot. 108 00:12:59,290 --> 00:13:05,620 And here you can see that it is using this wall directly on the container, but remember that this is 109 00:13:05,630 --> 00:13:11,020 a hotspot mount from what it could from back up from the control plane load. 110 00:13:15,990 --> 00:13:18,000 Now, if you're on Kubasik, you'll get Pott's. 111 00:13:19,590 --> 00:13:22,470 Deployments and service. 112 00:13:26,250 --> 00:13:28,530 You'll see that all of them have been recreated. 113 00:13:31,700 --> 00:13:33,860 Thank you for joining me for the solution we do. 114 00:13:33,890 --> 00:13:35,390 I hope that you find it useful. 115 00:13:35,570 --> 00:13:36,830 I'll see you in the next one.