1
00:00:01,040 --> 00:00:02,090
In this demonstration,

2
00:00:02,090 --> 00:00:06,610
I'll highlight some of the failover clustering‑related concepts we went over,

3
00:00:06,610 --> 00:00:08,540
starting with Cloud Witness.

4
00:00:08,540 --> 00:00:10,630
Now there is, by definition,

5
00:00:10,630 --> 00:00:13,740
going to be some overlap among the different modules of the course,

6
00:00:13,740 --> 00:00:16,000
and I want you to understand that's not accidental,

7
00:00:16,000 --> 00:00:17,440
it's intentional.

8
00:00:17,440 --> 00:00:21,980
Number one part of my effectiveness as a teacher is interweaving the

9
00:00:21,980 --> 00:00:25,360
content within a course and between related courses.

10
00:00:25,360 --> 00:00:28,960
Remember we have a number of courses that support AZ‑801.

11
00:00:28,960 --> 00:00:32,140
And also as an adult educator for well over 20 years,

12
00:00:32,140 --> 00:00:35,070
I know that repetition, especially when you're just learning,

13
00:00:35,070 --> 00:00:36,740
is really important.

14
00:00:36,740 --> 00:00:38,340
So, don't mind the repetition.

15
00:00:38,340 --> 00:00:43,770
Let's open up VS Code and recall that with respect to quorum and witnesses,

16
00:00:43,770 --> 00:00:46,670
we've got the various options, and it's easy as pie,

17
00:00:46,670 --> 00:00:50,840
so to speak, to use PowerShell to create a witness of any kind.

18
00:00:50,840 --> 00:00:53,560
Notice on line 18 in my PowerShell script,

19
00:00:53,560 --> 00:00:56,650
Set‑ClusterQuorum and then CloudWitness.

20
00:00:56,650 --> 00:00:58,400
And when you go down that route,

21
00:00:58,400 --> 00:01:00,690
you have to provide the name of your Azure storage

22
00:01:00,690 --> 00:01:02,810
account and one of your access keys.

23
00:01:02,810 --> 00:01:03,960
How do you do that?

24
00:01:03,960 --> 00:01:05,150
Again, this is good review.

25
00:01:05,150 --> 00:01:10,630
Let's go into the Azure portal, and let's dial up my storage accounts.

26
00:01:10,630 --> 00:01:16,240
And I have one called timstorage001.

27
00:01:16,240 --> 00:01:18,520
And there's a number of ways to authenticate and

28
00:01:18,520 --> 00:01:20,710
authorize access to a storage account.

29
00:01:20,710 --> 00:01:24,700
The original way is with these access keys, which are, you know, sensitive.

30
00:01:24,700 --> 00:01:29,300
You want to rotate them on a schedule, so they don't leak anywhere.

31
00:01:29,300 --> 00:01:32,350
And unfortunately, in this example,

32
00:01:32,350 --> 00:01:35,720
you could either do the raw text of the access key,

33
00:01:35,720 --> 00:01:40,500
or frankly, if you were authenticated to Azure and Visual Studio Code,

34
00:01:40,500 --> 00:01:43,330
we could retrieve the access key from KeyVault,

35
00:01:43,330 --> 00:01:45,940
which would be a far superior option.

36
00:01:45,940 --> 00:01:47,050
So that's the witness.

37
00:01:47,050 --> 00:01:51,640
Another way to go, of course, is back in the Cluster Manager MMC.

38
00:01:51,640 --> 00:01:55,550
We can right‑click our server, and we can come down to More Actions,

39
00:01:55,550 --> 00:01:58,530
and we've got Configure Cluster Quorum Settings,

40
00:01:58,530 --> 00:02:01,680
and that will allow us to step through a wizard to do the

41
00:02:01,680 --> 00:02:05,200
same exact thing or to change your mind if you're already

42
00:02:05,200 --> 00:02:07,740
using a particular kind of witness.

43
00:02:07,740 --> 00:02:11,520
So in terms of some of those roles, you might remember in the previous lesson,

44
00:02:11,520 --> 00:02:16,740
I ran into some dead ends trying to create a highly available virtual machine.

45
00:02:16,740 --> 00:02:19,270
Now remember the procedure there is you're going to want to have

46
00:02:19,270 --> 00:02:21,900
your cluster nodes up running and available,

47
00:02:21,900 --> 00:02:25,840
and you also want to make sure that your shared storage is sorted out.

48
00:02:25,840 --> 00:02:29,450
We used the enable storage spaces direct PowerShell

49
00:02:29,450 --> 00:02:33,340
cmdlet to auto create this Cluster Pool 1,

50
00:02:33,340 --> 00:02:35,290
this S2D pool.

51
00:02:35,290 --> 00:02:38,920
And then within that pool, if I go down to Physical Disks,

52
00:02:38,920 --> 00:02:43,940
it enlisted my two prepared disks in each of my two nodes.

53
00:02:43,940 --> 00:02:49,260
And then we can then start to carve Virtual Disks from those PhysicalDisks,

54
00:02:49,260 --> 00:02:52,640
and we can get over there on the Disks splayed as well.

55
00:02:52,640 --> 00:02:54,860
And I showed you how to step through that wizard,

56
00:02:54,860 --> 00:02:58,440
and then once you've created that resource,

57
00:02:58,440 --> 00:03:02,860
you can add to or remove from the Cluster Shared

58
00:03:02,860 --> 00:03:05,740
Volume simply by right‑clicking.

59
00:03:05,740 --> 00:03:08,070
And the benefit of the Cluster Shared Volume,

60
00:03:08,070 --> 00:03:08,980
or CSV,

61
00:03:08,980 --> 00:03:12,290
is that you then have a mount point on every one of

62
00:03:12,290 --> 00:03:16,060
your cluster nodes in the cluster, and it's the same path too,

63
00:03:16,060 --> 00:03:18,560
see ClusterStorage vm‑disk.

64
00:03:18,560 --> 00:03:22,520
Now I think my problem in the previous lesson,

65
00:03:22,520 --> 00:03:25,840
let me go to Roles, I do have a virtual machine,

66
00:03:25,840 --> 00:03:30,040
a highly available VM that's up and running and happy and ready to go.

67
00:03:30,040 --> 00:03:32,770
I'm not going to go through the thing of creating one,

68
00:03:32,770 --> 00:03:36,110
because, hopefully, you're coming out of the previous module.

69
00:03:36,110 --> 00:03:39,390
But remember what you can do to do a highly available VM is

70
00:03:39,390 --> 00:03:42,640
that you can either start from scratch and go through the

71
00:03:42,640 --> 00:03:45,220
Hyper‑V New Virtual Machine wizard.

72
00:03:45,220 --> 00:03:49,200
You choose a node, and then you can just step through the wizard,

73
00:03:49,200 --> 00:03:52,140
or you can use PowerShell, whatever you want to do.

74
00:03:52,140 --> 00:03:57,560
The other way to go is configure role, and then in the High Availability Wizard,

75
00:03:57,560 --> 00:03:59,210
you can choose Virtual Machine,

76
00:03:59,210 --> 00:04:03,470
and that will enumerate any VMs that are detected on any of your

77
00:04:03,470 --> 00:04:06,540
nodes that have the Hyper‑V role installed.

78
00:04:06,540 --> 00:04:09,870
So once you're there, once the VM is up and running,

79
00:04:09,870 --> 00:04:11,990
there are a number of things that we can do here,

80
00:04:11,990 --> 00:04:16,800
including right‑clicking and Manage to open up the Hyper‑V Manager directly.

81
00:04:16,800 --> 00:04:21,210
Because, after all, I'm on cluster node MEM1 right now and by definition,

82
00:04:21,210 --> 00:04:26,240
it has the Hyper‑V role and the Hyper‑V Management Tools already installed.

83
00:04:26,240 --> 00:04:27,680
Anyway, long story short,

84
00:04:27,680 --> 00:04:33,870
my problem from the previous lesson is I was not storing the hard drive,

85
00:04:33,870 --> 00:04:37,290
and the VM configuration in the Cluster Shared Volume.

86
00:04:37,290 --> 00:04:39,660
I know it's grayed out because the VMs running,

87
00:04:39,660 --> 00:04:43,240
but notice that this virtual machine's virtual hard disk is in the

88
00:04:43,240 --> 00:04:47,740
VM disk virtual disk under C:\ClusterStorage.

89
00:04:47,740 --> 00:04:53,330
That's critical because that makes the VM available to all nodes in the cluster,

90
00:04:53,330 --> 00:04:56,940
and that will make live migration a snap.

91
00:04:56,940 --> 00:05:01,240
What I actually needed to do is at the Hyper‑V host level,

92
00:05:01,240 --> 00:05:05,730
go into Hyper‑V Settings and notice that I changed the Virtual Machines

93
00:05:05,730 --> 00:05:09,540
property to the CSV that I want to use in that case.

94
00:05:09,540 --> 00:05:11,340
Hopefully, that makes sense.

95
00:05:11,340 --> 00:05:14,690
Now you'll see I already have a node called Scale‑Out File Server,

96
00:05:14,690 --> 00:05:18,280
let me show you and work through the highly available

97
00:05:18,280 --> 00:05:20,090
file share business with you right now.

98
00:05:20,090 --> 00:05:23,240
Let's go through, right‑click, Configure Role,

99
00:05:23,240 --> 00:05:26,120
and let's skip this first page, so we don't see it anymore.

100
00:05:26,120 --> 00:05:28,830
We'll choose the File Server as our role,

101
00:05:28,830 --> 00:05:31,550
and then we're asked that question is this going to be an

102
00:05:31,550 --> 00:05:34,240
ordinary File Server or a Scale‑Out File Server?

103
00:05:34,240 --> 00:05:36,540
I'm going to do a File Server.

104
00:05:36,540 --> 00:05:37,430
Give it a name.

105
00:05:37,430 --> 00:05:41,650
I'll call this, let's see, how about I call it az801fs.

106
00:05:41,650 --> 00:05:47,130
And then we have a Client Access Point, this needs to be an unused address,

107
00:05:47,130 --> 00:05:49,800
and we can validate that by nominating an address

108
00:05:49,800 --> 00:05:51,460
and validating by hitting Next.

109
00:05:51,460 --> 00:05:56,150
And if there's a conflict, that'll work, it will show available storage.

110
00:05:56,150 --> 00:06:02,430
In this case, we've got our CSV that I created before class called sofs‑disk,

111
00:06:02,430 --> 00:06:06,390
and this is selecting the storage volume that I want to assign.

112
00:06:06,390 --> 00:06:08,070
Now you'd have to have that created.

113
00:06:08,070 --> 00:06:11,950
Now it's telling me that at least one disk needs to have a drive letter,

114
00:06:11,950 --> 00:06:16,220
aha, so that is, let's see, so we're going to have to do some work here.

115
00:06:16,220 --> 00:06:19,360
And again, this tends to happen with me when I'm demoing,

116
00:06:19,360 --> 00:06:22,840
and it can be a good troubleshooting experience.

117
00:06:22,840 --> 00:06:27,690
So let's go to sofs‑disk, and then let's come down below.

118
00:06:27,690 --> 00:06:31,660
When I created the Volume, I obviously didn't do a drive letter,

119
00:06:31,660 --> 00:06:35,340
so let me right‑click the Volume and change the drive letter,

120
00:06:35,340 --> 00:06:38,400
and I'm just going to call this drive F for file share.

121
00:06:38,400 --> 00:06:38,980
How's that?

122
00:06:38,980 --> 00:06:40,540
So we'll do that.

123
00:06:40,540 --> 00:06:43,250
And now that that CSV volume is available,

124
00:06:43,250 --> 00:06:45,760
it has a drive letter, so it's anchored.

125
00:06:45,760 --> 00:06:49,010
That drive letter needs to be available on all nodes, by the way.

126
00:06:49,010 --> 00:06:52,860
Let me configure the role, File Server, Next,

127
00:06:52,860 --> 00:06:57,980
File Server for general use, I had called this az801fs,

128
00:06:57,980 --> 00:07:03,240
and I used, I think, 88 as my client access address,

129
00:07:03,240 --> 00:07:07,040
and that'll be registered as a hostname in DNS.

130
00:07:07,040 --> 00:07:12,540
I'll select the sofs‑disk virtual disk that's in the Cluster Shared Volumes.

131
00:07:12,540 --> 00:07:16,340
We're ready to configure, Next.

132
00:07:16,340 --> 00:07:22,340
Okay, so it tells us here that the network name is az801fs.

133
00:07:22,340 --> 00:07:30,000
We've got a virtual IP, so okay good, so let's go to az801fs, our running File Server.