1
00:00:00,740 --> 00:00:04,140
Another common problem we have as Windows Server administrators,

2
00:00:04,140 --> 00:00:06,500
particularly when you're using failover clustering,

3
00:00:06,500 --> 00:00:09,710
is that you may find that in your clusters you're

4
00:00:09,710 --> 00:00:12,180
using highly available Hyper‑V VMs,

5
00:00:12,180 --> 00:00:16,360
and some of those VMs may suck up up too many resources,

6
00:00:16,360 --> 00:00:18,340
particularly in the storage subsystem.

7
00:00:18,340 --> 00:00:22,160
How can you provide quality of service, particularly in a cluster,

8
00:00:22,160 --> 00:00:24,720
particularly even more so when you have Hyper‑V,

9
00:00:24,720 --> 00:00:27,600
so that you're providing more equitable storage

10
00:00:27,600 --> 00:00:30,840
access on those virtual machines?

11
00:00:30,840 --> 00:00:35,490
Well, that's the setup for Storage Quality of Service, or Storage QoS.

12
00:00:35,490 --> 00:00:39,780
And this is a Windows feature that's used with Hyper‑V Scale‑Out File

13
00:00:39,780 --> 00:00:42,760
Server as a way to optimize your storage system.

14
00:00:42,760 --> 00:00:47,320
Now this requires that you're using CSV storage for your VMs,

15
00:00:47,320 --> 00:00:48,690
the Cluster Shared Volumes,

16
00:00:48,690 --> 00:00:52,340
and it basically allows you to granularly control the

17
00:00:52,340 --> 00:00:55,810
input/output operations per second that your clustered

18
00:00:55,810 --> 00:00:58,810
Hyper‑V VMs are consuming in those CSVs.

19
00:00:58,810 --> 00:01:00,980
And this would, at the end of the day,

20
00:01:00,980 --> 00:01:10,000
give you consistent access for those clustered VMs. That's really all we need to know about Storage QoS for the purpose of the exam.