[Updated: May, 22nd, 2016]

Hello everyone,

In today’s demo, I’ll show you a very interesting new feature that was introduced in Windows Server 2016 Hyper-V Distributed storage QoS.

If you remember, check in Windows Server 2012 R2, Microsoft added Storage QoS feature support for a virtual machine where you can go in and set the minimum or maximum cover for a virtual disk and prevent it from chewing all IOPs on the system.

• Minimum IOPS / VHD / X: not mandatory and not guaranteed, it is for information only!
• Maximum IOPS / VHD / X: maximizes storage performance.

That was great! but that wasn’t enough, Microsoft is investing more and more in this area for more functionality.

Recording QoS has a couple of big challenges today Windows Server 2012 R2.

The first is, ok, we have this technology that allows us to go in and say that you know this virtual machine will cap this number of IOPs and the second with the VM with this number, and that everything works fine on one Hyper-V server!

But honestly, no one takes a separate Hyper-V host into production, of course we take advantage of the Hyper-V cluster for high availability.

Storage QoS today will not work properly if you have a dozen Hyper-V servers are chatting with shared storage, because in Windows Server 2012 R2 these Hyper-V servers are not aware that they compete with each other for storage bandwidth.

Fortunately, in the next release of Windows Server, Microsoft introduced Distributed Storage QoS Policy Management, which was directly attached to Scale Out File Server as a cluster resource.

HV-vNext-DistStorageQoS-01

Of course, we still have what we had in Windows Server 2012 R2 that you can go to Hyper-V and go to the virtual machine settings and configure the Storage QoS features for each virtual hard disk, bIn the technical preview, we can now move on to expanding the file server cluster and configuring Storage QoS policies there, and this allows for a few really interesting scenarios:

1- The first scenario if you have a multiple Hyper-V Servers that chat with the same file server will respect all storage QoS policies.

2 – The second scenario allows us to really do some really cool things where we can now start applying Storage QoS policies and that we have one policy that applies to multiple virtual hard disks / virtual machines instead of just one virtual machine or one virtual hard disk.

Note: One important point that mentions that Windows Server 2016 Distributed Storage QoS also works in SOFS deployment and Clustered Shared Volume (CSV).

So rather switch without my demo system and show how distributed storage QoS works Mouth to mouth

Update: In Windows Server 2016 Technical Preview 5, the names of the Storage QoS Policy types are renamed. Multiple instances the policy is renamed Dedicated and Once was renamed Collected. Also change the management behavior of dedicated policies – VHD (X) files on the same virtual machine with the same Dedicated the policy applied to them does not share I / O allocations.

I hope you enjoyed the presentation and would like to thank you for watching.

Cheers,
/ Charbel

LEAVE A REPLY

Please enter your comment!
Please enter your name here