table of contents€¦ · web viewwindows server 2012 r2 supports two vdi deployment scenarios,...

Large scale Virtual Desktop Infrastructure deployment using Windows Server 2012 R2 with Storage Tiers and Data

Deduplication

Abstract:This whitepaper explains a large-scale deployment of personal virtual machines that uses a combination of Storage Spaces and Data Deduplication in Windows Server 2012 R2. Performance comparisons are included to help customers make appropriate cost benefit analysis about enabling Data Deduplication, which can save storage costs.

Authors:Sriprasad Bhat KasargodPaul Despe

Published: December 2014

Updated:December 2015: Adds information for supported hyper-converged configuration (John Loveall)

Copyright informationThis document is provided “as-is.” Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it.

This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.

© 2015 Microsoft Corporation. All rights reserved.

Microsoft, Windows, Windows Server, Hyper-V are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Table of ContentsTable of Contents........................................................................................................................................3

Executive summary.....................................................................................................................................5

Objectives................................................................................................................................................5

Target audience.......................................................................................................................................6

Technology overview...................................................................................................................................7

Microsoft Virtual Desktop Infrastructure.................................................................................................7

Hyper-V over SMB Scale-Out File Server.................................................................................................7

Storage Spaces.........................................................................................................................................8

Data Deduplication for VDI workloads....................................................................................................8

How Data Deduplication works...........................................................................................................8

Why Scale-Out File Server for VDI workloads with Data Deduplication...............................................9

HyperV usage type for VDI workloads...............................................................................................10

Limited Hyper-Converged VDI Configuration with Local Storage..............................................................11

Large Scale Deployment Configuration with Storage Tiers........................................................................11

Network and switch topology................................................................................................................12

Compute cluster design considerations.................................................................................................13

Storage cluster design considerations...................................................................................................14

Deployment configuration.....................................................................................................................16

Storage classification.........................................................................................................................16

Data Deduplication configuration......................................................................................................19

Virtual machine configuration...........................................................................................................22

Virtual Desktop Infrastructure configuration.....................................................................................22

Test strategy..............................................................................................................................................23

Objectives..............................................................................................................................................23

Test tools...............................................................................................................................................23

Test setup..............................................................................................................................................23

Test workload........................................................................................................................................24

Test scenario..........................................................................................................................................25

Test preparation....................................................................................................................................25

Virtual desktop profile creation.........................................................................................................25

Storage Spaces Tier preparation........................................................................................................26

Data Deduplication preparation........................................................................................................26

Test stages.............................................................................................................................................27

Maintenance stage............................................................................................................................27

Measurement stage...........................................................................................................................27

Test Results...............................................................................................................................................29

Baseline runs without Data Deduplication............................................................................................29

1750 virtual machine test (VSIMax v4 = 1158 sessions and baseline 1663 milliseconds)..................29


Test runs with Data Deduplication enabled...........................................................................................30



Analysis..................................................................................................................................................31

Reduced storage configuration.................................................................................................................34

Conclusion.................................................................................................................................................37

Appendix...................................................................................................................................................38

Windows configuration.........................................................................................................................38

Storage configuration details.................................................................................................................38

Executive summaryA number of IT organizations are using Virtual Desktop Infrastructure (VDI) technology as a way to host their desktop operating systems. This technology enables IT administrators to solve typical challenges involved in desktop deployments, including data security, patch management, data recovery, and availability. Providing users with access to virtual desktops that are consolidated and managed from a centralized back-end infrastructure simplifies the overall administration of software and hardware. It also provides users with the ability to access their corporate desktop environment from a range of devices. Windows Server® 2012 R2 provides built-in functionality to host and manage VDI deployments.

This whitepaper explains a large-scale VDI deployment with virtual machines based on Hyper-V®. The virtual disks are deployed on a Scale-Out File Server cluster running Window Server 2012 R2 (with the latest updates). The deployment demonstrated that by using a combination of the Storage Spaces and Data Deduplication features in Windows Server 2012 R2, you can deliver a highly resilient solution with good performance and high savings rates for storage.

The solution uses industry standard servers and Serial Attached SCSI (SAS) just-a-bunch-of-disks (JBOD) storage enclosures. Performance comparisons include variations with Data Deduplication enabled to help customers make appropriate cost analyses about enabling Data Deduplication, which can save storage costs.

In the deployment discussed, the system was able to support 1500 virtual desktop users while maintaining adequate levels of performance. The deployment also demonstrates that the same number of users can be sustained with reduced storage when Data Deduplication is used. During the deployment, a number of configuration best practices were developed, and they are documented here.

In addition, this whitepaper also describes a limited configuration for using dedup on the locally mounted storage of a VDI server or server cluster. This “hyper-converged” configuration requires that the dedup processing be scheduled to run only when the VDI guests are idle, but does allow a VDI server to be configured without a separate file server.

ObjectivesThe main objectives for delivering this whitepaper are:

1. Identify best practices for deploying a large-scale personal virtual desktop solution with the virtual machines stored on a Windows Server 2012 R2 Scale-Out File Server cluster that uses Storage Spaces and shared JBOD storage enclosures.

2. Demonstrate the value of using Data Deduplication with the goal of reducing storage requirements per virtual machine-based desktop while maintaining acceptable performance.

3. Provide guidance about maintaining and monitoring such a deployment.4. Provide a description of a limited, “hyper-converged” VDI server that uses locally mounted

storage without a separate file server.

Target audienceThis white paper is intended for IT administrators who are involved in the planning and/or implementation of a large-scale VDI solution that uses Windows Server 2012 R2. Readers should be familiar with the general concepts of VDI in addition to the compute, storage, and networking requirements for such a deployment.

Technology overview

Microsoft Virtual Desktop Infrastructure Microsoft® Virtual Desktop Infrastructure (VDI) is powered by Windows Server 2012 R2. It empowers you to deploy architectures for Remote Desktop Services that provide employees with the flexibility to work anywhere and allow them to seamlessly access their corporate Windows® desktop or an application environment that is running in the datacenter. This access is possible from a range of devices.

VDI facilitates the optimal use of hardware by enabling access to multiple Windows environments (for example, development, test, business, or personal) from the same client device. It also enables organizations to pursue Bring Your Own Device (BYOD) programs for employees, in which they can use their personally owned hardware for personal needs and for work. This helps IT administrators keep the corporate environment secure even when it is accessed from unmanaged devices.

Windows Server 2012 R2 supports two VDI deployment scenarios, virtual desktop pools (shared among a set of users) and personal virtual desktops (assigned to a specific user). A personal virtual desktop is a dedicated virtual machine that is hosted on a Remote Desktop Virtualization Host. In a virtual desktop pool, a virtual machine can be configured to roll back the changes when a user signs out. A personal virtual desktop retains all changes made by the user, like a typical desktop computer would.

This whitepaper exclusively focuses on a personal desktop deployment.

For more information, see VDI - Operating System Virtualization

Hyper-V over SMB Scale-Out File ServerStorage has traditionally been the major hardware cost when hosting VDI. The requirement to host a large number of virtual machine images on a high performance, highly available storage solution has usually meant depending on expensive enterprise storage area networks (SANs) with iSCSI or Fiber Channel.

A Scale-Out File Server built with Windows Server 2012 R2 is designed to provide file shares that are continuously available for Hyper-V workloads. A Scale-Out File Server cluster utilizes shared Storage Spaces and can provide resiliency and performance similar to a SAN, while using inexpensive JBOD storage enclosures.

The Scale-Out File Server role provides a continuously available Server Message Block (SMB) service. It also provides a mechanism for clustered file servers in an active-active configuration to aggregate bandwidth across the cluster. The I/O operations for SMB clients are transparently directed by their owner node to achieve clustered load balancing.

For more information, see Cost-effective storage for Hyper-V workloads by using Windows Server

http://technet.microsoft.com/en-us/library/dn554251.aspx

http://www.microsoft.com/en-us/windows/enterprise/products-and-technologies/virtualization/operating-system/default.aspx

Storage Spaces Storage Spaces in Windows Server 2012 R2 includes features such as write-back cache, solid-state drive (SSD) and hard disk drive (HDD) storage tiers, trim, resiliency, and continuous availability with commodity hardware. It gives you the ability to consolidate all of your SAS-connected disks into storage pools. Storage Spaces are compatible with other Windows Server 2012 R2 storage features, including SMB Direct and Failover Clustering. This enables IT administrators to use industry-standard hardware to create powerful and resilient storage infrastructures on a limited budget and to supply high-performance and feature-rich storage to servers, clusters, and applications.

For more information, see Storage Spaces Overview

Data Deduplication for VDI workloadsData Deduplication support for running VDI workloads is a new feature in Window Server 2012 R2. Virtual machine hard disk files (.vhd and .vhdx) have large amounts of common data that can be deduplicated very well. Virtual machines hosted on a remote Scale-Out File Server file share over SMB 3.0 allows large numbers of VDI images to be efficiently stored on deduplicated volumes. Thereby, it provides a way to achieve very high virtual machine densities while maintaining performance.

How Data Deduplication works

Data deduplication involves finding and removing duplication within data without compromising its reliability or integrity. Data Deduplication optimizes files as a post processing operation. As data is added over the course of a day, it is not optimized immediately, and it takes up space on a disk. This new data is processed by a periodic background job.

The Data Deduplication optimization job chunks the file into small variable sizes (32–128 KB), identifies duplicate chunks, and maintains a single compressed copy of each chunk in special container files the “chunk store.” The chunk store is located under the System Volume Information folder on the volume. Any chunk that is referenced more than the threshold configured, is copied and stored in special “hotspot” container files for increased redundancy. The data in the primary data stream of the file is truncated and a reparse point is applied on the file stub. The reparse point that is specific to Data Deduplication contains enough information to reconstruct the file data.

Data access to these files is handled by the Data Deduplication filter driver, which performs the necessary operations to serve I/O on such files. Any I/O on deduplicated files is served from the chunk store or from the primary data stream of the file or a combination of both (depending on where the data resides, which is tracked reliably by the Data Deduplication filter driver). All data residing in the chunk store is protected by using strong metadata checksums, and every access validates the integrity of the data being delivered. Any inconsistency that is detected during data access (most commonly due to underlying disk issues) is logged and treated as an I/O failure. If the underlying volume is based on Storage Spaces, an attempt is made to retrieve the correct data from redundant copies.

http://technet.microsoft.com/en-us/library/hh831739.aspx

When data is deleted or when data is no longer referenced, it is not immediately removed during the I/O operation. Rather, a periodic schedule (weekly by default) runs a garbage collection job. This job iterates on data that has been deleted or is no longer referenced, and it removes such data from the chunk store.

A periodic schedule (weekly by default) runs a scrubbing job. This job iterates through any detected inconsistencies, logs them in the event logs, and tries to repair them if possible. This repair is made possible due to redundant copies provided by Storage Spaces or through redundant chunks that are maintained in dedicated hotspot container files in the chunk store.

For more information, see Introduction to Data Deduplication and Data Deduplication Overview

Why Scale-Out File Server for VDI workloads with Data Deduplication

Due to its nature, Data Deduplication consumes system resources such as storage, processor, and memory when running its jobs and when serving data during I/O on deduplicated files. As such, when extending Data Deduplication for VDI workloads in Windows Server 2012 R2, the compute and storage pieces of the deployment are separated and Data Deduplication is deployed on the Scale-Out File Server cluster nodes. This ensures that the virtual machines running on the Hyper-V hosts are not impacted by the overhead imposed by Data Deduplication.

The main advantages of such a deployment include:

1. By scaling up the number of deduplicated volumes as a multiple of the number of cluster nodes, we have the ability to run multiple Data Deduplication jobs in parallel, distributed across cluster nodes. Data Deduplication jobs on a Cluster Shared Volume always run on the node that owns the volume.

2. By distributing the I/O across multiple nodes of the cluster, resources (such as memory and compute hours) are efficiently utilized in parallel across cluster nodes.

3. By separating the storage from the compute, Data Deduplication subsystem can optimize I/O coming over SMB by using efficient caching mechanisms and spread the load across the cluster nodes.

While the use of a separate, Scale-Out File Server is the primary configuration supported for VDI workloads with Data Deduplication, there are limited configurations supported for the use of local storage on the same server(s) that run the VDI workloads. This “hyper-converged” configuration can be useful, for example, when external SAN storage is to be used or when smaller deployments would benefit from the costs/admin savings of using a simpler hardware configuration. The hyper-converged configuration must adhere to specific requirements for scheduling the dedup and VDI workloads separately to avoid potential resource and/or priority conflicts from affecting system performance. See the section “Limited Hyper-Converged VDI Configuration with Local Storage” below for the detailed requirements of this configuration.

For more information, see Scale-Out File Server for Application Data Overview



http://blogs.technet.com/b/filecab/archive/2012/05/21/introduction-to-data-deduplication-in-windows-server-2012.aspx

HyperV usage type for VDI workloads

The HyperV usage type for Data Deduplication was introduced as part of Windows Server 2012 R2 for supporting VDI workloads. Enabling Data Deduplication on a volume with this usage type sets several low-level settings to defaults that are appropriate for the VDI workload. These settings include:

1. Enabling “Open File Optimization,” which allows Data Deduplication jobs to process virtual disk files while they are in use by the server running Hyper-V.

2. Enabling “Partial File Optimization,” which allows the Data Deduplication jobs to set up USN range tracking on the volume and not reoptimize recently accessed hot data within a file.

3. Setting the “MinimumFileAgeDays” parameter so that the days signify the number of days needed to elapse before a range is considered cold.

4. Setting up the file extension exclusion list to exclude Hyper-V metadata files from being processed by Data Deduplication jobs.

5. Optimizing the internal behavior of the Data Deduplication subsystem for optimizing I/O over SMB. Frequently used common data chunks are cached in the Data Deduplication filter and in the cache manager.

For more information, see Extending Data Deduplication to new workloads in Windows Server 2012 R2 and Deploying Data Deduplication for VDI storage in Windows Server 2012 R2

Limited Hyper-Converged VDI Configuration with Local StorageThe configuration of enabling Windows Server Data Deduplication on data volumes directly mounted on a Hyper-V compute server (as opposed to mounted from a shared folder hosted on a separate file server) is not supported in the general case. However, there is a useful, limited configuration that is supported as an exception. This configuration is designed to avoid the occurrence of priority and/or resource conflicts between the Hyper-V guest workloads and data deduplication host partition processing by using appropriate scheduling.

For this limited configuration, deduplication must be running in a supported scenario as defined in the TechNet article Plan to Deploy Data Deduplication. In particular, open VHD files used for accessing storage in guest virtual machines are only supported for VDI and virtualized backup scenarios.

For VDI deployments, this limited configuration consists of the following:

Hyper-V compute server or cluster dedicated to running VDI guest workloadso All server nodes are running Windows Server 2012 R2 with the November 2014 update

rollup for Windows Server 2012 R2 (KB 3000850) or later. Guest VHDs are stored in locally attached data volumes. In a cluster configuration the volumes

are mounted as Cluster Shared Volumes. Windows Server Data Deduplication is enabled on these locally attached data volumes. All deduplication tasks on a given server node are scheduled to run in a limited “idle”

timeframe when all VDI workloads are idle on that node.

http://support.microsoft.com/kb/3000850

https://technet.microsoft.com/en-us/library/hh831700.aspx

http://blogs.technet.com/b/filecab/archive/2013/07/31/deploying-data-deduplication-for-vdi-storage-in-windows-server-2012-r2.aspx

http://blogs.technet.com/b/filecab/archive/2013/07/31/extending-data-deduplication-to-new-workloads-in-windows-server-2012-r2.aspx

o It is not required to actively enforce a block on running VDI workloads during this scheduled time, but the system is required to be configured so that operation of is idle or paused during the scheduled dedup processing window.

Volume sizing and deduplication performance monitoring are done in accordance with the procedures defined in the article Sizing Volumes for Data Deduplication in Windows Server . o If deduplication processing is not able to keep up with the daily data churn, either the

“downtime” deduplication processing window must be extended or fewer simultaneous active VDI workloads must be configured on the node.

In addition to meeting the above requirements, the following steps are also strongly recommended:

Review the recommendations in the article Deduplication Tuning for Deployments with High Saving Rates. If the savings rates measured in the VDI deployment fall in the range covered in this article, adjust the deduplication settings as instructed.

In order to validate the VDI workload capacity of this limited configuration, run a load test using the supported VDI guest images. Tools such as LoginVSI or the equivalent should be used to directly validate the configuration prior to use in production.

An active Microsoft Service Premier Support contract is recommended to facilitate further communication, telemetry, and advice that can be useful when defining these configurations.

Large Scale Deployment Configuration with Storage TiersThe deployment was built around the following high-level design goals:

1. Support 1500 virtual desktop users, each with an assigned personal virtual desktop.2. Deploy virtual desktops with storage classifications. Use a separate storage tier for data with

different performance characteristics.3. Maintain “N + 1” hardware resiliency, with the ability to withstand a single component failure in

the deployment.4. Use storage spaces with automated storage tiering, and deploy Data Deduplication to reduce

costs.

The following diagram describes the logical components of the deployment:

http://www.microsoft.com/en-us/microsoftservices/support.aspx

http://www.loginvsi.com/

http://social.technet.microsoft.com/wiki/contents/articles/32049.deduplication-tuning-for-deployments-with-high-saving-rates.aspx

http://social.technet.microsoft.com/wiki/contents/articles/32049.deduplication-tuning-for-deployments-with-high-saving-rates.aspx

http://blogs.technet.com/b/filecab/archive/2014/12/04/sizing-volumes-for-data-deduplication-in-windows-server.aspx

Network and switch topologyThe main goal for the network topology was to separate the network traffic into three types:

1. Management network for host management2. Tenant network for communication between the tenant virtual machines and VDI.3. Storage network for handling SMB 3.0 traffic between the cluster nodes in Hyper-V and the

Scale-Out File Server nodes

The following diagram describes the network topology the deployment:

Compute cluster design considerationsHere are the design considerations for the compute cluster redundancy and performance:

Server fault tolerance and improved performance

Solution: Clustered configuration with virtual machines distributed across the nodes with enough free capacity to withstand node failures. This also implies that the workload can be distributed across the cluster.

Network fault tolerance and improved throughput

Solution: Fully redundant dual paths on the storage network from each cluster node in Hyper-V to each Scale-Out File Server node, including redundant switches on separate subnets for using SMB Multichannel.

Solution: Fully redundant dual paths on the tenant network, including redundant switches on separate subnets for using NIC Teaming.

The specific compute cluster that we tested was a 15-node Hyper-V cluster with each node comprised of a Dell PowerEdge R720 server with the following configuration:

http://www.dell.com/us/business/p/poweredge-r720/pd

Processor:

2 x Intel(R) Xeon(R) CPU E5-2660 0 @ 2.20 GHz, 2200 MHz, 8 Cores, 16 logical processors

Memory:

192 GB

Networks:

Tenant network: 2 x 10 Gbps (Broadcom BCM5780 NetXtreme II 10 GigE) with NIC Teaming Storage network: 2 x 10 Gbps RDMA (Chelsio) with SMB Multichannel Management network: 2 x 1 Gbps (Broadcom BCM5780 NetXtreme II 1 GigE)

Storage cluster design considerationsHere are the design considerations for the storage cluster:

Redundancy and performance

Server fault tolerance and improved performance

Solution: Clustered configuration with the number of Cluster Shared Volumes (CSV) hosting the file shares scaled with cluster nodes so as to tolerate node failures. By keeping the number of CSVs and file shares a multiple of the number of cluster nodes, the workload can be evenly distributed across the cluster.

Network fault tolerance and improved throughput

Solution: Fully redundant dual paths on the storage network from each Scale-Out File Server node to cluster nodes in Hyper-V, including redundant switches on separate subnets to use SMB Multichannel.

Ability to withstand a single storage component failure

Solution: Fully redundant dual paths from each file server node to each storage device.

Ability to withstand a single physical disk failure with redundant data copies

Solution: Utilize two-way mirror virtual disks in Storage Spaces. Mirroring is designed to increase performance and resiliency by placing multiple (in this case two) copies of the data on separate physical disks. Data Deduplication takes advantage of this by validating the data integrity of its metadata and failing over to use the redundant copy if there are integrity issues with the data returned from the first copy.

Ability to withstand a single storage enclosure failure.

Solution: Create virtual disks with enclosure awareness enabled, so that Storage Spaces can associate each copy of data with a particular JBOD enclosure. This way, if one enclosure fails or goes offline, the data remains available in one or more alternate enclosures.

Recovery from failure

Ability to failover between cluster nodes quickly.

Solution: Use two storage pools, keeping the number of disks per clustered storage pool to fewer than the recommended limit of 80 disks per pool. This also allows us to plan for isolating spindles for dedicated workloads, if necessary. (For example, the ability to separate virtual desktops based on SLAs).

Performance

Achieve optimal storage I/O performance

Solution: Align I/O block sizes along the entire storage stack. Use 64 KB for the virtual disk interleave and the NTFS cluster allocation unit size. This aligns with the sparse file compression unit size because all deduplicated files are inherently sparse in nature.

Efficiently utilize faster storage

Solution: Use storage tiers to utilize faster SSDs. Size the SSD tier depending on the frequently accessed hot working set, so as to hold most (if not all) of the hot data.

Efficiently utilize write-back cache

Solution: Storage Spaces can use existing SSDs in the storage pool to create a write-back cache that is tolerant of power failures and that stages small random writes to SSDs and later writing them to hard disk drives efficiently. The optimal and recommended size of the write-back cache is currently 1 GB per virtual disk.

Reduce the impact of frequent writes to the page file in the guest operating system

Solution: In virtual desktops, the area of the disk where the page file is located can be the target of heavy write activity, which is demanding in terms of performance. Separating this data by transferring the page file to a separate virtual hard drive (VHD) and storing such VHDs on a separate storage tier with faster storage can benefit performance inside the operating system.

Reduce the time required to optimize the deduplicated dataset

Solution: A Data Deduplication optimization job is single threaded in nature, and it can significantly benefit by splitting the dataset across multiple volumes so that the processing can run in parallel. In our deployment, we use six virtual disks (three disks across two pools).

Capacity

Reduce storage capacity needed to host duplicate, cold, read-only data that is spread across operating system VHDs

Solution: Deploy Data Deduplication on the storage volumes to reduce storage capacity requirements.

Reliability

Reduce impact of file fragmentation due to Data Deduplication

Solution: Due to the nature of the implementation, Data Deduplication can cause fragmentation of data in the NTFS file system. To reduce the impact, NTFS is formatted to use a large file record segment to better handle fragmentation limits.

For more information, see Storage Spaces Frequently Asked Questions (FAQ)

The storage capacity for the solution was deployed by using a three node Scale-Out File Server cluster with each node comprised of a Dell PowerEdge R620 server with the following configuration:

Processor:

2 x Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90 GHz, 2900 MHz, 8 cores, 16 logical processors

Memory:

128 GB

Network:

Storage network: 2 x 10 Gbps RDMA (Chelsio) with SMB Multichannel Management network: 2 x 1 Gbps (Broadcom BCM5780 NetXtreme II 1 GigE)

Storage:

2 x LSI SAS9207-8E adapters per node 4 x Dell MD306e (60 disk capacity, and we used 27 disks per JBOD)

16 HDDs per JBOD (2.73 TB, Seagate ST33000650SS 7.2K SAS) 8 SSDs per JBOD (186 GB, Toshiba MK2001GRZB) 3 SSDs per JBOD (372 GB, Pliant LB406M)

Deployment configuration

Storage classification

Storage for the virtual hard disks that belong to the virtual desktops was partitioned and classified based on the performance characteristic of the workload. This includes separate file shares for page file data and operating system data. For this deployment, it was assumed that the user data would be handled separately. The storage was classified into two groups as follows:

Virtual machine operating system VHD storage:

2 storage pools, each using 8 x 2.73TB HDDs and 4 x 186GB SSDs from each enclosure (a total of 32 HDDs and 16 SSDs per pool)

6 tiered virtual disks, 3 per pool 10 TB in size (9.53 TB HDD tier and 480 GB SSD tier) 1 GB write-back cache

http://www.dell.com/us/business/p/poweredge-r620/pd

http://social.technet.microsoft.com/wiki/contents/articles/11382.storage-spaces-frequently-asked-questions-faq.aspx

2-way mirror, 6 column count 64 KB interleave Enclosure aware

Each virtual disk configured as a Cluster Shared Volume that hosts a file share NTFS formatted with 64KB allocation unit size and large file record segment.

Virtual machine page file VHD storage:

1 storage pool, using 3 x 372GB SSD’s from each enclosure (Total 12 SSD’s) 3 virtual disks

676 GB in size 2-way mirror, 4 column count 64KB interleave Enclosure aware

Each virtual disk configured as a Cluster Shared Volume hosting a file share NTFS formatted with 64 KB allocation unit size

The following sample Windows PowerShell script shows how to set up this configuration for the operating system VHD storage:

# Get all eligible disksUpdate-StorageProviderCacheUpdate-HostStorageCache$PhysicalDisks = Get-PhysicalDisk | ? BusType -eq SAS | ? CanPool -eq $true | Sort-Object -Property PhysicalLocation

# Group HDD's by enclosure$HDDs = @()$PhysicalDisks | ? MediaType -eq HDD | ForEach-Object { $PhysicalLocation = $_.PhysicalLocation; $EnclosureId = $PhysicalLocation.Replace($PhysicalLocation.Substring($PhysicalLocation.IndexOf(" : ")), "").Replace("SES Enclosure ", ""); $Disk = New-Object System.Object; Add-Member -InputObject $Disk -Type NoteProperty -Name "EnclosureId" -Value $EnclosureId; Add-Member -InputObject $Disk -Type NoteProperty -Name "DiskObj" -Value $_; $HDDs += $Disk }$HDDsGroupedByEnclosure = $HDDs | Group-Object -Property EnclosureId

# Group SSD's by enclosure$SSDs = @()$PhysicalDisks | ? MediaType -eq SSD | ForEach-Object { $PhysicalLocation = $_.PhysicalLocation; $EnclosureId = $PhysicalLocation.Replace($PhysicalLocation.Substring($PhysicalLocation.IndexOf(" : ")), "").Replace("SES Enclosure ", ""); $Disk = New-Object System.Object; Add-Member -InputObject $Disk -Type NoteProperty -Name "EnclosureId" -Value $EnclosureId; Add-Member -InputObject $Disk -Type NoteProperty -Name "DiskObj" -Value $_; $SSDs += $Disk }$SSDsGroupedByEnclosure = $SSDs | Group-Object -Property EnclosureId

# Select disks equally from all enclosures$NumEnclosures = 4$NumHDDsPerEnclosure = 8$NumSSDsPerEnclosure = 4

$TieredPool1HDDs = @()$TieredPool1SSDs = @()$TieredPool2HDDs = @()$TieredPool2SSDs = @()for ($Idx = 0; $Idx -lt $NumEnclosures; $Idx++){ $TieredPool1HDDs += $HDDsGroupedByEnclosure[$Idx].Group.DiskObj[0..((1 * $NumHDDsPerEnclosure) - 1)] $TieredPool1SSDs += $SSDsGroupedByEnclosure[$Idx].Group.DiskObj[0..((1 * $NumSSDsPerEnclosure) - 1)]

$TieredPool2HDDs += $HDDsGroupedByEnclosure[$Idx].Group.DiskObj[(1 * $NumHDDsPerEnclosure)..((2 * $NumHDDsPerEnclosure) - 1)] $TieredPool2SSDs += $SSDsGroupedByEnclosure[$Idx].Group.DiskObj[(1 * $NumSSDsPerEnclosure)..((2 * $NumSSDsPerEnclosure) - 1)]}

# Create poolsNew-StoragePool -FriendlyName TieredPool1 -PhysicalDisks $TieredPool1HDDs -StorageSubSystemFriendlyName "*Clustered Storage Spaces*"Add-PhysicalDisk -StoragePoolFriendlyName TieredPool1 -PhysicalDisks $TieredPool1SSDsNew-StoragePool -FriendlyName TieredPool2 -PhysicalDisks $TieredPool2HDDs -StorageSubSystemFriendlyName "*Clustered Storage Spaces*"Add-PhysicalDisk -StoragePoolFriendlyName TieredPool2 -PhysicalDisks $TieredPool2SSDs

# Create tenant disks$HDDTierSize = (9760GB)$SSDTierSize = (480GB)

# Create virtual disks and create CSV's$NumberOfPools = 2$NumberOfDisksPerPool = 3for ($Idx = 0; $Idx -lt $NumberOfPools; $Idx++){ $StoragePoolName = "TieredPool" + ($Idx + 1) $HDDTier = New-StorageTier -FriendlyName HDDTier -StoragePoolFriendlyName $StoragePoolName -MediaType HDD $SSDTier = New-StorageTier -FriendlyName SSDTier -StoragePoolFriendlyName $StoragePoolName -MediaType SSD

for ($Jdx = 0; $Jdx -lt $NumberOfDisksPerPool; $Jdx++) { $VirtualDiskName = "TieredDisk" + (($Idx * $NumberOfDisksPerPool) + ($Jdx + 1)) $VirtualDisk = New-VirtualDisk -StoragePoolFriendlyName $StoragePoolName -FriendlyName $VirtualDiskName -StorageTiers @($HDDTier,$SSDTier) -StorageTierSizes @($HDDTierSize,$SSDTierSize) -ResiliencySettingName Mirror -NumberOfDataCopies 2 -Interleave 64KB -NumberOfColumns 6 -AutoWriteCacheSize -IsEnclosureAware $true

Move-ClusterGroup -Name "Available Storage" -Node $env:COMPUTERNAME $ClusterDiskResource = Get-ClusterResource | ? { $_.Name -match $VirtualDisk.FriendlyName } Suspend-ClusterResource -InputObject $ClusterDiskResource

$Disk = Get-Disk -VirtualDisk $VirtualDisk $Partition = New-Partition -InputObject $Disk -UseMaximumSize $Volume = Format-Volume -Partition $Partition -FileSystem NTFS -AllocationUnitSize 64KB –UseLargeFRS -Force -Confirm:$false

Resume-ClusterResource -InputObject $ClusterDiskResource Add-ClusterSharedVolume -InputObject $ClusterDiskResource }}

Data Deduplication configuration

Each Scale-Out File Server node is configured by enabling Data Deduplication under the File and Storage Services role. Data Deduplication was enabled on each of the CSVs that host the operating system VHD file shares by setting the UsageType to HyperV.

The following sample Windows PowerShell script shows how to enable Data Deduplication with usage type of HyperV:

# Enable Dedup on volumes$NumberOfCSVs = 6for ($Idx = 1; $Idx -le $NumberOfCSVs; $Idx++){ $VolumePath = "C:\ClusterStorage\Volume" + $Idx Enable-DedupVolume -Volume $VolumePath -UsageType HyperV}

Data Deduplication creates default scheduled tasks for running jobs. The default schedules created are as follows:

Background optimization: Attempts to run the Data Deduplication optimization job every hour in a background mode. This job uses low system resources and is configured to stop when the system is busy.

Weekly garbage collection: Attempts to run the Data Deduplication garbage collection job every week during the weekend, in order to cleanup unreferenced data and metadata from the Data Deduplication chunk store.

Weekly scrubbing: Attempts to run the Data Deduplication scrubbing job every week during the weekend, in order to detect any inconsistencies in the Data Deduplication chunk store and repair if and when possible.

For VDI workloads, we can either utilize the default schedules or disable them and create custom schedules depending on the requirements. In our deployment we disabled the default schedules so that they would not interfere with our benchmark tests and to keep the state as stable and reproducible as possible.

On a production deployment, one possible option is to disable the default background optimization schedule so as to not impact the primary workload when the system is under use, and create a custom daily schedule to optimize data in the normal mode (also known as throughput mode) during maintenance hours or when the system is under reduced load.

Best practice: Ensure that the Data Deduplication schedules are setup correctly depending on the system load and requirements to either run the default hourly background optimization schedule or a custom optimization schedule during daily maintenance window.

Ensuring that the right amount of the working set is retained on the disk is critical to efficient utilization of the faster tier. Under optimal conditions, the frequently accessed data is considered hot by Data Deduplication, depending on the MinimumFileAgeDays policy setting (the default value is 3 days). With OptimizePartialFiles policy setting enabled (This is enabled by default when the UsageType is set to HyperV), the MinimumFileAgeDays policy setting for a deduplicated volume determines which regions of files on that volume are hot retains these regions on the primary data stream of the file. Storage Spaces would also consider most of these regions as hot, and move them into the faster tier, thereby speeding up access to this data.

If the MinimumFileAgeDays policy setting for a deduplicated volume is set to a very small value or zero, this can cause hot data to be optimized and move between the faster tier to the chunk store and back. A small value can also cause all hot data to be considered cold when the deployment is left idle for more than this threshold. If the MinimumFileAgeDays policy setting for a deduplicated volume is set to a very large value, it will cause cold data to be considered hot, thereby wasting precious space on the faster tier until it is ejected during the Storage Spaces Tier optimization job.

The default value of 3 days for the MinimumFileAgeDays policy setting is sufficient for most purposes; however, it is critical to adjust this number based on the actual workload pattern. The most effective method is to monitor the change in file size on disk over a period of several days, and adjust the policy to retain the right working set for the disk.

Best practice: Ensure that the MinimumFileAgeDays policy setting for Data Deduplication-enabled volumes is set to an appropriate number, depending on how frequently the working set is accessed.

The Data Deduplication filter uses its internal caching mechanism in addition to the system cache when serving read I/O in regions of the deduplicated files that are fully optimized. However, regions of the file may have been recalled due to prior writes to the region or due to the region being hot. In this situation, the I/O on recalled regions bypasses the Data Deduplication filter, and it is served by NTFS. It is critical that such data be on the faster tier because it does not benefit from caching.

Due to access patterns by the Data Deduplication jobs and by the Data Deduplication filter while serving I/O, the Data Deduplication chunk store data may end up on the faster tier. However due to internal caching mechanisms, this data does not benefit from residing on the faster tier, except while populating the cache during a cold start after a system restart or long idle times. It is beneficial to move the Data Deduplication chunk store files out of the faster SSD tier to free up this precious space for user data

working set. This is achieved by creating a scheduled task that runs before the nightly Storage Spaces Tier optimization scheduled task. This custom task enumerates all files in the Data Deduplication chunk store and pins the metadata files to the slower HDD tier.

Although there are multiple ways to do this, the following method is provided as a sample:

1. Create custom scripts per volume on all nodes, for example, C:\ddppinscripts\pincsv1.ps1.$VolumeName = "C:\ClusterStorage\Volume1"$HDDTierName = "TieredDisk1_HDDTier"

$ClusterSharedVolume = Get-ClusterSharedVolume | Where-Object { $_.SharedVolumeInfo.FriendlyVolumeName -eq $VolumeName }if ($ClusterSharedVolume.OwnerNode -eq $env:COMPUTERNAME){ $DedupCSPath = $VolumeName + "\System Volume Information\Dedup" Get-ChildItem -Path $DedupCSPath -Recurse -File -Force | ForEach-Object { try { Set-FileStorageTier -FilePath $_.FullName -DesiredStorageTierFriendlyName $HDDTierName } catch {} }}

2. Create a scheduled task as SYSTEM on all nodes to run the scripts every night at 12:00 AM—an hour before the nightly Storage Spaces Tier optimization scheduled task.$PinTaskAction = New-ScheduledTaskAction -Execute "powershell.exe" -Argument "-file C:\ddppinscripts\pincsv1.ps1"

$PinTaskTrigger = New-ScheduledTaskTrigger -Daily -At 12AM -RandomDelay (New-TimeSpan -Minutes 15)

$PinTaskSettingsSet = New-ScheduledTaskSettingsSet -Compatibility Win8 -Priority 10 -StartWhenAvailable

Register-ScheduledTask -TaskName "Pin Dedup Metadata - CSV1" -TaskPath "\Microsoft\Windows\Storage Tiers Management" -Action $PinTaskAction -User "SYSTEM" -RunLevel Highest -Trigger $PinTaskTrigger -Settings $PinTaskSettingsSet

Best practice: Ensure that Data Deduplication metadata files in the chunk store are pinned to the slower tier. Follow this with the Storage Spaces Tier optimization job to move the Data Deduplication chunk store to the slower tier, freeing space in the faster tier for recalled user data.

Virtual machine configuration

To simulate customer scenarios, Windows 7 SP1 (with the latest updates) was used as the guest operating system. For compatibility with the VDI solution in Windows Server 2012 R2, the tenant virtual

machine was configured as a generation 1 virtual machine. The virtual machine template was set with two virtual processors, and it was configured to use dynamic memory with a minimum of 1 GB RAM allocated for startup and maximum limits set to 1.5 GB.

All the tenant virtual machines were deployed by using Microsoft System Center Virtual Machine Manager 2012 R2 (SCVMM). The virtual machine template was set to use two virtual hard disks. The guest operating system was configured to create a page file on an additional disk that is dedicated for this purpose. The page file data was separated from the base operating system data for the following reasons:

To allow better management of transient page file data for operations such as backup and replication.

To allow deployment of frequently accessed page file data to fast SSD storage. To allow exclusion of frequently accessed page file data from Data Deduplication, which avoids

expensive processing of easily invalidated data.

Each virtual machine was set up with typical information worker applications such as Microsoft Office, Internet Explorer, Adobe Reader, and FreeMind for test purposes, before finalizing the VHD templates. The operating system VHD template was compacted by using the Optimize-VHD Windows PowerShell cmdlet to reduce its overall size and reduce file copy overhead during deployment.

SCVMM was made aware of the storage and compute resources, and the file shares that were exposed by the Scale-Out File Server were configured with the appropriate classification. This allowed SCVMM to efficiently deploy a large number of virtual machines and distribute the virtual hard disks across the file shares according their classification.

For more information, see Administering System Center 2012 - Virtual Machine Manager

Virtual Desktop Infrastructure configuration

The Remote Desktop Services components such as the Remote Desktop Connection Broker was set up on a dedicated server by using the deployment tools that are included in Windows Server 2012 R2. All the tenant virtual machines, which were deployed earlier, were registered with the Connection Broker as part of a Personal Desktop collection. The collection was created as an unmanaged collection to allow the flexibility of assigning user accounts to specific personal desktops for ease of testing.

For more information, see Remote Desktop Services Overview


http://technet.microsoft.com/en-us/library/gg610615.aspx


Test strategy

ObjectivesThe main test objectives were:

Develop best practices for deploying a large-scale VDI deployment to support around 1500 personal virtual desktops.

Determine how many virtual desktops can be realistically hosted by the deployed configuration with and without Data Deduplication, while maintaining an acceptable experience for the virtual desktop users.

Test toolsTo simulate a real-world information worker workload and to measure user response indicators during the test, we used Login VSI v4.0.11. Login VSI is an industry standard benchmark and load test tool for virtual desktop environments, which allowed us to:

Simulate a real-world information worker workload on the deployment and simulate typical usage scenarios associated with such a workload (such as the typical 9:00 A.M. boot storm)

Determine the maximum virtual desktop user capacity that is supported by the deployment. Understand the performance of the system from a user point-of-view. Analyze the impact of introducing a change in the system (for example, enabling Data

Deduplication).

For more information, see Login VSI – Performance Testing

Test setupThe test deployment was made up of the following components:

VSI manager

Virtual machine running Windows Server 2012 R2 with 4 GB memory and 4 virtual processors This machine was dedicated to hosting the following Login VSI components:

Login VSI Management Console Login VSI Session Monitor Login VSI Analyzer Login VSI Share (binary and log share)

VSI launcher

60 virtual machines running Windows 7 SP1 with 4 GB memory and 4 virtual processors

http://www.loginvsi.com/

These machines initiate RDP sessions to the target virtual machines.

VSI target

2000 tenant virtual machines running Windows 7 SP1 with dynamic memory (1 GB minimum) and 2 virtual processors

Each virtual machine is configured to run the Login VSI target and typical information worker applications to simulate the user workload.

VSI data server and web server

16 dedicated machines hosting the VSI data and web servers To handle the large I/O load on these machines, the volumes that contain the data were

enabled with the default Data Deduplication workload and optimized to use Data Deduplication caching. They were set up to serve the requests from memory rather than from disks, thereby speeding up access and avoiding a bottleneck during test runs.

For more information, see Login VSI logical set-up

Test workloadDuring a Login VSI test, the workload that runs inside a virtual machine is generated by using industry standard information worker applications. During each test, the Login VSI software measures the response time for each activity that it runs. The point when the response time of a user's actions inside the virtual machine goes beyond the defined threshold is called as VSIMax. The number of virtual machines running at this point are logged as the maximum number of virtual desktops that are supported for that setup.

The medium workload is the default workload in Login VSI. This workload emulates a knowledge worker who is using Microsoft Office, Internet Explorer, Adobe Reader, and FreeMind, and 7-Zip. Login VSI assumes the following:

When a session has been started, the workload repeats (loops) every 48 minutes. The loop is divided into four segments, each consecutive user sign-in starts a different segment.

This ensures that all elements in the workload are equally used throughout the test. During each loop, the response time is measured every 3 4 minutes. The medium workload opens up to five applications simultaneously. The keyboard type rate is 160 milliseconds for each character. Approximately two minutes of idle time is included to simulate real-world users. Each loop opens and uses the following:

Microsoft Outlook to browse messages Microsoft Internet Explorer to browse websites and video (for example, a 480p movie

trailer). It is opened three times in every loop. Microsoft Word: One instance to measure response time and one instance to review

and edit a document Adobe Reader and Doro PDF Printer: A word document is printed and reviewed in PDF.

http://www.loginvsi.com/documentation/index.php?title=Login_VSI_logical_set-up

Microsoft Excel: A large, random spreadsheet is opened. Microsoft PowerPoint: A presentation is reviewed and edited. FreeMind (a Java-based mind mapping application) 7-Zip (a file archive tool with a high compression ratio)

For more information, see Login VSI Workloads

Test scenarioIn version 4, Login VSI introduced the Benchmark mode, which enforces strict testing standards. This provides industry standard results that are objective, comparable, and repeatable. This feature ensures that all vendors test with the same Login VSI settings applied to their environments, allowing for an easier comparison of whitepapers.

When using Benchmark Mode, the test runs for approximately 48 minutes. During this time, the test establishes a baseline of performance and then tests signing in to all virtual machines. This simulates a high sign-in rate scenario, where most users sign in to their dedicated virtual desktops within a short period of time, leading to the tenant virtual machines resumed from the saved state. This would in turn generate high I/O requests from the storage subsystem.

The goal of this scenario is to validate that the entire system can sustain the high sign-in rate while maintaining acceptable levels of performance.

Test preparationBefore starting the actual tests, we need to set up the system in a stable/steady state so that the performance measurement is predictable and repeatable. This can be done by properly aging the system. For our test purpose, we warmed up the test setup by simulating a week worth of churn by running dummy test cycles spread over seven days.

Virtual desktop profile creation

When a user signs in to a virtual desktop for the first time, the user profile is created. To keep the tests predictable, all virtual desktops under test had the profile created in advance and all the applications used by the test were properly initialized by launching a few dummy runs in Login VSI. This is a one-time task that can be done by launching a new test and checking the Profile Creation mode in the Test Configuration screen during the Start Test Wizard from the Login VSI management console.

Test best practice: Ensure that all test virtual desktops have been through the Login VSI profile creation stage at least once.

http://www.loginvsi.com/documentation/index.php?title=All_settings#Workloads

Storage Spaces Tier preparation

When the tenant virtual machines are initially deployed, the data is randomly distributed across the HDD and SSD tiers on the volumes. As the virtual machines go through multiple boot and test cycles, the Storage Spaces Tier subsystem gathers and stores heat data on areas of the VHD files that are more frequently accessed. When running the Storage Spaces Tier optimization job, the hot data is moved into the faster SSD tier and relatively cold data is moved into the slower HDD tier.

To ensure the best possible state performance, the storage tiers heat database must have enough information to ensure that all possible hot data is moved into the SSD tier during the Storage Spaces Tier optimization job. This can be verified by running multiple dummy tests with the virtual machines going through the shutdown/reboot, save/resume, and test phases and running the Storage Spaces Tier optimization job between each run until we reach a stable state. In our test deployment, we simulated a weeks’ worth of data by running dummy tests twice a day, followed by running a Storage Spaces Tier optimization job.

Test best practice: Ensure that all virtual desktops go through multiple dummy test passes so that the Storage Spaces Tier optimization job has enough information to move hot data into the faster tier.

In Login VSI, the VSIMax benchmark number depends on the number of virtual machines under test. If more than the maximum number of virtual desktops supported by the deployment are used, attempting to boot more can have a negative impact on the final VSIMax number. As such, it is imperative to attempt the tests with the correct number of virtual machines by starting with a high number of virtual machines and reducing the number till we hit the maximum possible VSIMax indicating the optimal number of virtual desktops supported by the deployment.

Technology such as storage tiers can have an influence on this. When running benchmark tests, only the virtual machines under test should occupy precious SSD space. This can be achieved by manually pinning any other data to the slower tier by using the Set-FileStorageTier Windows PowerShell cmdlet, followed by running a Storage Spaces Tier optimization job.

Test best practice: Ensure that only the virtual desktops under test occupy the faster SSD tier.

Data Deduplication preparation

As described earlier, to ensure the best possible performance, the maximum amount the hot data regions must be moved into the SSD tier. This can be done by running multiple dummy tests with the virtual machines going through the shutdown/reboot, save/resume, and test phases. This recalls the frequently accessed dataset to the primary data stream. The Data Deduplication optimization job is run between each phase, which retains the regions recently written to on the primary data stream of the file. This is followed by pinning any newly generated metadata files in the Data Deduplication chunk store to the slower HDD tier. This is followed by the Storage Spaces Tier optimization job which moves the recalled hot data into the faster SSD tier and the manually pinned Data Deduplication metadata files


into the slower HDD tier. In our test deployment, we simulated a weeks’ worth of data by running dummy tests twice a day, followed by running a Storage Spaces Tier optimization job.

Test best practice: Ensure that all virtual desktops go through multiple dummy test passes. After each test, run a Data Deduplication optimization job and then a Storage Spaces Tier optimization job to move hot data in deduplicated files into the faster tier.

Test stagesEach test run included a maintenance stage and a measurement stage.

Maintenance stage

This stage simulates the nightly activities that run daily for the deployment. Each test was set up to simulate a 9:00 A.M. condition in a typical workday. For our deployment we simulated a scenario where the default Data Deduplication optimization scheduled task was disabled and instead a custom scheduled task was created to run Data Deduplication optimization job in throughput mode at 7:00 P.M. In this case, the maintenance tasks involved:

1. Run the Data Deduplication optimization job in throughput mode.2. Pin the Data Deduplication chunk store to the slower HDD tier.3. Run the Storage Spaces Tier optimization job.

Test best practice: For test runs, disable the default Data Deduplication scheduled tasks so that they do not interfere with the benchmark runs. Instead simulate the daily/weekly maintenance tasks manually before the test run.

Measurement stage

Each test measurement consisted of the following steps:

1. Start all tenant virtual machines and wait for approximately 60 minutes until all boot-related I/O completes.

2. Save all tenant virtual machines.3. Start all Login VSI launcher machines and wait for them to enter the ready state.4. Start the Login VSI test per the test scenario.5. After the run completes and all the users are signed out, shutdown the tenant virtual machines.6. Use the Login VSI analyzer to find if VSIMax was reached.

a. If VSIMax was not reached, increase the number of virtual machines under test and repeat the test until the optimal VSIMax is reached.

b. If VSIMax was reached, but it is significantly lower than the number of virtual machines under test, reduce the number of virtual machines and repeat the test until the optimal VSIMax is reached.

Test best practice: For dummy runs, follow the same procedure as you will use for the actual test runs to ensure the deployment is in a stable state.

Test Results

Baseline runs without Data DeduplicationFor the baseline runs, we started with the full set of 2000 virtual machines with the Storage Spaces Tier preparation completed. Depending on the observed VSIMax, we reduced the number of virtual machines under test until the best possible VSIMax number was achieved. Before each run, we ensured that the virtual machines not under test were excluded from the SSD tier as described earlier.

1750 virtual machine test (VSIMax v4 = 1158 sessions and baseline 1663 milliseconds)


Test runs with Data Deduplication enabledFor the test runs, we started with a set of 1750 virtual machines with Data Deduplication and Storage Spaces Tier preparation completed. Depending on the observed VSIMax, we reduced the number of virtual machines under test until the best possible VSIMax number was achieved. Before each run, we ensured that the virtual machines not under test were excluded from the SSD tier as described earlier.


AnalysisBy plotting the VSI response times against the number of user sessions, we see that the results for the deduplicated dataset mirrors that of the baseline runs and is better in some cases.

50150

250350

450550

650750

850950

10501150

12501350

14501550

16500

1000

2000

3000

4000

5000

6000

7000

VSI Response Times (milliseconds)vs.

User Sessions

Non-Dedup 1750 Dedup 1750 Non-Dedup 1550 Dedup 1550

Data Deduplication transforms the physical allocation of a file, so I/O on deduplicated files requires more processing. Every I/O action needs to be validated against the metadata, resulting in additional I/O on the metadata. This is followed by decompressing the chunks that are stored in the chunk store and reconstructing the data requested. This extra processing is offset by the multilevel caching mechanism employed by Data Deduplication as follows:

The most popular chunks that are duplicated across the dataset are held in memory by the Data Deduplication filter cache.

The container files containing the metadata and data are opened in a cached mode, thereby benefitting from the file system caching.

The frequently written data that resides in the primary data stream of the deduplicated files (which bypasses the cache) is held in the faster SSD tier under the proper conditions, thereby eliminating the impact of random I/O.

In our test setup, looking at the allocation of the data on disk for all the volumes and aggregating the data, we see that a majority of the hot data resides on the faster SSD tier.

SizeOnSSD : 1430.72 GBSizeOnHDD : 467.14 GBTotalSizeOnDisk : 1897.86 GBSizeOnSSDPct : 75.40%

Throughout the tests, Data Deduplication delivered high savings in storage capacity. We observed a savings of 75% to 80% on an average. The following data sample shows the savings rate from one of the volumes:

PS C:\Users\Administrator> Get-DedupVolume | fl

Volume : C:\ClusterStorage\Volume6VolumeId : \\?\Volume{9c77f5f3-a9d2-49cd-a2d6-a86f0078e670}\Enabled : TrueUsageType : HyperVDataAccessEnabled : TrueCapacity : 10 TBFreeSpace : 8.58 TBUsedSpace : 1.42 TBUnoptimizedSize : 6.78 TBSavedSpace : 5.35 TBSavingsRate : 78 %MinimumFileAgeDays : 3MinimumFileSize : 32768NoCompress : FalseExcludeFolder : {\share6\LoginVSI}ExcludeFileType :ExcludeFileTypeDefault : {bin, vsv, slp, xml...}NoCompressionFileType : {asf, mov, wma, wmv...}ChunkRedundancyThreshold : 100Verify : FalseOptimizeInUseFiles : TrueOptimizePartialFiles : True

PS C:\Users\sribhat> Get-DedupStatus | fl

Volume : C:\ClusterStorage\Volume6VolumeId : \\?\Volume{9c77f5f3-a9d2-49cd-a2d6-a86f0078e670}\Capacity : 10 TBFreeSpace : 8.58 TBUsedSpace : 1.42 TBUnoptimizedSize : 6.78 TBSavedSpace : 5.35 TBSavingsRate : 78 %OptimizedFilesCount : 337OptimizedFilesSize : 6.37 TBOptimizedFilesSavingsRate : 84 %InPolicyFilesCount : 337InPolicyFilesSize : 6.37 TBLastOptimizationTime : 7/14/2014 6:14:49 AMLastOptimizationResult : 0x00000000LastOptimizationResultMessage : The operation completed successfully.LastGarbageCollectionTime : 6/23/2014 4:13:52 AMLastGarbageCollectionResult : 0x00000000LastGarbageCollectionResultMessage : The operation completed successfully.

LastScrubbingTime :LastScrubbingResult :LastScrubbingResultMessage :

Reduced storage configurationThere is interest in defining a system configuration that uses the results of Windows Server data deduplication to allow the reduction of the storage subsystem size rather than use the existing storage size more efficiently. While a full validation of such a reduced storage configuration is beyond the scope of this whitepaper, we are able to provide some general guidelines based on the above test deployment that can be used as a starting point for further system evaluations. As always, it is important to validate any new system configurations against the particular workloads of a given environment.

The size of the OS VHD per virtual desktop largely depends on the applications installed in the guest OS and will vary depending on the deployment specific to each customer. In our test deployment, each VDI desktop utilized around 30GB per OS VHD and the entire dataset of 1500 VM’s evaluates to around 44TB of storage.

Assuming we want to retain the same 6 virtual disk configuration, with 2 virtual disks per storage node, each virtual disk needs the ability to store around 7.5TB. Considering an average savings of 80%, this implies we would need around 1.5TB of space on each volume enabled with Data Deduplication. Allowing enough space for new data, we recommend to size the volume size to be around 3TB per volume.

Best practice: For reliable operation, allow enough free space on the volume to accommodate new data that is expected on the volume. This includes deploying new virtual desktops and the amount of churn expected within the guest operating system per virtual desktop.

In our test deployment, reoptimization of a sample representative dataset with an average expected churn of 5%-10%, yielded a throughput of 300 MB/sec per virtual disk. This is throughput reported in the Data Deduplication operational event logs and represents the normal mode reoptimization throughput in terms of the logical dataset size for a given amount of churn. This implies that on this deployment any nightly optimization job running in the normal mode (also known as the throughput mode) on a 5 TB logical dataset and 5-10% churn should complete in around 5 hours ( 5 TB / 300 MB = 4.85 hours).

Best practice: For reliable operation, size the virtual disks and the logical data set in such a way so as to allow Data Deduplication jobs such as optimization to complete in a reasonable time frame depending on the deployment requirements. For more information on volume sizing considerations for Data Deduplication, see Sizing Volumes for Data Deduplication in Windows Server.

The amount of data that is expected to be hot and retained in the primary data stream of the files by the Data Deduplication subsystem depends on the workload within the guest operating system and the MinimumFileAgeDays policy setting. In our test deployment, with the MinimumFileAgeDays policy set to the default of 3 days, we measured the amount of hot data per virtual disk to be around 850 MB or 1250 GB for the entire deployment.



Assuming we want to retain the same 6 virtual disk configuration, with 2 virtual disks per storage node, each virtual disk needs to support around 210GB of SSD tier size to accommodate all the hot data. Storage tiering requires additional SSD tier capacity for the higher density VM deployment. In our testing, we observed that doubling (around 480 GB) the calculated SSD tier size was sufficient to hold a majority of the hot data (as earlier described in the full-sized configuration)..

Best practice: For reliable operation, allow enough SSD tier space on the volume to accommodate most, if not all, the hot data expected on the volume. This also depends on the MinimumFileAgeDays policy setting as described earlier.

Best practice: For existing deployments, provision additional SSD tier capacity to the virtual disks, either from reserved SSD capacity in the storage pool, or by the addition of SSDs to the storage pool.

Best practice: For new deployments, overprovision the amount of SSD tier in the reduced storage configuration.

For recommendations on monitoring storage tiering performance, along with how to determine if you have sufficient SSD tier capacity for your deployment, see Monitor Storage Tiers Performance in Windows Server 2012 R2.

Incorporating the above guidelines, a starting configuration for evaluating a reduced storage configuration of the test deployment is as follows:

Reduce the configuration for storage enclosures and pools. 2 enclosures instead of the 4 used in the test deployment. Note that this does not

provide enclosure awareness because a minimum of 3 enclosures (with even distribution of disks) is necessary for enclosure awareness in a cluster.

1 storage pool using 16 x 3TB HDD’s and 8 x 400GB SSD’s from each of the 2 enclosures (Total 32 HDD’s and 16 SSD’s).

Retain the 6 virtual disk configuration (without enclosure awareness), two per storage node. 3 TB in size (3TB HDD tier and 480 GB SSD tier) 1 GB write-back cache 2-way mirror, 6 column count 64 KB interleave

Configure each virtual disk as a Cluster Shared Volume hosting a file share. Format NTFS with 64 KB allocation unit size and a large file record segment.

Best practice: When sizing the reduced configuration, it is critical to allow enough HDD spindle availability to ensure the HDD tier is able to cater to the performance demanded by the deployment both in terms of I/O load during data access as well as during Data Deduplication maintenance jobs like optimization, garbage collection and scrubbing.

Best practice: When reducing storage hardware, you need to consider clustering requirements to provide adequate redundancy with Storage Spaces. For more information, see Deploy Clustered Storage Spaces.

http://technet.microsoft.com/en-us/library/jj822937.aspx

http://technet.microsoft.com/en-us/library/jj822937.aspx



ConclusionDeploying Data Deduplication on a large-scale VDI dataset that resides on a Scale-Out File Server and uses Windows Server 2012 R2 reduces the physical storage requirements per VDI desktop. At the same time, it delivers an excellent performance on par with a deployment without Data Deduplication, with no perceptible impact on the user's perceived performance.

Appendix

Windows configurationWindows Server 2012 R2 with all released patches and updates including the update rollup for Windows Server 2012 R2 that is dated November 2014 (KB 3000850)


Storage configuration detailsHere is the detailed output for the storage tiers configuration, which you can use as a reference.

PS C:\Users\Administrator> Get-StoragePool -FriendlyName TieredPool1 | fl *

Usage : OtherOperationalStatus : OKHealthStatus : HealthyProvisioningTypeDefault : FixedSupportedProvisioningTypes : FixedReadOnlyReason : NoneRepairPolicy : ParallelRetireMissingPhysicalDisks : AutoWriteCacheSizeDefault : AutoFileSystem : UnknownVersion : Windows Server 2012 R2ObjectId : {1}\\ITE1-STORCL\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StoragePool.Obj ectId="{43568ad0-fdb5-4197-bcbb-ec11c71df9d2}:SP:{7136f30d-ca3d-11e3-b28b-000743147 5d8}"PassThroughClass :PassThroughIds :PassThroughNamespace :PassThroughServer :UniqueId : {7136f30d-ca3d-11e3-b28b-0007431475d8}AllocatedSize : 66036195917824ClearOnDeallocate : FalseEnclosureAwareDefault : FalseFriendlyName : TieredPool1IsClustered : TrueIsPowerProtected : FalseIsPrimordial : FalseIsReadOnly : FalseLogicalSectorSize : 512Name :OtherOperationalStatusDescription :OtherUsageDescription :PhysicalSectorSize : 4096ResiliencySettingNameDefault : MirrorSize : 99179384799232SupportsDeduplication : FalseThinProvisioningAlertThresholds : {70}WriteCacheSizeMax : 107374182400WriteCacheSizeMin : 0PSComputerName :


CimClass : ROOT/Microsoft/Windows/Storage:MSFT_StoragePoolCimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

PS C:\Users\Administrator> Get-StoragePool -FriendlyName TieredPool2 | fl *

Usage : OtherOperationalStatus : OKHealthStatus : HealthyProvisioningTypeDefault : FixedSupportedProvisioningTypes : FixedReadOnlyReason : NoneRepairPolicy : ParallelRetireMissingPhysicalDisks : AutoWriteCacheSizeDefault : AutoFileSystem : UnknownVersion : Windows Server 2012 R2ObjectId : {1}\\ITE1-STORCL\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StoragePool.Obj ectId="{43568ad0-fdb5-4197-bcbb-ec11c71df9d2}:SP:{7136f3bf-ca3d-11e3-b28b-000743147 5d8}"PassThroughClass :PassThroughIds :PassThroughNamespace :PassThroughServer :UniqueId : {7136f3bf-ca3d-11e3-b28b-0007431475d8}AllocatedSize : 66006131146752ClearOnDeallocate : FalseEnclosureAwareDefault : FalseFriendlyName : TieredPool2IsClustered : TrueIsPowerProtected : FalseIsPrimordial : FalseIsReadOnly : FalseLogicalSectorSize : 512Name :OtherOperationalStatusDescription :OtherUsageDescription :PhysicalSectorSize : 4096ResiliencySettingNameDefault : MirrorSize : 99179384799232SupportsDeduplication : FalseThinProvisioningAlertThresholds : {70}WriteCacheSizeMax : 107374182400WriteCacheSizeMin : 0PSComputerName :CimClass : ROOT/Microsoft/Windows/Storage:MSFT_StoragePoolCimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

PS C:\Users\Administrator> Get-StoragePool -FriendlyName TieredPool1 | Get-PhysicalDisk | Sort-Object -Property PhysicalLocation | Format-Table -GroupBy @{Expression={$_.PhysicalLocation.Split(":")[0]}} -Property @{Label="FriendlyName";Width=16;Expression={$_.FriendlyName}},@{Label="PhysicalLocation";Width=42;Expression={$_.PhysicalLocation}},@{Label="MediaType";Width=11;Expression={$_.MediaType}},@{Label="Model";Width=16;Expression={$_.Model}},@{Label="Size (GB)";Alignment="Left";Width=18;Expression={$_.Size / 1GB}}

$_.PhysicalLocation.Split(":")[0]: SES Enclosure 50080E5176F9E000

FriendlyName PhysicalLocation MediaType Model Size (GB)------------ ---------------- --------- ----- ---------PhysicalDisk123 SES Enclosure 50080E5176F9E000 : Slot 10 HDD ST33000650SS 2793.75

PhysicalDisk125 SES Enclosure 50080E5176F9E000 : Slot 14 HDD ST33000650SS 2793.75PhysicalDisk130 SES Enclosure 50080E5176F9E000 : Slot 19 HDD ST33000650SS 2793.75PhysicalDisk145 SES Enclosure 50080E5176F9E000 : Slot 34 HDD ST33000650SS 2793.75PhysicalDisk146 SES Enclosure 50080E5176F9E000 : Slot 35 SSD MK2001GRZB 185.5PhysicalDisk147 SES Enclosure 50080E5176F9E000 : Slot 36 SSD MK2001GRZB 185.5PhysicalDisk149 SES Enclosure 50080E5176F9E000 : Slot 38 HDD ST33000650SS 2793.75PhysicalDisk155 SES Enclosure 50080E5176F9E000 : Slot 44 HDD ST33000650SS 2793.75PhysicalDisk157 SES Enclosure 50080E5176F9E000 : Slot 46 HDD ST33000650SS 2793.75PhysicalDisk158 SES Enclosure 50080E5176F9E000 : Slot 47 SSD MK2001GRZB 185.5PhysicalDisk169 SES Enclosure 50080E5176F9E000 : Slot 60 SSD MK2001GRZB 185.5PhysicalDisk122 SES Enclosure 50080E5176F9E000 : Slot 9 HDD ST33000650SS 2793.75

$_.PhysicalLocation.Split(":")[0]: SES Enclosure 50080E5207286000

FriendlyName PhysicalLocation MediaType Model Size (GB)------------ ---------------- --------- ----- ---------PhysicalDisk182 SES Enclosure 50080E5207286000 : Slot 15 HDD ST33000650SS 2793.75PhysicalDisk171 SES Enclosure 50080E5207286000 : Slot 2 HDD ST33000650SS 2793.75PhysicalDisk187 SES Enclosure 50080E5207286000 : Slot 20 HDD ST33000650SS 2793.75PhysicalDisk190 SES Enclosure 50080E5207286000 : Slot 23 SSD MK2001GRZB 185.5PhysicalDisk172 SES Enclosure 50080E5207286000 : Slot 3 HDD ST33000650SS 2793.75PhysicalDisk202 SES Enclosure 50080E5207286000 : Slot 35 SSD MK2001GRZB 185.5PhysicalDisk206 SES Enclosure 50080E5207286000 : Slot 39 HDD ST33000650SS 2793.75PhysicalDisk213 SES Enclosure 50080E5207286000 : Slot 46 HDD ST33000650SS 2793.75PhysicalDisk214 SES Enclosure 50080E5207286000 : Slot 47 SSD MK2001GRZB 185.5PhysicalDisk215 SES Enclosure 50080E5207286000 : Slot 48 SSD MK2001GRZB 185.5PhysicalDisk223 SES Enclosure 50080E5207286000 : Slot 56 HDD ST33000650SS 2793.75PhysicalDisk178 SES Enclosure 50080E5207286000 : Slot 9 HDD ST33000650SS 2793.75

$_.PhysicalLocation.Split(":")[0]: SES Enclosure 50080E520737D000

FriendlyName PhysicalLocation MediaType Model Size (GB)------------ ---------------- --------- ----- ---------PhysicalDisk73 SES Enclosure 50080E520737D000 : Slot 19 HDD ST33000650SS 2793.75PhysicalDisk74 SES Enclosure 50080E520737D000 : Slot 20 HDD ST33000650SS 2793.75PhysicalDisk80 SES Enclosure 50080E520737D000 : Slot 26 HDD ST33000650SS 2793.75PhysicalDisk81 SES Enclosure 50080E520737D000 : Slot 27 HDD ST33000650SS 2793.75PhysicalDisk59 SES Enclosure 50080E520737D000 : Slot 3 HDD ST33000650SS 2793.75PhysicalDisk89 SES Enclosure 50080E520737D000 : Slot 35 SSD MK2001GRZB 185.5PhysicalDisk90 SES Enclosure 50080E520737D000 : Slot 36 SSD MK2001GRZB 185.5PhysicalDisk92 SES Enclosure 50080E520737D000 : Slot 38 HDD ST33000650SS 2793.75PhysicalDisk97 SES Enclosure 50080E520737D000 : Slot 43 HDD ST33000650SS 2793.75PhysicalDisk102 SES Enclosure 50080E520737D000 : Slot 48 SSD MK2001GRZB 185.5PhysicalDisk107 SES Enclosure 50080E520737D000 : Slot 53 HDD ST33000650SS 2793.75PhysicalDisk112 SES Enclosure 50080E520737D000 : Slot 59 SSD MK2001GRZB 185.5


FriendlyName PhysicalLocation MediaType Model Size (GB)------------ ---------------- --------- ----- ---------PhysicalDisk11 SES Enclosure 50080E5207425000 : Slot 14 HDD ST33000650SS 2793.75PhysicalDisk12 SES Enclosure 50080E5207425000 : Slot 15 HDD ST33000650SS 2793.75PhysicalDisk14 SES Enclosure 50080E5207425000 : Slot 17 HDD ST33000650SS 2793.75PhysicalDisk18 SES Enclosure 50080E5207425000 : Slot 21 HDD ST33000650SS 2793.75PhysicalDisk19 SES Enclosure 50080E5207425000 : Slot 23 SSD MK2001GRZB 185.5PhysicalDisk20 SES Enclosure 50080E5207425000 : Slot 24 SSD MK2001GRZB 185.5PhysicalDisk3 SES Enclosure 50080E5207425000 : Slot 3 HDD ST33000650SS 2793.75PhysicalDisk27 SES Enclosure 50080E5207425000 : Slot 31 HDD ST33000650SS 2793.75PhysicalDisk31 SES Enclosure 50080E5207425000 : Slot 35 SSD MK2001GRZB 185.5PhysicalDisk46 SES Enclosure 50080E5207425000 : Slot 50 HDD ST33000650SS 2793.75PhysicalDisk54 SES Enclosure 50080E5207425000 : Slot 58 HDD ST33000650SS 2793.75PhysicalDisk56 SES Enclosure 50080E5207425000 : Slot 60 SSD MK2001GRZB 185.5

PS C:\Users\Administrator> Get-StoragePool -FriendlyName TieredPool2 | Get-PhysicalDisk | Sort-Object -Property PhysicalLocation | Format-Table -GroupBy @{Expression={$_.PhysicalLocation.Split(":")[0]}} -Property @{Label="FriendlyName";Width=16;Expression={$_.FriendlyName}},@{Label="PhysicalLocation";Width=42;Expression={$_.PhysicalLocation}},@{Label="MediaType";Width=11;Expression={$_.MediaType}},@{Label="Model";Width=16;Expression={$_.Model}},@{Label="Size (GB)";Alignment="Left";Width=18;Expression={$_.Size / 1GB}}

$_.PhysicalLocation.Split(":")[0]: SES Enclosure 50080E5176F9E000

FriendlyName PhysicalLocation MediaType Model Size (GB)------------ ---------------- --------- ----- ---------PhysicalDisk182 SES Enclosure 50080E5176F9E000 : Slot 15 HDD ST3000NM0023 2793.75PhysicalDisk187 SES Enclosure 50080E5176F9E000 : Slot 20 HDD ST33000650SS 2793.75PhysicalDisk188 SES Enclosure 50080E5176F9E000 : Slot 21 HDD ST33000650SS 2793.75PhysicalDisk190 SES Enclosure 50080E5176F9E000 : Slot 23 SSD MK2001GRZB 185.5PhysicalDisk191 SES Enclosure 50080E5176F9E000 : Slot 24 SSD MK2001GRZB 185.5PhysicalDisk206 SES Enclosure 50080E5176F9E000 : Slot 39 HDD ST33000650SS 2793.75PhysicalDisk212 SES Enclosure 50080E5176F9E000 : Slot 45 HDD ST33000650SS 2793.75PhysicalDisk215 SES Enclosure 50080E5176F9E000 : Slot 48 SSD MK2001GRZB 185.5PhysicalDisk223 SES Enclosure 50080E5176F9E000 : Slot 56 HDD ST33000650SS 2793.75PhysicalDisk224 SES Enclosure 50080E5176F9E000 : Slot 59 SSD MK2001GRZB 185.5PhysicalDisk176 SES Enclosure 50080E5176F9E000 : Slot 7 HDD ST33000650SS 2793.75PhysicalDisk177 SES Enclosure 50080E5176F9E000 : Slot 8 HDD ST33000650SS 2793.75


FriendlyName PhysicalLocation MediaType Model Size (GB)------------ ---------------- --------- ----- ---------PhysicalDisk123 SES Enclosure 50080E5207286000 : Slot 10 HDD ST3000NM0023 2793.75PhysicalDisk130 SES Enclosure 50080E5207286000 : Slot 19 HDD ST3000NM0023 2793.75PhysicalDisk132 SES Enclosure 50080E5207286000 : Slot 21 HDD ST3000NM0023 2793.75PhysicalDisk133 SES Enclosure 50080E5207286000 : Slot 22 HDD ST33000650SS 2793.75PhysicalDisk135 SES Enclosure 50080E5207286000 : Slot 24 SSD MK2001GRZB 185.5PhysicalDisk145 SES Enclosure 50080E5207286000 : Slot 34 HDD ST3000NM0023 2793.75PhysicalDisk147 SES Enclosure 50080E5207286000 : Slot 36 SSD MK2001GRZB 185.5PhysicalDisk156 SES Enclosure 50080E5207286000 : Slot 45 HDD ST33000650SS 2793.75PhysicalDisk164 SES Enclosure 50080E5207286000 : Slot 53 HDD ST33000650SS 2793.75PhysicalDisk168 SES Enclosure 50080E5207286000 : Slot 59 SSD MK2001GRZB 185.5PhysicalDisk169 SES Enclosure 50080E5207286000 : Slot 60 SSD MK2001GRZB 185.5PhysicalDisk120 SES Enclosure 50080E5207286000 : Slot 7 HDD ST33000650SS 2793.75

$_.PhysicalLocation.Split(":")[0]: SES Enclosure 50080E520737D000

FriendlyName PhysicalLocation MediaType Model Size (GB)------------ ---------------- --------- ----- ---------PhysicalDisk12 SES Enclosure 50080E520737D000 : Slot 14 HDD ST33000650SS 2793.75PhysicalDisk2 SES Enclosure 50080E520737D000 : Slot 2 HDD ST33000650SS 2793.75PhysicalDisk21 SES Enclosure 50080E520737D000 : Slot 23 SSD MK2001GRZB 185.5PhysicalDisk22 SES Enclosure 50080E520737D000 : Slot 24 SSD MK2001GRZB 185.5PhysicalDisk29 SES Enclosure 50080E520737D000 : Slot 31 HDD ST33000650SS 2793.75PhysicalDisk43 SES Enclosure 50080E520737D000 : Slot 45 HDD ST33000650SS 2793.75PhysicalDisk44 SES Enclosure 50080E520737D000 : Slot 46 HDD ST33000650SS 2793.75PhysicalDisk45 SES Enclosure 50080E520737D000 : Slot 47 SSD MK2001GRZB 185.5PhysicalDisk49 SES Enclosure 50080E520737D000 : Slot 51 HDD ST33000650SS 2793.75PhysicalDisk53 SES Enclosure 50080E520737D000 : Slot 55 HDD ST33000650SS 2793.75PhysicalDisk57 SES Enclosure 50080E520737D000 : Slot 60 SSD MK2001GRZB 185.5PhysicalDisk9 SES Enclosure 50080E520737D000 : Slot 9 HDD ST33000650SS 2793.75


FriendlyName PhysicalLocation MediaType Model Size (GB)------------ ---------------- --------- ----- ---------PhysicalDisk70 SES Enclosure 50080E5207425000 : Slot 16 HDD ST33000650SS 2793.75PhysicalDisk78 SES Enclosure 50080E5207425000 : Slot 25 HDD ST33000650SS 2793.75PhysicalDisk89 SES Enclosure 50080E5207425000 : Slot 36 SSD MK2001GRZB 185.5

PhysicalDisk90 SES Enclosure 50080E5207425000 : Slot 37 HDD ST33000650SS 2793.75PhysicalDisk91 SES Enclosure 50080E5207425000 : Slot 38 HDD ST33000650SS 2793.75PhysicalDisk97 SES Enclosure 50080E5207425000 : Slot 44 HDD ST33000650SS 2793.75PhysicalDisk99 SES Enclosure 50080E5207425000 : Slot 46 HDD ST33000650SS 2793.75PhysicalDisk100 SES Enclosure 50080E5207425000 : Slot 47 SSD MK2001GRZB 185.5PhysicalDisk101 SES Enclosure 50080E5207425000 : Slot 48 SSD MK2001GRZB 185.5PhysicalDisk107 SES Enclosure 50080E5207425000 : Slot 54 HDD ST33000650SS 2793.75PhysicalDisk109 SES Enclosure 50080E5207425000 : Slot 56 HDD ST33000650SS 2793.75PhysicalDisk112 SES Enclosure 50080E5207425000 : Slot 59 SSD MK2001GRZB 185.5

PS C:\Users\Administrator> Get-StoragePool -FriendlyName TieredPool1 | Get-VirtualDisk | fl *

Usage : OtherNameFormat :OperationalStatus : OKHealthStatus : HealthyProvisioningType : FixedParityLayout : UnknownAccess : Read/WriteUniqueIdFormat : Vendor SpecificDetachedReason : NoneWriteCacheSize : 1073741824ObjectId : {1}\\ITE1-STORCL\root/Microsoft/Windows/Storage/Providers_v2\SPACES_VirtualDisk.Obj ectId="{43568ad0-fdb5-4197-bcbb-ec11c71df9d2}:VD:{7136f30d-ca3d-11e3-b28b-000743147 5d8}{cddb7d66-ccbb-11e3-b28f-000743146e28}"PassThroughClass :PassThroughIds :PassThroughNamespace :PassThroughServer :UniqueId : 667DDBCDBBCCE311B28F000743146E28AllocatedSize : 12884901888FootprintOnPool : 25769803776FriendlyName : QuorumInterleave : 65536IsDeduplicationEnabled : FalseIsEnclosureAware : TrueIsManualAttach : TrueIsSnapshot : FalseLogicalSectorSize : 512Name :NumberOfAvailableCopies :NumberOfColumns : 4NumberOfDataCopies : 2OtherOperationalStatusDescription :OtherUsageDescription :PhysicalDiskRedundancy : 1PhysicalSectorSize : 4096RequestNoSinglePointOfFailure : FalseResiliencySettingName : MirrorSize : 12884901888UniqueIdFormatDescription :PSComputerName :CimClass : ROOT/Microsoft/Windows/Storage:MSFT_VirtualDiskCimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

Usage : OtherNameFormat :OperationalStatus : OKHealthStatus : HealthyProvisioningType : FixedParityLayout : UnknownAccess : Read/WriteUniqueIdFormat : Vendor Specific

DetachedReason : NoneWriteCacheSize : 1073741824ObjectId : {1}\\ITE1-STORCL\root/Microsoft/Windows/Storage/Providers_v2\SPACES_VirtualDisk.Obj ectId="{43568ad0-fdb5-4197-bcbb-ec11c71df9d2}:VD:{7136f30d-ca3d-11e3-b28b-000743147 5d8}{cddb7dbc-ccbb-11e3-b28f-000743146e28}"PassThroughClass :PassThroughIds :PassThroughNamespace :PassThroughServer :UniqueId : BC7DDBCDBBCCE311B28F000743146E28AllocatedSize : 10997263761408FootprintOnPool : 21994527522816FriendlyName : TieredDisk1Interleave : 65536IsDeduplicationEnabled : FalseIsEnclosureAware : TrueIsManualAttach : TrueIsSnapshot : FalseLogicalSectorSize : 512Name :NumberOfAvailableCopies :NumberOfColumns : 6NumberOfDataCopies : 2OtherOperationalStatusDescription :OtherUsageDescription :PhysicalDiskRedundancy : 1PhysicalSectorSize : 4096RequestNoSinglePointOfFailure : FalseResiliencySettingName : MirrorSize : 10997263761408UniqueIdFormatDescription :PSComputerName :CimClass : ROOT/Microsoft/Windows/Storage:MSFT_VirtualDiskCimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

Usage : OtherNameFormat :OperationalStatus : OKHealthStatus : HealthyProvisioningType : FixedParityLayout : UnknownAccess : Read/WriteUniqueIdFormat : Vendor SpecificDetachedReason : NoneWriteCacheSize : 1073741824ObjectId : {1}\\ITE1-STORCL\root/Microsoft/Windows/Storage/Providers_v2\SPACES_VirtualDisk.Obj ectId="{43568ad0-fdb5-4197-bcbb-ec11c71df9d2}:VD:{7136f30d-ca3d-11e3-b28b-000743147 5d8}{cddb7dfb-ccbb-11e3-b28f-000743146e28}"PassThroughClass :PassThroughIds :PassThroughNamespace :PassThroughServer :UniqueId : FB7DDBCDBBCCE311B28F000743146E28AllocatedSize : 10997263761408FootprintOnPool : 21994527522816FriendlyName : TieredDisk2Interleave : 65536IsDeduplicationEnabled : FalseIsEnclosureAware : TrueIsManualAttach : TrueIsSnapshot : FalseLogicalSectorSize : 512Name :

NumberOfAvailableCopies :NumberOfColumns : 6NumberOfDataCopies : 2OtherOperationalStatusDescription :OtherUsageDescription :PhysicalDiskRedundancy : 1PhysicalSectorSize : 4096RequestNoSinglePointOfFailure : FalseResiliencySettingName : MirrorSize : 10997263761408UniqueIdFormatDescription :PSComputerName :CimClass : ROOT/Microsoft/Windows/Storage:MSFT_VirtualDiskCimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

Usage : OtherNameFormat :OperationalStatus : OKHealthStatus : HealthyProvisioningType : FixedParityLayout : UnknownAccess : Read/WriteUniqueIdFormat : Vendor SpecificDetachedReason : NoneWriteCacheSize : 1073741824ObjectId : {1}\\ITE1-STORCL\root/Microsoft/Windows/Storage/Providers_v2\SPACES_VirtualDisk.Obj ectId="{43568ad0-fdb5-4197-bcbb-ec11c71df9d2}:VD:{7136f30d-ca3d-11e3-b28b-000743147 5d8}{cddb7e34-ccbb-11e3-b28f-000743146e28}"PassThroughClass :PassThroughIds :PassThroughNamespace :PassThroughServer :UniqueId : 347EDBCDBBCCE311B28F000743146E28AllocatedSize : 10997263761408FootprintOnPool : 21994527522816FriendlyName : TieredDisk3Interleave : 65536IsDeduplicationEnabled : FalseIsEnclosureAware : TrueIsManualAttach : TrueIsSnapshot : FalseLogicalSectorSize : 512Name :NumberOfAvailableCopies :NumberOfColumns : 6NumberOfDataCopies : 2OtherOperationalStatusDescription :OtherUsageDescription :PhysicalDiskRedundancy : 1PhysicalSectorSize : 4096RequestNoSinglePointOfFailure : FalseResiliencySettingName : MirrorSize : 10997263761408UniqueIdFormatDescription :PSComputerName :CimClass : ROOT/Microsoft/Windows/Storage:MSFT_VirtualDiskCimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

PS C:\Users\Administrator> Get-StoragePool -FriendlyName TieredPool2 | Get-VirtualDisk | fl *

Usage : Other

NameFormat :OperationalStatus : OKHealthStatus : HealthyProvisioningType : FixedParityLayout : UnknownAccess : Read/WriteUniqueIdFormat : Vendor SpecificDetachedReason : NoneWriteCacheSize : 1073741824ObjectId : {1}\\ITE1-STORCL\root/Microsoft/Windows/Storage/Providers_v2\SPACES_VirtualDisk.Obj ectId="{43568ad0-fdb5-4197-bcbb-ec11c71df9d2}:VD:{7136f3bf-ca3d-11e3-b28b-000743147 5d8}{cddb7e6f-ccbb-11e3-b28f-000743146e28}"PassThroughClass :PassThroughIds :PassThroughNamespace :PassThroughServer :UniqueId : 6F7EDBCDBBCCE311B28F000743146E28AllocatedSize : 10997263761408FootprintOnPool : 21994527522816FriendlyName : TieredDisk4Interleave : 65536IsDeduplicationEnabled : FalseIsEnclosureAware : TrueIsManualAttach : TrueIsSnapshot : FalseLogicalSectorSize : 512Name :NumberOfAvailableCopies :NumberOfColumns : 6NumberOfDataCopies : 2OtherOperationalStatusDescription :OtherUsageDescription :PhysicalDiskRedundancy : 1PhysicalSectorSize : 4096RequestNoSinglePointOfFailure : FalseResiliencySettingName : MirrorSize : 10997263761408UniqueIdFormatDescription :PSComputerName :CimClass : ROOT/Microsoft/Windows/Storage:MSFT_VirtualDiskCimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

Usage : OtherNameFormat :OperationalStatus : OKHealthStatus : HealthyProvisioningType : FixedParityLayout : UnknownAccess : Read/WriteUniqueIdFormat : Vendor SpecificDetachedReason : NoneWriteCacheSize : 1073741824ObjectId : {1}\\ITE1-STORCL\root/Microsoft/Windows/Storage/Providers_v2\SPACES_VirtualDisk.Obj ectId="{43568ad0-fdb5-4197-bcbb-ec11c71df9d2}:VD:{7136f3bf-ca3d-11e3-b28b-000743147 5d8}{cddb7ea9-ccbb-11e3-b28f-000743146e28}"PassThroughClass :PassThroughIds :PassThroughNamespace :PassThroughServer :UniqueId : A97EDBCDBBCCE311B28F000743146E28AllocatedSize : 10997263761408FootprintOnPool : 21994527522816FriendlyName : TieredDisk5

Interleave : 65536IsDeduplicationEnabled : FalseIsEnclosureAware : TrueIsManualAttach : TrueIsSnapshot : FalseLogicalSectorSize : 512Name :NumberOfAvailableCopies :NumberOfColumns : 6NumberOfDataCopies : 2OtherOperationalStatusDescription :OtherUsageDescription :PhysicalDiskRedundancy : 1PhysicalSectorSize : 4096RequestNoSinglePointOfFailure : FalseResiliencySettingName : MirrorSize : 10997263761408UniqueIdFormatDescription :PSComputerName :CimClass : ROOT/Microsoft/Windows/Storage:MSFT_VirtualDiskCimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

Usage : OtherNameFormat :OperationalStatus : OKHealthStatus : HealthyProvisioningType : FixedParityLayout : UnknownAccess : Read/WriteUniqueIdFormat : Vendor SpecificDetachedReason : NoneWriteCacheSize : 1073741824ObjectId : {1}\\ITE1-STORCL\root/Microsoft/Windows/Storage/Providers_v2\SPACES_VirtualDisk.Obj ectId="{43568ad0-fdb5-4197-bcbb-ec11c71df9d2}:VD:{7136f3bf-ca3d-11e3-b28b-000743147 5d8}{cddb7ee2-ccbb-11e3-b28f-000743146e28}"PassThroughClass :PassThroughIds :PassThroughNamespace :PassThroughServer :UniqueId : E27EDBCDBBCCE311B28F000743146E28AllocatedSize : 10997263761408FootprintOnPool : 21994527522816FriendlyName : TieredDisk6Interleave : 65536IsDeduplicationEnabled : FalseIsEnclosureAware : TrueIsManualAttach : TrueIsSnapshot : FalseLogicalSectorSize : 512Name :NumberOfAvailableCopies :NumberOfColumns : 6NumberOfDataCopies : 2OtherOperationalStatusDescription :OtherUsageDescription :PhysicalDiskRedundancy : 1PhysicalSectorSize : 4096RequestNoSinglePointOfFailure : FalseResiliencySettingName : MirrorSize : 10997263761408UniqueIdFormatDescription :PSComputerName :CimClass : ROOT/Microsoft/Windows/Storage:MSFT_VirtualDiskCimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

PS C:\Users\Administrator> Get-VirtualDisk | Get-StorageTier | fl *

MediaType : HDDObjectId : {1}\\ITE1-STORCL\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageTier.ObjectId="{4356 8ad0-fdb5-4197-bcbb-ec11c71df9d2}:ST:{7136f30d-ca3d-11e3-b28b-0007431475d8}{cddb7d6d-ccbb-11e3- b28f-000743146e28}"PassThroughClass :PassThroughIds :PassThroughNamespace :PassThroughServer :UniqueId : {cddb7d6d-ccbb-11e3-b28f-000743146e28}Description :FriendlyName : Quorum_HDDTierSize : 12884901888PSComputerName :CimClass : ROOT/Microsoft/Windows/Storage:MSFT_StorageTierCimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

MediaType : SSDObjectId : {1}\\ITE1-STORCL\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageTier.ObjectId="{4356 8ad0-fdb5-4197-bcbb-ec11c71df9d2}:ST:{7136f3bf-ca3d-11e3-b28b-0007431475d8}{cddb7eb0-ccbb-11e3- b28f-000743146e28}"PassThroughClass :PassThroughIds :PassThroughNamespace :PassThroughServer :UniqueId : {cddb7eb0-ccbb-11e3-b28f-000743146e28}Description :FriendlyName : TieredDisk5_SSDTierSize : 515396075520PSComputerName :CimClass : ROOT/Microsoft/Windows/Storage:MSFT_StorageTierCimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

MediaType : HDDObjectId : {1}\\ITE1-STORCL\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageTier.ObjectId="{4356 8ad0-fdb5-4197-bcbb-ec11c71df9d2}:ST:{7136f3bf-ca3d-11e3-b28b-0007431475d8}{cddb7eb1-ccbb-11e3- b28f-000743146e28}"PassThroughClass :PassThroughIds :PassThroughNamespace :PassThroughServer :UniqueId : {cddb7eb1-ccbb-11e3-b28f-000743146e28}Description :FriendlyName : TieredDisk5_HDDTierSize : 10481867685888PSComputerName :CimClass : ROOT/Microsoft/Windows/Storage:MSFT_StorageTierCimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

MediaType : SSDObjectId : {1}\\ITE1-STORCL\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageTier.ObjectId="{4356 8ad0-fdb5-4197-bcbb-ec11c71df9d2}:ST:{7136f3bf-ca3d-11e3-b28b-0007431475d8}{cddb7ee9-ccbb-11e3-

b28f-000743146e28}"PassThroughClass :PassThroughIds :PassThroughNamespace :PassThroughServer :UniqueId : {cddb7ee9-ccbb-11e3-b28f-000743146e28}Description :FriendlyName : TieredDisk6_SSDTierSize : 515396075520PSComputerName :CimClass : ROOT/Microsoft/Windows/Storage:MSFT_StorageTierCimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

MediaType : HDDObjectId : {1}\\ITE1-STORCL\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageTier.ObjectId="{4356 8ad0-fdb5-4197-bcbb-ec11c71df9d2}:ST:{7136f3bf-ca3d-11e3-b28b-0007431475d8}{cddb7eea-ccbb-11e3- b28f-000743146e28}"PassThroughClass :PassThroughIds :PassThroughNamespace :PassThroughServer :UniqueId : {cddb7eea-ccbb-11e3-b28f-000743146e28}Description :FriendlyName : TieredDisk6_HDDTierSize : 10481867685888PSComputerName :CimClass : ROOT/Microsoft/Windows/Storage:MSFT_StorageTierCimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

MediaType : SSDObjectId : {1}\\ITE1-STORCL\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageTier.ObjectId="{4356 8ad0-fdb5-4197-bcbb-ec11c71df9d2}:ST:{7136f30d-ca3d-11e3-b28b-0007431475d8}{cddb7e3b-ccbb-11e3- b28f-000743146e28}"PassThroughClass :PassThroughIds :PassThroughNamespace :PassThroughServer :UniqueId : {cddb7e3b-ccbb-11e3-b28f-000743146e28}Description :FriendlyName : TieredDisk3_SSDTierSize : 515396075520PSComputerName :CimClass : ROOT/Microsoft/Windows/Storage:MSFT_StorageTierCimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

MediaType : HDDObjectId : {1}\\ITE1-STORCL\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageTier.ObjectId="{4356 8ad0-fdb5-4197-bcbb-ec11c71df9d2}:ST:{7136f30d-ca3d-11e3-b28b-0007431475d8}{cddb7e3c-ccbb-11e3- b28f-000743146e28}"PassThroughClass :PassThroughIds :PassThroughNamespace :PassThroughServer :UniqueId : {cddb7e3c-ccbb-11e3-b28f-000743146e28}Description :FriendlyName : TieredDisk3_HDDTierSize : 10481867685888PSComputerName :CimClass : ROOT/Microsoft/Windows/Storage:MSFT_StorageTier

CimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

MediaType : SSDObjectId : {1}\\ITE1-STORCL\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageTier.ObjectId="{4356 8ad0-fdb5-4197-bcbb-ec11c71df9d2}:ST:{7136f30d-ca3d-11e3-b28b-0007431475d8}{cddb7e02-ccbb-11e3- b28f-000743146e28}"PassThroughClass :PassThroughIds :PassThroughNamespace :PassThroughServer :UniqueId : {cddb7e02-ccbb-11e3-b28f-000743146e28}Description :FriendlyName : TieredDisk2_SSDTierSize : 515396075520PSComputerName :CimClass : ROOT/Microsoft/Windows/Storage:MSFT_StorageTierCimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

MediaType : HDDObjectId : {1}\\ITE1-STORCL\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageTier.ObjectId="{4356 8ad0-fdb5-4197-bcbb-ec11c71df9d2}:ST:{7136f30d-ca3d-11e3-b28b-0007431475d8}{cddb7e03-ccbb-11e3- b28f-000743146e28}"PassThroughClass :PassThroughIds :PassThroughNamespace :PassThroughServer :UniqueId : {cddb7e03-ccbb-11e3-b28f-000743146e28}Description :FriendlyName : TieredDisk2_HDDTierSize : 10481867685888PSComputerName :CimClass : ROOT/Microsoft/Windows/Storage:MSFT_StorageTierCimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

MediaType : SSDObjectId : {1}\\ITE1-STORCL\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageTier.ObjectId="{4356 8ad0-fdb5-4197-bcbb-ec11c71df9d2}:ST:{7136f3bf-ca3d-11e3-b28b-0007431475d8}{cddb7e77-ccbb-11e3- b28f-000743146e28}"PassThroughClass :PassThroughIds :PassThroughNamespace :PassThroughServer :UniqueId : {cddb7e77-ccbb-11e3-b28f-000743146e28}Description :FriendlyName : TieredDisk4_SSDTierSize : 515396075520PSComputerName :CimClass : ROOT/Microsoft/Windows/Storage:MSFT_StorageTierCimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

MediaType : HDDObjectId : {1}\\ITE1-STORCL\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageTier.ObjectId="{4356 8ad0-fdb5-4197-bcbb-ec11c71df9d2}:ST:{7136f3bf-ca3d-11e3-b28b-0007431475d8}{cddb7e78-ccbb-11e3- b28f-000743146e28}"PassThroughClass :PassThroughIds :

PassThroughNamespace :PassThroughServer :UniqueId : {cddb7e78-ccbb-11e3-b28f-000743146e28}Description :FriendlyName : TieredDisk4_HDDTierSize : 10481867685888PSComputerName :CimClass : ROOT/Microsoft/Windows/Storage:MSFT_StorageTierCimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

MediaType : SSDObjectId : {1}\\ITE1-STORCL\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageTier.ObjectId="{4356 8ad0-fdb5-4197-bcbb-ec11c71df9d2}:ST:{7136f30d-ca3d-11e3-b28b-0007431475d8}{cddb7dc3-ccbb-11e3- b28f-000743146e28}"PassThroughClass :PassThroughIds :PassThroughNamespace :PassThroughServer :UniqueId : {cddb7dc3-ccbb-11e3-b28f-000743146e28}Description :FriendlyName : TieredDisk1_SSDTierSize : 515396075520PSComputerName :CimClass : ROOT/Microsoft/Windows/Storage:MSFT_StorageTierCimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

MediaType : HDDObjectId : {1}\\ITE1-STORCL\root/Microsoft/Windows/Storage/Providers_v2\SPACES_StorageTier.ObjectId="{4356 8ad0-fdb5-4197-bcbb-ec11c71df9d2}:ST:{7136f30d-ca3d-11e3-b28b-0007431475d8}{cddb7dc4-ccbb-11e3- b28f-000743146e28}"PassThroughClass :PassThroughIds :PassThroughNamespace :PassThroughServer :UniqueId : {cddb7dc4-ccbb-11e3-b28f-000743146e28}Description :FriendlyName : TieredDisk1_HDDTierSize : 10481867685888PSComputerName :CimClass : ROOT/Microsoft/Windows/Storage:MSFT_StorageTierCimInstanceProperties : {ObjectId, PassThroughClass, PassThroughIds, PassThroughNamespace...}CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties

PS C:\Users\Administrator>

table of contents€¦ · web viewwindows server 2012 r2 supports two vdi deployment scenarios,...

Documents