Alright.
So as we just saw,
we can right‑click to add to cluster shared volumes and that creates a
mount point on the C drive of every cluster node,
and note that we can remove one of these virtual disk volumes from CSV.
It just occurred to me I'm going to need a disk larger than 80 to put VMs on it,
so I guess I'm going to need to rinse and repeat.
So let's right‑click and add another virtual disk.
It's good to see this over and over again because at least I know that for me,
I really needed it.
So let's create a much larger disk this time.
I'll call this vm‑disk‑2.
Go Next.
It looks like the free space is 148 so I'm going to do 140.
Okay, that should do it.
Now let's create that.
Again, we'll create a volume doing the same thing that we did before.
I'm not going to assign a drive letter.
I'm going to call this vm2‑volume.
Next, Create.
Excellent.
Alright, so now you see how to create these virtual disks,
and when you right‑click and add them to cluster shared volumes,
the great benefit there is that you've got yourself both
on mem1 and mem2 a local mount point.
Under C, ClusterStorage.
You've got a mount point.
So the idea is that you're highly available VMs,
you'll store those VM VHDs and configuration files in that path,
and if I try a \\mem2\C$ to connect to the administrative share,
notice that we've got mappings or mount points there
as well to that shared storage, so that's CSV.
Now, we need to wrap this demo up so I'm just going to show you,
I'm going to talk you through how to do a highly available VM,
and then we'll continue this discussion in the next module,
but we'll go to Roles, right‑click,
and we can either configure role and this would be what you
do if you have an existing Hyper‑V VM.
We could select Virtual Machine from the list,
and then I have a Windows Server Core machine on this host
that I could bring in and make highly available by putting its
files on cluster shared volumes.
The other thing we could do is to right‑click Roles and create
a new VM from scratch because remember I've installed the
Hyper‑V role on each of these nodes.
So I can go to a New Virtual Machine, select the owner node,
and then walk through the virtual machine wizard just like we
would if we were on the Hyper‑V Manager itself,
you see what I mean?
Either way, at the end of that process,
we would have that VM as a role that can then be moved to
another node in a failover configuration. More on that, though, in the next lesson.