1
00:00:01,540 --> 00:00:03,510
As we saw in the previous module,

2
00:00:03,510 --> 00:00:07,920
Windows Server failover clustering supports a good handful of cluster roles,

3
00:00:07,920 --> 00:00:11,690
many of which are aligned to native Windows Server

4
00:00:11,690 --> 00:00:14,190
roles, like DHCP Server and so on.

5
00:00:14,190 --> 00:00:17,630
The two production workloads that I see in the industry most

6
00:00:17,630 --> 00:00:22,440
commonly are highly available Hyper‑V virtual machines and

7
00:00:22,440 --> 00:00:24,100
highly available file shares.

8
00:00:24,100 --> 00:00:26,940
And, in particular, you can combine those two with

9
00:00:26,940 --> 00:00:32,390
Scale‑Out File Server, or SOFS. SOFS is one of the two ways

10
00:00:32,390 --> 00:00:37,110
to do a highly available file share, continuously available file shares.

11
00:00:37,110 --> 00:00:37,280
Now,

12
00:00:37,280 --> 00:00:39,720
the thing with Scale Out that's a bit different from a

13
00:00:39,720 --> 00:00:42,790
traditional clustered file share is that it's active,

14
00:00:42,790 --> 00:00:43,250
active.

15
00:00:43,250 --> 00:00:47,890
All nodes host the share, and this is to support the fact

16
00:00:47,890 --> 00:00:51,730
that when you're doing SOFS, you're not offering general

17
00:00:51,730 --> 00:00:54,110
purpose file shares, instead,

18
00:00:54,110 --> 00:00:58,080
SOFS is designed specifically for virtual machine hosting,

19
00:00:58,080 --> 00:01:01,810
Cluster Shared Volumes and virtual machine hosting.

20
00:01:01,810 --> 00:01:07,470
So when you do an SOFS clustered role, you're using Storage Spaces Direct,

21
00:01:07,470 --> 00:01:09,840
you're using Cluster Shared Volumes,

22
00:01:09,840 --> 00:01:15,560
you're using Hyper‑V, and you're storing those Hyper‑V VMs in the SOFS file

23
00:01:15,560 --> 00:01:21,840
shares. You then get native features like automatic client rebalancing, and

24
00:01:21,840 --> 00:01:27,840
this is where the failover cluster will live migrate virtual machines so that

25
00:01:27,840 --> 00:01:30,860
they're active on another node, let's say,

26
00:01:30,860 --> 00:01:35,670
just to make sure that a particular node isn't oversaturated with virtual

27
00:01:35,670 --> 00:01:40,960
machines, okay? So to review, when you're doing a file share cluster

28
00:01:40,960 --> 00:01:44,700
node, there's the file server for general use that you'll use for

29
00:01:44,700 --> 00:01:47,740
traditional highly available file shares.

30
00:01:47,740 --> 00:01:52,670
You can share these folders with Server Message Block or Network File System,

31
00:01:52,670 --> 00:01:57,500
and these highly available shares are compatible with File Server

32
00:01:57,500 --> 00:02:01,730
Resource Manager, that means you can do data deduplication. Also

33
00:02:01,730 --> 00:02:05,740
compatible with Distributed File System, or DFS trees.

34
00:02:05,740 --> 00:02:11,100
The other way you can go is Scale‑Out File Server for application data, and

35
00:02:11,100 --> 00:02:14,890
there I had mentioned this is a great home for highly available Hyper‑V

36
00:02:14,890 --> 00:02:20,250
virtual machines. But, we shouldn't forget that SQL Server databases often

37
00:02:20,250 --> 00:02:27,000
will be homed on an SOFS file share as well. Just know those details for your exam, okay?