WEBVTT 1 00:00.000 --> 00:04.850 So, my intention for this video is to walk you through a proven process for 2 00:04.850 --> 00:05.020 studying 3 00:05.020 --> 00:07.920 everything down gracefully and then getting snapshots. 4 00:07.920 --> 00:10.960 So if we want to, we can return right back to the point that we left off. 5 00:10.960 --> 00:14.200 And again, the benefit of that is that if we want to try something new or new 6 00:14.200 --> 00:15.180 configuration, 7 00:15.180 --> 00:17.100 we can just configure till the cows come home. 8 00:17.100 --> 00:20.470 And then when we're done, we can revert to the snapshot and start over at the 9 00:20.470 --> 00:21.040 same initial 10 00:21.040 --> 00:22.040 place again. 11 00:22.040 --> 00:25.770 And sometimes we're attempting a new configuration or something different than 12 00:25.770 --> 00:27.000 our normal operations. 13 00:27.000 --> 00:31.190 Sometimes we may want to practice a new configuration or additional options WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:27.000 --> 00:31.190 Sometimes we may want to practice a new configuration or additional options 14 00:31.190 --> 00:32.040 many times. 15 00:32.040 --> 00:35.880 And so having a graceful shutdown and snapshot process allows that to happen. 16 00:35.880 --> 00:38.180 So here is the order of operations for what we're going to do. 17 00:38.180 --> 00:41.740 We are going to take the NSX manager, which is currently running on our 18 00:41.740 --> 00:42.520 physical host. 19 00:42.520 --> 00:45.920 And we are going to shut down the NSX manager. 20 00:45.920 --> 00:46.920 So that's the first step. 21 00:46.920 --> 00:47.920 Let's do that first. 22 00:47.920 --> 00:52.740 Let's go to our physical hosted environment, find the NSX manager, which we're 23 00:52.740 --> 00:53.320 running 24 00:53.320 --> 00:56.040 on our physical environment and do a shutdown. 25 00:56.040 --> 00:59.110 And although there's more than one way to gracefully shut that down, the way I 26 00:59.110 --> 00:59.520 prefer 27 00:59.520 --> 01:04.170 to do it is to do it via the command line, the SSH over to the NSX manager and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 27 00:59.520 --> 01:04.170 to do it is to do it via the command line, the SSH over to the NSX manager and 28 01:04.170 --> 01:04.920 actually 29 01:04.920 --> 01:07.560 just do a shutdown command after logging in. 30 01:07.560 --> 01:11.640 So here in the NSX manager, if we go to appliances, they'll show us the details 31 01:11.640 --> 01:12.440 regarding the 32 01:12.440 --> 01:14.240 IP address or addresses involved. 33 01:14.240 --> 01:20.780 So my single NSX manager, as part of my cluster is .11 and the VAP address is . 34 01:20.780 --> 01:21.760 10. 35 01:21.760 --> 01:25.950 So I could use either of those addresses to connect to the NSX manager via SSH 36 01:25.950 --> 01:26.480 and shut 37 01:26.480 --> 01:27.480 it down. 38 01:27.480 --> 01:29.800 So here are my secure CRT terminal with SSH running. 39 01:29.800 --> 01:31.640 I'm connected over to .11. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 39 01:29.800 --> 01:31.640 I'm connected over to .11. 40 01:31.640 --> 01:33.800 There's our NSX manager and logged in. 41 01:33.800 --> 01:36.000 We'll just type in shutdown press enter. 42 01:36.000 --> 01:38.400 We'll type in yes, confirm and boom. 43 01:38.400 --> 01:40.800 This guy is off to graceful shutdown land. 44 01:40.800 --> 01:43.880 So our next step is to shut down the edge nodes. 45 01:43.880 --> 01:48.720 Now those two edge nodes are both running on the nested ESXi host called ESXi 46 01:48.720 --> 01:49.120 dash 47 01:49.120 --> 01:50.120 management. 48 01:50.120 --> 01:53.920 So to use the vSphere client, we can go to that host to find those two VMs. 49 01:53.920 --> 01:57.900 And then because they're both running VMware tools, we can perform a graceful 50 01:57.900 --> 01:58.400 shutdown 51 01:58.400 --> 02:01.590 from the vSphere client for those two VMs that are running on the ESXi WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 51 01:58.400 --> 02:01.590 from the vSphere client for those two VMs that are running on the ESXi 52 02:01.590 --> 02:02.920 management host. 53 02:02.920 --> 02:04.240 So let's do that next. 54 02:04.240 --> 02:07.370 So here in the vSphere client in our lab environment, so the single sign on 55 02:07.370 --> 02:08.320 domain is right there, 56 02:08.320 --> 02:10.320 ogit.lab. 57 02:10.320 --> 02:12.520 Let's go over to the ESXi management host. 58 02:12.520 --> 02:14.080 We'll click on VMs. 59 02:14.080 --> 02:15.080 There's our two VMs. 60 02:15.080 --> 02:18.990 We'll go ahead and select both of them, then right click and say power and then 61 02:18.990 --> 02:19.520 we'll do 62 02:19.520 --> 02:24.880 the graceful shutdown, which is shutdown guest OS and we'll click on yes. 63 02:24.880 --> 02:28.000 And those two are now being gracefully shut down. 64 02:28.000 --> 02:30.560 So none of those two edge nodes are on their way down gracefully. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 64 02:28.000 --> 02:30.560 So none of those two edge nodes are on their way down gracefully. 65 02:30.560 --> 02:35.720 The next step is to go ahead and do a graceful shutdown of our nested vCenter. 66 02:35.720 --> 02:38.080 So our vCenter is currently running on that same management host. 67 02:38.080 --> 02:41.660 And what I like to do for a nice clean shutdown is go to the management console 68 02:41.660 --> 02:42.480 for the vCenter 69 02:42.480 --> 02:46.720 that's on port 5480 and then do the shutdown from there. 70 02:46.720 --> 02:49.480 And actually before I shut down vCenter, I also want to take a job. 71 02:49.480 --> 02:53.460 Just a moment just to make sure that any other VMs, like I think the mint VM 72 02:53.460 --> 02:54.280 that I launched, 73 02:54.280 --> 02:57.480 I want to make sure any other VMs that are currently running are also grace 74 02:57.480 --> 02:58.040 fully shut 75 02:58.040 --> 02:59.040 down. 76 02:59.040 --> 03:01.730 So we'll go to the vSphere client first, make sure we gracefully shut down any WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 76 02:59.040 --> 03:01.730 So we'll go to the vSphere client first, make sure we gracefully shut down any 77 03:01.730 --> 03:02.240 remaining 78 03:02.240 --> 03:03.360 VMs there. 79 03:03.360 --> 03:06.400 And then we'll go ahead and turn off vCenter itself. 80 03:06.400 --> 03:10.290 So here in the ogit.lab, our vSphere nested environment, I'll go ahead and go 81 03:10.290 --> 03:10.760 to the 82 03:10.760 --> 03:12.720 very top level here, click on VMs. 83 03:12.720 --> 03:17.480 I'm going to sort based on state and I've got mint be right there. 84 03:17.480 --> 03:21.390 So I'm going to go ahead and just take that one right click and go to power and 85 03:21.390 --> 03:21.720 then we'll 86 03:21.720 --> 03:23.600 gracefully power that off as well. 87 03:23.600 --> 03:26.560 They shut down guest OS and click on yes. 88 03:26.560 --> 03:27.560 All right. 89 03:27.560 --> 03:30.260 And then for the vCenter itself, which is right here, I'm going to go ahead and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 89 03:27.560 --> 03:30.260 And then for the vCenter itself, which is right here, I'm going to go ahead and 90 03:30.260 --> 03:30.680 do that 91 03:30.680 --> 03:32.640 from the management console for vCenter. 92 03:32.640 --> 03:36.500 So we can log out right here of the vSphere client and let's head over to the 93 03:36.500 --> 03:37.160 management 94 03:37.160 --> 03:39.320 console for the vCenter itself. 95 03:39.320 --> 03:40.320 And that's right here. 96 03:40.320 --> 03:42.760 So we'll log on as administrator, click login. 97 03:42.760 --> 03:46.640 And then from here, we'll click on actions and we'll click on shutdown. 98 03:46.640 --> 03:50.460 And we'll confirm the shutdown and that's going to gracefully shut down vCenter 99 03:50.460 --> 03:50.520 . 100 03:50.520 --> 03:54.250 So now with the vCenter shutting down, our next step is to go ahead and grace 101 03:54.250 --> 03:54.920 fully power 102 03:54.920 --> 04:00.830 off these three ESXi hosts, the VM that's running as ESXi a and the other VM as WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 102 03:54.920 --> 04:00.830 off these three ESXi hosts, the VM that's running as ESXi a and the other VM as 103 04:00.830 --> 04:01.320 ESXi 104 04:01.320 --> 04:03.480 b and the other one as the ESXi management. 105 04:03.480 --> 04:05.360 Now the way you want to do this is up to you. 106 04:05.360 --> 04:08.610 We could have actually in the vCenter, you know, shut down a couple of them 107 04:08.610 --> 04:09.160 except for 108 04:09.160 --> 04:12.640 the one that was running vCenter itself, or we can use the host client on each 109 04:12.640 --> 04:13.200 of those 110 04:13.200 --> 04:16.790 and do a shutdown there, or the other option is go to our physical environment 111 04:16.790 --> 04:17.200 here at 112 04:17.200 --> 04:20.970 the physical servers in the parent vSphere environment and shut down the 113 04:20.970 --> 04:22.120 individual VMs 114 04:22.120 --> 04:23.200 from here. 115 04:23.200 --> 04:26.400 And because they're running the VMware tools, it'll perform a graceful shutdown 116 04:26.400 --> 04:26.600 . 117 04:26.600 --> 04:30.290 So what are the benefits of logging into these individually with the host WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 117 04:26.600 --> 04:30.290 So what are the benefits of logging into these individually with the host 118 04:30.290 --> 04:31.040 client and then 119 04:31.040 --> 04:32.240 doing a shutdown from there? 120 04:32.240 --> 04:35.640 As you can also verify that there's no VMs that are still running. 121 04:35.640 --> 04:39.070 So even though there are multiple ways of doing this, if we're sure that those 122 04:39.070 --> 04:39.840 VMs are powered 123 04:39.840 --> 04:43.390 off the edge nodes and also the vCenter, we could just go to the parent 124 04:43.390 --> 04:44.400 environment. 125 04:44.400 --> 04:48.040 That's our physical servers in the vSphere environment there and gracefully 126 04:48.040 --> 04:48.560 power off 127 04:48.560 --> 04:49.560 those three VMs. 128 04:49.560 --> 04:50.880 So let's do that next. 129 04:50.880 --> 04:53.680 So to do that, we'll go back to our vSphere parent environment. 130 04:53.680 --> 04:56.320 This is the OGAT.prod domain. 131 04:56.320 --> 04:58.360 The other nested environment was .lab. 132 04:58.360 --> 05:01.080 So from here, here's our nested VMs. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 132 04:58.360 --> 05:01.080 So from here, here's our nested VMs. 133 05:01.080 --> 05:05.770 So if we just choose that folder and click on those three and then right click 134 05:05.770 --> 05:06.520 and select 135 05:06.520 --> 05:07.520 power. 136 05:07.520 --> 05:09.440 And then we can do a graceful shutdown right here. 137 05:09.440 --> 05:12.650 And if we're concerned that again, there might be some VMs still running or v 138 05:12.650 --> 05:13.280 Center hasn't 139 05:13.280 --> 05:17.090 completely shut down, you could individually go into those ESXi host with the 140 05:17.090 --> 05:17.760 host client 141 05:17.760 --> 05:21.080 and just verify it from there and do the shutdown from there if you wanted to. 142 05:21.080 --> 05:23.200 So I'm pretty confident that everything is shut down. 143 05:23.200 --> 05:26.040 So I'm going to go ahead and shut these three VMs down here. 144 05:26.040 --> 05:29.880 I'll click on yes to confirm and those three are on their way to graceful 145 05:29.880 --> 05:30.840 shutdowns. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 145 05:29.880 --> 05:30.840 shutdowns. 146 05:30.840 --> 05:33.200 And we'll give that a moment to complete. 147 05:33.200 --> 05:36.780 And also while they're shutting down, we can also see right here that based on 148 05:36.780 --> 05:37.320 DRS, it 149 05:37.320 --> 05:39.600 did a pretty good distribution of the works. 150 05:39.600 --> 05:47.210 So the NSX local manager here, it ran on ESXi2, ESXi8, it ran on ESXi1 and ESXi 151 05:47.210 --> 05:47.760 B and the 152 05:47.760 --> 05:52.240 management ESXi host, it ran on my physical host three. 153 05:52.240 --> 05:56.060 And that was all courtesy of distributed resource scheduler making decisions on 154 05:56.060 --> 05:56.800 its own as far 155 05:56.800 --> 05:58.240 as where it wanted to put VMs. 156 05:58.240 --> 05:59.240 All right. 157 05:59.240 --> 06:04.350 So ESXi8 is powered off and survey says ESXiB should be close behind and it is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 157 05:59.240 --> 06:04.350 So ESXi8 is powered off and survey says ESXiB should be close behind and it is 158 06:04.350 --> 06:04.920 off. 159 06:04.920 --> 06:09.140 So now with all those VMs turned off and previously all the VMs within those V 160 06:09.140 --> 06:10.160 Ms turned off, let's 161 06:10.160 --> 06:12.880 go ahead and remove all the snapshots. 162 06:12.880 --> 06:17.750 So we'll go to ESXi8, click on the snapshots tab and click on delete all and 163 06:17.750 --> 06:18.760 delete all. 164 06:18.760 --> 06:21.560 And we'll repeat that for each of our ESXi hosts. 165 06:21.560 --> 06:26.340 So for ESXiB, delete all snapshots, confirm that, go to the ESXi management, 166 06:26.340 --> 06:27.200 click delete 167 06:27.200 --> 06:29.200 all, delete all. 168 06:29.200 --> 06:32.790 The NSX global, we didn't actually turn that one on, but I had NSX federations WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 168 06:29.200 --> 06:32.790 The NSX global, we didn't actually turn that one on, but I had NSX federations 169 06:32.790 --> 06:33.440 configured 170 06:33.440 --> 06:34.960 at one point, so I used that as well. 171 06:34.960 --> 06:38.440 But because I'm not touching that at the moment, I'm going to leave that alone. 172 06:38.440 --> 06:42.770 And then the NSX manager we did use was this one right here, NSX manager 01 173 06:42.770 --> 06:43.400 local, and 174 06:43.400 --> 06:46.680 we'll delete all of its snapshots as well, click on delete all. 175 06:46.680 --> 06:50.250 And then the background, those respective ESXi hosts that are supporting those 176 06:50.250 --> 06:50.560 VMs are 177 06:50.560 --> 06:52.960 in the process of deleting those snapshots. 178 06:52.960 --> 06:55.510 So if we will put up our recent tasks right here and I'm going to say, please 179 06:55.510 --> 06:55.960 just show 180 06:55.960 --> 07:01.980 me the running recent tasks, it is now in the process of deleting all snapshots WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 180 06:55.960 --> 07:01.980 me the running recent tasks, it is now in the process of deleting all snapshots 181 07:01.980 --> 07:02.360 . 182 07:02.360 --> 07:07.570 So it already removed the snapshots from ESXiA and B, and now it's working on 183 07:07.570 --> 07:08.920 ESXi management, 184 07:08.920 --> 07:12.160 and the NSX manager will probably take the longest. 185 07:12.160 --> 07:16.070 And as far as how long it'll take, it depends a lot on how much we did and how 186 07:16.070 --> 07:16.600 much was 187 07:16.600 --> 07:18.960 changed on the disks for those virtual machines. 188 07:18.960 --> 07:24.000 So the NSX manager again may take somewhere between five minutes and 30 minutes 189 07:24.000 --> 07:24.400 , and some 190 07:24.400 --> 07:28.160 of that is also dependent on the back end regarding network storage and how 191 07:28.160 --> 07:28.720 fast that 192 07:28.720 --> 07:31.000 is and what the latency is and all that good stuff. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 192 07:28.720 --> 07:31.000 is and what the latency is and all that good stuff. 193 07:31.000 --> 07:34.550 So I'm going to go ahead and simply wait until it's completely done removing 194 07:34.550 --> 07:36.040 all the snapshots, 195 07:36.040 --> 07:40.110 and then I'm going to go back and I'm going to recreate snapshots for each of 196 07:40.110 --> 07:40.920 those VMs, 197 07:40.920 --> 07:45.320 ESXiA, B, management, and also the local NSX manager. 198 07:45.320 --> 07:49.000 And then once we have those new snapshots created, we can then go ahead and run 199 07:49.000 --> 07:49.240 the 200 07:49.240 --> 07:52.920 lab again, make changes, and if we want to revert back to the snapshots that we 201 07:52.920 --> 07:53.400 're about 202 07:53.400 --> 07:57.640 to make, we could go ahead and revert back to the snapshots and start over. 203 07:57.640 --> 08:00.720 For practicing a configuration, we want to do it multiple times. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 203 07:57.640 --> 08:00.720 For practicing a configuration, we want to do it multiple times. 204 08:00.720 --> 08:04.240 Once again, we could restore to the snapshots once we create them. 205 08:04.240 --> 08:07.680 Oh, and based on the timestamps over here, it's giving it away. 206 08:07.680 --> 08:08.680 Happy New Year, everybody. 207 08:08.680 --> 08:11.520 I hope this year is a fantastic one for everybody. 208 08:11.520 --> 08:15.330 All right, so the snapshots are all removed and then I'd go back to each of 209 08:15.330 --> 08:15.960 those VMs 210 08:15.960 --> 08:17.640 and recreate new ones. 211 08:17.640 --> 08:21.510 So here's ESXiA, we'll send it to go ahead and with these snapshots tab 212 08:21.510 --> 08:22.280 selected, click 213 08:22.280 --> 08:25.080 on take snapshot, we'll confirm that. 214 08:25.080 --> 08:28.290 If you want to put descriptions and various titles and so forth for each of the 215 08:28.290 --> 08:28.920 snapshots, 216 08:28.920 --> 08:30.120 no problem at all. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 216 08:28.920 --> 08:30.120 no problem at all. 217 08:30.120 --> 08:33.320 However, what I've discovered is that if I'm doing all the snapshots at the 218 08:33.320 --> 08:33.960 same time 219 08:33.960 --> 08:38.350 for all of these VMs as part of a group, because it's in a lab environment, I 220 08:38.350 --> 08:38.760 rarely 221 08:38.760 --> 08:41.800 need to come back and identify, okay, what was it doing at that time? 222 08:41.800 --> 08:44.080 Because I'm normally coming back to it fairly quickly. 223 08:44.080 --> 08:48.490 So I'll repeat that process for ESXiAP, we'll select it, click on take snapshot 224 08:48.490 --> 08:48.560 , click 225 08:48.560 --> 08:53.730 on create, and repeat that process for ESXiA management and also for the NSX 226 08:53.730 --> 08:54.640 manager. 227 08:54.640 --> 08:58.720 So once we take all the snapshots and then we restart the lab environment, we 228 08:58.720 --> 08:59.080 can then 229 08:59.080 --> 09:02.680 continue to configure whatever it is we want to practice configuring in our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 229 08:59.080 --> 09:02.680 continue to configure whatever it is we want to practice configuring in our 230 09:02.680 --> 09:04.160 home lab environment. 231 09:04.160 --> 09:07.480 And the cool part is we can practice and if something doesn't go right or we 232 09:07.480 --> 09:07.880 want to 233 09:07.880 --> 09:11.960 revert back, we can come back to these snapshots just by saying revert. 234 09:11.960 --> 09:14.420 And when we do the revert, you don't have to actually gracefully power them off 235 09:14.420 --> 09:14.680 . 236 09:14.680 --> 09:18.640 You can say, you know what, I want to revert back to that previous snapshot and 237 09:18.640 --> 09:19.160 boom, it'll 238 09:19.160 --> 09:23.450 power off the VM, restore that snapshot, which is very, very quick because 239 09:23.450 --> 09:24.000 there's 240 09:24.000 --> 09:26.280 no disk merging or anything else. 241 09:26.280 --> 09:28.640 It's just a quick reversion to that previous state. 242 09:28.640 --> 09:31.960 So I'm going to finish off with these snapshots, making sure I have them for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 242 09:28.640 --> 09:31.960 So I'm going to finish off with these snapshots, making sure I have them for 243 09:31.960 --> 09:32.640 each of these 244 09:32.640 --> 09:35.120 VMs and I'll see you my friend in the very next video.