1
00:00:01,040 --> 00:00:01,400
Oh,

2
00:00:01,400 --> 00:00:04,850
looks like I've got some problems. You knew that anyway about

3
00:00:04,850 --> 00:00:07,930
me, but I'm talking about the failover cluster. And if we

4
00:00:07,930 --> 00:00:10,480
expand the storage system particularly,

5
00:00:10,480 --> 00:00:13,350
this is where we can get into our pools. This is where we

6
00:00:13,350 --> 00:00:16,890
can get into our virtual disks that may or may not be part

7
00:00:16,890 --> 00:00:19,040
of a cluster shared volume.

8
00:00:19,040 --> 00:00:21,820
All right, so to get to this point,

9
00:00:21,820 --> 00:00:25,920
this is some review earlier in the course, there was just this single

10
00:00:25,920 --> 00:00:31,200
PowerShell cmdlet. To enable cluster storage direct, you specify the name of

11
00:00:31,200 --> 00:00:35,760
the cluster. In my case, it's az801cluster. Optionally, you can provide a

12
00:00:35,760 --> 00:00:40,610
pool‑friendly name, and that will go through and enlist all available

13
00:00:40,610 --> 00:00:44,120
unallocated storage on those nodes, simple as that.

14
00:00:44,120 --> 00:00:47,720
And then from now on, any new nodes will be enlisted into the cluster, so

15
00:00:47,720 --> 00:00:52,490
it's a pretty powerful operation. And I found reverse engineering it trying

16
00:00:52,490 --> 00:00:57,190
to get out of a Storage Spaces Direct environment to be pretty painful, so

17
00:00:57,190 --> 00:00:59,640
I wouldn't wish that on anybody.

18
00:00:59,640 --> 00:01:01,210
All right, so as you can see here,

19
00:01:01,210 --> 00:01:06,040
I've got my single cluster pool, and we can report on it in Failover Cluster

20
00:01:06,040 --> 00:01:12,490
Manager down below. Our used space is a half a TB. Our capacity is 506. Wow!

21
00:01:12,490 --> 00:01:15,440
I'm running pretty low on free space here.

22
00:01:15,440 --> 00:01:18,630
We can report on the physical disks that are included here.

23
00:01:18,630 --> 00:01:22,600
We've got looks like two on one node and two on the other.

24
00:01:22,600 --> 00:01:26,160
I can tell that only because of the IDs. And then we have

25
00:01:26,160 --> 00:01:29,090
the virtual disks that we've created here for various

26
00:01:29,090 --> 00:01:32,540
reasons and a couple like my VM disk,

27
00:01:32,540 --> 00:01:36,600
I've added to Cluster Shared Volume, so it's mounted under the point

28
00:01:36,600 --> 00:01:41,040
C:\ClusterStorage\vm‑disk on all cluster nodes.

29
00:01:41,040 --> 00:01:44,490
The default virtual disk is ClusterPerformanceHistory.

30
00:01:44,490 --> 00:01:49,770
You may see some additional system created disks in terms of, especially

31
00:01:49,770 --> 00:01:54,090
actually, if you're doing tiered storage. And then ultimately,

32
00:01:54,090 --> 00:01:57,570
as I said, we can manage those individual disks here.

33
00:01:57,570 --> 00:01:58,530
Like, for example,

34
00:01:58,530 --> 00:02:04,230
if we pick on this test disk, right‑click. We can take the disk

35
00:02:04,230 --> 00:02:09,000
offline. We can filter event log. We can replicate that storage

36
00:02:09,000 --> 00:02:13,050
using storage replication. We can go to its properties where it just

37
00:02:13,050 --> 00:02:18,290
shows us things like dependencies, how you want to handle resource failure.

38
00:02:18,290 --> 00:02:21,890
This is a similar motif to how you would handle a Windows service if you

39
00:02:21,890 --> 00:02:26,550
want the storage to, if there's a failure, for Windows to attempt a certain

40
00:02:26,550 --> 00:02:30,880
number of times within a certain waiting period to try to restart the

41
00:02:30,880 --> 00:02:36,650
storage. And notice that we have the preferred owner policy for storage for

42
00:02:36,650 --> 00:02:41,800
our virtual disks, as well as for our nodes. That means, of course, that we

43
00:02:41,800 --> 00:02:45,870
can right‑click one of these virtual disks. And besides enabling

44
00:02:45,870 --> 00:02:52,470
replication, we can simulate failure to see that failover take place, as

45
00:02:52,470 --> 00:02:57,690
well as assign to another role if you want to associate a clustered role

46
00:02:57,690 --> 00:03:01,830
with another virtual disk, or is there anything else in there?

47
00:03:01,830 --> 00:03:04,440
Show Dependency Report, no that's about it.

48
00:03:04,440 --> 00:03:05,380
Long story short,

49
00:03:05,380 --> 00:03:08,210
I strongly suggest that you click around in here. And when you're

50
00:03:08,210 --> 00:03:12,010
browsing Failover Cluster Manager, practice right‑clicking on

51
00:03:12,010 --> 00:03:15,900
just about everything to get an idea of what possibilities exist

52
00:03:15,900 --> 00:03:17,500
within this control plane.

53
00:03:17,500 --> 00:03:22,220
And you'll remember by means of review that Windows Admin

54
00:03:22,220 --> 00:03:25,470
Center is slowly catching up in parity.

55
00:03:25,470 --> 00:03:30,370
You can do probably the most common failover cluster administration in

56
00:03:30,370 --> 00:03:33,570
the browser. But for anything really substantial,

57
00:03:33,570 --> 00:03:40,000
you'll want to work either in Windows PowerShell or here in the Failover Cluster Manager.