Website under construction

Figure 2-62:
Single-thread processing versus parallel processing 
On top of this parallel execution, the algorithm for processing files has been redesigned using a new 
stream map structure and improved partial file optimization. This accommodates the scalability and 
performance to handle files up to the 1 TB size limit. Figure 2-63 shows how the mapping technology 
has changed to allow for better optimization overall on the volume. 

---

61 
CHAPTER 2 | Software-defined datacenter 
Figure 2-63:
Old mapping versus the new stream map structures in windows 2016 
Although Microsoft technically supported and provided guidance to use deduplicated volumes with 
DPM in Windows Server 2012 R2, now further improvements to ensure ease of configuration and 
support are included within Windows Server 2016. You can configure this directly in the Windows 
2016 GUI or via Windows PowerShell by using the Enable-DeDup cmdlet, but including the new 
Backup
attribute. 
Enable-DedupVolume -Volume  -UsageType Backup 
Another new great option is support for rolling cluster upgrade. You can begin the process of 
upgrading your cluster nodes to Windows Server 2016 and maintain the deduplication process in 
Windows 2012. Previously this was unsupported. During the migration to Windows 2016, all jobs will 
run in Windows 2012 mode. 
Finally, a minor update, but one still worth noting, is the availability of a Storage Management API 
(SMAPI) interface for use with System Center Virtual Machine Manager 2016. This makes it possible 
for you to set up storage deduplication and status reporting from within System Center Virtual 
Machine Manager 2016. 
Storage Quality of Service 
One of the “missing” features from previous editions of Windows Server was the ability to apply 
Quality of Service (QoS) policies in relation to storage traffic. This became a huge problem in 
virtualization estates; if you wanted to prioritize certain workloads and give them, for example, a 
guaranteed level of I/O operations per second (IOPS), you simply couldn’t do it. 
In Windows Server 2016, you can now enforce resource fairness or prioritization depending on the 
policies that you want to configure for your storage. The core usage of storage QoS will be focused 
around Hyper-V VMs deployed on either a SOFS or Hyper-V Cluster with Cluster Shared Volumes. 
Figure 2-64 demonstrates that we can create various policies and apply them to our different VMs, 
giving you the ability to have different service standards or prioritize business-critical workloads. 

---

62 
CHAPTER 2 | Software-defined datacenter