1
00:00:01,440 --> 00:00:03,540
What did we learn in this first module?

2
00:00:03,540 --> 00:00:03,700
Well,

3
00:00:03,700 --> 00:00:06,720
definitely there's the theme that the Windows Server

4
00:00:06,720 --> 00:00:09,780
engineers at Microsoft have the customer in mind,

5
00:00:09,780 --> 00:00:13,790
particularly customers who are cost‑conscious in terms of they may

6
00:00:13,790 --> 00:00:18,250
not be able to afford all that shared storage hardware. Maybe

7
00:00:18,250 --> 00:00:20,700
they're not able to afford server hardware.

8
00:00:20,700 --> 00:00:24,520
So remember, we've got the idea of guest clustering where you can set up

9
00:00:24,520 --> 00:00:30,800
failover clusters entirely within VM fabric, or virtual machine fabric, and

10
00:00:30,800 --> 00:00:34,440
also, Storage Spaces Direct with Cluster Shared Volumes.

11
00:00:34,440 --> 00:00:37,240
Now, in terms of what you can do in Azure,

12
00:00:37,240 --> 00:00:40,760
there's so many choices, of course, with Azure being a public cloud,

13
00:00:40,760 --> 00:00:43,970
but assuming that you're doing a lift‑and‑shift migration,

14
00:00:43,970 --> 00:00:47,410
you can absolutely run failover clusters,

15
00:00:47,410 --> 00:00:53,040
both top line clusters where you're using Azure VMs as cluster nodes, or

16
00:00:53,040 --> 00:00:57,410
you can enable nested virtualization on those Azure VMs and then set up

17
00:00:57,410 --> 00:01:03,160
Hyper‑V with a guest cluster on those VMs. Nested virtualization is not

18
00:01:03,160 --> 00:01:08,440
supported by all VM sizes in Azure, but a pretty good number of them.

19
00:01:08,440 --> 00:01:10,140
Now, up next in module two,

20
00:01:10,140 --> 00:01:13,060
we're going to continue our work with failover clustering,

21
00:01:13,060 --> 00:01:16,330
particularly diving into storage because we didn't set

22
00:01:16,330 --> 00:01:18,740
up storage in this first module.

23
00:01:18,740 --> 00:01:24,000
I'm taking a step by step into the deep end of the pool. Happy studying.