1
00:00:01,140 --> 00:00:01,470
Alright.

2
00:00:01,470 --> 00:00:03,240
So as we just saw,

3
00:00:03,240 --> 00:00:07,060
we can right‑click to add to cluster shared volumes and that creates a

4
00:00:07,060 --> 00:00:11,490
mount point on the C drive of every cluster node,

5
00:00:11,490 --> 00:00:16,940
and note that we can remove one of these virtual disk volumes from CSV.

6
00:00:16,940 --> 00:00:22,230
It just occurred to me I'm going to need a disk larger than 80 to put VMs on it,

7
00:00:22,230 --> 00:00:25,150
so I guess I'm going to need to rinse and repeat.

8
00:00:25,150 --> 00:00:29,340
So let's right‑click and add another virtual disk.

9
00:00:29,340 --> 00:00:33,970
It's good to see this over and over again because at least I know that for me,

10
00:00:33,970 --> 00:00:35,190
I really needed it.

11
00:00:35,190 --> 00:00:38,060
So let's create a much larger disk this time.

12
00:00:38,060 --> 00:00:41,240
I'll call this vm‑disk‑2.

13
00:00:41,240 --> 00:00:41,780
Go Next.

14
00:00:41,780 --> 00:00:47,240
It looks like the free space is 148 so I'm going to do 140.

15
00:00:47,240 --> 00:00:49,040
Okay, that should do it.

16
00:00:49,040 --> 00:00:51,540
Now let's create that.

17
00:00:51,540 --> 00:00:55,540
Again, we'll create a volume doing the same thing that we did before.

18
00:00:55,540 --> 00:00:57,840
I'm not going to assign a drive letter.

19
00:00:57,840 --> 00:01:02,740
I'm going to call this vm2‑volume.

20
00:01:02,740 --> 00:01:05,450
Next, Create.

21
00:01:05,450 --> 00:01:07,540
Excellent.

22
00:01:07,540 --> 00:01:11,140
Alright, so now you see how to create these virtual disks,

23
00:01:11,140 --> 00:01:14,330
and when you right‑click and add them to cluster shared volumes,

24
00:01:14,330 --> 00:01:17,760
the great benefit there is that you've got yourself both

25
00:01:17,760 --> 00:01:21,030
on mem1 and mem2 a local mount point.

26
00:01:21,030 --> 00:01:23,670
Under C, ClusterStorage.

27
00:01:23,670 --> 00:01:24,820
You've got a mount point.

28
00:01:24,820 --> 00:01:27,430
So the idea is that you're highly available VMs,

29
00:01:27,430 --> 00:01:33,340
you'll store those VM VHDs and configuration files in that path,

30
00:01:33,340 --> 00:01:39,570
and if I try a \\mem2\C$ to connect to the administrative share,

31
00:01:39,570 --> 00:01:42,430
notice that we've got mappings or mount points there

32
00:01:42,430 --> 00:01:45,840
as well to that shared storage, so that's CSV.

33
00:01:45,840 --> 00:01:48,780
Now, we need to wrap this demo up so I'm just going to show you,

34
00:01:48,780 --> 00:01:52,340
I'm going to talk you through how to do a highly available VM,

35
00:01:52,340 --> 00:01:55,270
and then we'll continue this discussion in the next module,

36
00:01:55,270 --> 00:01:57,500
but we'll go to Roles, right‑click,

37
00:01:57,500 --> 00:02:00,810
and we can either configure role and this would be what you

38
00:02:00,810 --> 00:02:03,710
do if you have an existing Hyper‑V VM.

39
00:02:03,710 --> 00:02:07,240
We could select Virtual Machine from the list,

40
00:02:07,240 --> 00:02:11,220
and then I have a Windows Server Core machine on this host

41
00:02:11,220 --> 00:02:14,390
that I could bring in and make highly available by putting its

42
00:02:14,390 --> 00:02:16,840
files on cluster shared volumes.

43
00:02:16,840 --> 00:02:20,380
The other thing we could do is to right‑click Roles and create

44
00:02:20,380 --> 00:02:23,040
a new VM from scratch because remember I've installed the

45
00:02:23,040 --> 00:02:26,090
Hyper‑V role on each of these nodes.

46
00:02:26,090 --> 00:02:30,740
So I can go to a New Virtual Machine, select the owner node,

47
00:02:30,740 --> 00:02:33,860
and then walk through the virtual machine wizard just like we

48
00:02:33,860 --> 00:02:36,600
would if we were on the Hyper‑V Manager itself,

49
00:02:36,600 --> 00:02:38,040
you see what I mean?

50
00:02:38,040 --> 00:02:39,940
Either way, at the end of that process,

51
00:02:39,940 --> 00:02:44,240
we would have that VM as a role that can then be moved to

52
00:02:44,240 --> 00:02:51,000
another node in a failover configuration. More on that, though, in the next lesson.

