What did we learn in this first module?
Well,
definitely there's the theme that the Windows Server
engineers at Microsoft have the customer in mind,
particularly customers who are cost‑conscious in terms of they may
not be able to afford all that shared storage hardware. Maybe
they're not able to afford server hardware.
So remember, we've got the idea of guest clustering where you can set up
failover clusters entirely within VM fabric, or virtual machine fabric, and
also, Storage Spaces Direct with Cluster Shared Volumes.
Now, in terms of what you can do in Azure,
there's so many choices, of course, with Azure being a public cloud,
but assuming that you're doing a lift‑and‑shift migration,
you can absolutely run failover clusters,
both top line clusters where you're using Azure VMs as cluster nodes, or
you can enable nested virtualization on those Azure VMs and then set up
Hyper‑V with a guest cluster on those VMs. Nested virtualization is not
supported by all VM sizes in Azure, but a pretty good number of them.
Now, up next in module two,
we're going to continue our work with failover clustering,
particularly diving into storage because we didn't set
up storage in this first module.
I'm taking a step by step into the deep end of the pool. Happy studying.