1
00:00:00,940 --> 00:00:03,000
What about Storage Spaces Direct?

2
00:00:03,000 --> 00:00:06,220
I give you the citation for this image in the lower left

3
00:00:06,220 --> 00:00:08,690
corner, and, of course, you've always got the Pluralsight

4
00:00:08,690 --> 00:00:10,910
exercise files to fall back on.

5
00:00:10,910 --> 00:00:14,340
But as I was saying, when you're using Storage Spaces in the

6
00:00:14,340 --> 00:00:18,010
context of a Windows Server failover cluster, that failover

7
00:00:18,010 --> 00:00:21,460
cluster is reliant upon shared storage.

8
00:00:21,460 --> 00:00:27,810
And so you can create a virtual storage pool that aggregates physical disks

9
00:00:27,810 --> 00:00:31,800
from some or all of the cluster nodes in your cluster.

10
00:00:31,800 --> 00:00:36,130
And the way the vocab works, the object model with Storage Spaces,

11
00:00:36,130 --> 00:00:37,800
is that you create your storage pool,

12
00:00:37,800 --> 00:00:41,380
which is an aggregation of physical disks, and then from that

13
00:00:41,380 --> 00:00:44,640
storage pool you start to break out virtual disks.

14
00:00:44,640 --> 00:00:47,560
And lastly, when you're doing Storage Spaces Direct,

15
00:00:47,560 --> 00:00:52,100
you can make sure that those virtual disks are replicated to each cluster

16
00:00:52,100 --> 00:00:57,700
node as VHD or VHDX files, and those cluster shared volumes, as they're

17
00:00:57,700 --> 00:01:00,480
called, will be on the file system of each node.

18
00:01:00,480 --> 00:01:01,030
And again,

19
00:01:01,030 --> 00:01:06,120
this makes that attachment and detachment process much faster when you

20
00:01:06,120 --> 00:01:11,240
need to move a workload from one primary node to another one because

21
00:01:11,240 --> 00:01:15,840
that secondary node that's going to take over already has a synchronized

22
00:01:15,840 --> 00:01:17,900
copy of that virtual disk volume.

23
00:01:17,900 --> 00:01:22,100
So this comes into play with workloads like Scale‑Out File Server where

24
00:01:22,100 --> 00:01:31,000
you've got highly available file shares, and that actually, SOFS, can be combined with highly available Hyper‑V virtual machines.

