What about Storage Spaces Direct?
I give you the citation for this image in the lower left
corner, and, of course, you've always got the Pluralsight
exercise files to fall back on.
But as I was saying, when you're using Storage Spaces in the
context of a Windows Server failover cluster, that failover
cluster is reliant upon shared storage.
And so you can create a virtual storage pool that aggregates physical disks
from some or all of the cluster nodes in your cluster.
And the way the vocab works, the object model with Storage Spaces,
is that you create your storage pool,
which is an aggregation of physical disks, and then from that
storage pool you start to break out virtual disks.
And lastly, when you're doing Storage Spaces Direct,
you can make sure that those virtual disks are replicated to each cluster
node as VHD or VHDX files, and those cluster shared volumes, as they're
called, will be on the file system of each node.
And again,
this makes that attachment and detachment process much faster when you
need to move a workload from one primary node to another one because
that secondary node that's going to take over already has a synchronized
copy of that virtual disk volume.
So this comes into play with workloads like Scale‑Out File Server where
you've got highly available file shares, and that actually, SOFS, can be combined with highly available Hyper‑V virtual machines.