1
00:00:00,940 --> 00:00:04,770
Now, what's this about Cluster‑Aware Updating, or CAU?

2
00:00:04,770 --> 00:00:05,170
Well,

3
00:00:05,170 --> 00:00:08,590
this is a built‑in capability of Windows Server failover

4
00:00:08,590 --> 00:00:12,180
clustering that automates Microsoft software updates without

5
00:00:12,180 --> 00:00:15,040
sacrificing high availability.

6
00:00:15,040 --> 00:00:17,880
It is a separate server feature that you'll need to install,

7
00:00:17,880 --> 00:00:21,140
it has a separate user interface as a matter of fact,

8
00:00:21,140 --> 00:00:23,040
separate PowerShell module.

9
00:00:23,040 --> 00:00:26,100
And here, we're looking at Microsoft updates,

10
00:00:26,100 --> 00:00:30,900
and you can either run Cluster‑Aware Updating runs on

11
00:00:30,900 --> 00:00:33,000
your cluster manually and interactively,

12
00:00:33,000 --> 00:00:35,340
or, perhaps more commonly,

13
00:00:35,340 --> 00:00:39,750
you'll schedule the cluster to do self‑updating runs on its own.

14
00:00:39,750 --> 00:00:42,680
One thing that's neat about Cluster‑Aware Updating,

15
00:00:42,680 --> 00:00:46,950
among many things actually, is that it's a hands‑off process.

16
00:00:46,950 --> 00:00:49,440
In other words, it automates,

17
00:00:49,440 --> 00:00:53,080
patching your servers from either Microsoft update or you

18
00:00:53,080 --> 00:00:55,340
could use Windows Server Update Service.

19
00:00:55,340 --> 00:01:00,120
And it automates draining clustered roles from each node,

20
00:01:00,120 --> 00:01:04,120
updating the node, taking it offline, putting it in maintenance mode,

21
00:01:04,120 --> 00:01:06,140
patching, rebooting,

22
00:01:06,140 --> 00:01:09,410
and then failing back the clustered roles that that

23
00:01:09,410 --> 00:01:11,780
machine should host or be primary for.

24
00:01:11,780 --> 00:01:18,740
It's a rolling update and nice way to keep your cluster hosts secure.

25
00:01:18,740 --> 00:01:20,050
What is a cluster set?

26
00:01:20,050 --> 00:01:24,730
Well, this is a more recent addition to Windows Server failover clustering.

27
00:01:24,730 --> 00:01:29,630
It is a way to create a much larger topology for

28
00:01:29,630 --> 00:01:31,480
your Windows cluster environment.

29
00:01:31,480 --> 00:01:32,740
In the previous module,

30
00:01:32,740 --> 00:01:37,440
we spent just a small amount of time looking at the stretch cluster,

31
00:01:37,440 --> 00:01:40,800
where you have a single cluster that has replicated

32
00:01:40,800 --> 00:01:43,940
shared storage across multiple sites,

33
00:01:43,940 --> 00:01:47,340
and the nodes are all part of the same logical cluster.

34
00:01:47,340 --> 00:01:50,500
Well, cluster set is another layer of abstraction.

35
00:01:50,500 --> 00:01:52,790
As you can see on the top of the screen,

36
00:01:52,790 --> 00:01:55,440
you've got a Management cluster,

37
00:01:55,440 --> 00:02:01,940
and then you join one or more totally separate member clusters to the set.

38
00:02:01,940 --> 00:02:08,120
This uses the Scale‑Out File Server namespace as a way to logically connect

39
00:02:08,120 --> 00:02:13,040
or logically have a pathway across this topology here.

40
00:02:13,040 --> 00:02:17,990
And this gives us potentially some really big benefits for businesses

41
00:02:17,990 --> 00:02:22,560
that may or may not be comprising of multiple sites,

42
00:02:22,560 --> 00:02:24,020
but at the least,

43
00:02:24,020 --> 00:02:29,130
you want to provide as many layers of redundancy and fault tolerance as you can.

44
00:02:29,130 --> 00:02:34,130
So again, this is another image of a cluster set, a logical image from the docs.

45
00:02:34,130 --> 00:02:37,740
You can see my attribution URL in the upper right.

46
00:02:37,740 --> 00:02:40,750
That when you define your cluster set with PowerShell,

47
00:02:40,750 --> 00:02:43,350
you're using the Scale‑Out File Server role,

48
00:02:43,350 --> 00:02:48,680
you've got your management cluster, and then you've got your member clusters.

49
00:02:48,680 --> 00:02:51,550
And the idea here is that you then have much bigger

50
00:02:51,550 --> 00:02:54,050
portability of your services,

51
00:02:54,050 --> 00:02:59,340
specifically cluster set is intended for highly available virtual machines.

52
00:02:59,340 --> 00:03:02,920
So you may have a VM that's running in the management cluster,

53
00:03:02,920 --> 00:03:05,470
and then a failover event needs to take place.

54
00:03:05,470 --> 00:03:09,700
It could not only failover to another node within the management cluster,

55
00:03:09,700 --> 00:03:14,740
but it could actually failover to any of your member clusters as well.

56
00:03:14,740 --> 00:03:17,860
Another thing that you do with the cluster set is that you

57
00:03:17,860 --> 00:03:20,740
define fault domains and availability sets.

58
00:03:20,740 --> 00:03:24,990
Now, you might be thinking, if you've used high availability in Azure,

59
00:03:24,990 --> 00:03:27,400
particularly with virtual machines, you might think,

60
00:03:27,400 --> 00:03:31,940
wait a minute now, I know what an availability set is and a fault domain.

61
00:03:31,940 --> 00:03:35,580
In Azure terminology an availability set is two or more

62
00:03:35,580 --> 00:03:39,500
replica VMs that you put in this container,

63
00:03:39,500 --> 00:03:40,640
essentially,

64
00:03:40,640 --> 00:03:44,310
that tells Microsoft to separate those VMs to make sure

65
00:03:44,310 --> 00:03:48,140
that they're on separate server racks, those are fault domains,

66
00:03:48,140 --> 00:03:51,340
and separate hosts, those are update domains,

67
00:03:51,340 --> 00:03:53,490
to ensure availability of your service.

68
00:03:53,490 --> 00:03:56,080
Well notice that you've got a similar motif here,

69
00:03:56,080 --> 00:03:57,630
where in this topology,

70
00:03:57,630 --> 00:04:02,240
it looks like Member Cluster 1 and 2 are logically

71
00:04:02,240 --> 00:04:04,540
associated with Fault Domain A.

72
00:04:04,540 --> 00:04:09,180
So, these could be clusters and nodes that are in the same datacenter,

73
00:04:09,180 --> 00:04:11,040
the same rack, the same site,

74
00:04:11,040 --> 00:04:16,080
and then we have Cluster 3 and Cluster 4 as separate fault domains.

75
00:04:16,080 --> 00:04:21,490
So you can, again, just get a wider picture of your cluster topology.

76
00:04:21,490 --> 00:04:23,440
I hope that makes some semblance of sense.

77
00:04:23,440 --> 00:04:27,530
This is another feature that could be a course unto itself.

78
00:04:27,530 --> 00:04:29,520
It's a gigantic subject.

79
00:04:29,520 --> 00:04:33,170
I've just explained the surface‑level points that you

80
00:04:33,170 --> 00:04:36,040
should keep in mind about cluster sets.

81
00:04:36,040 --> 00:04:40,430
So on the exam, if AZ‑104 were to ask you a question like,

82
00:04:40,430 --> 00:04:44,340
you're a hybrid cloud administrator and you need to

83
00:04:44,340 --> 00:04:48,330
put together a logical layer, a high‑availability layer,

84
00:04:48,330 --> 00:04:52,240
on multiple failover clusters across multiple sites.

85
00:04:52,240 --> 00:04:55,600
The correct answer would be to use, say,

86
00:04:55,600 --> 00:05:00,860
PowerShell to define a cluster set in which you've got one management cluster,

87
00:05:00,860 --> 00:05:14,000
one or more member clusters, SOFS namespace that goes across the entire set, and then you aggregate those clusters into fault domains.

