White Papers

Data Progression and Hyper-V
37 Dell EMC SC Series: Microsoft Hyper-V Best Practices | CML1009
4 Data Progression and Hyper-V
Data Progression is a core SC Series feature. While this feature is most commonly described in terms of how
it can optimize SC Series arrays that are comprised of multiple disk tiers, it will also optimize data placement
on SC Series arrays comprised of a single disk tier. With Data Progression, data is automatically and
intelligently placed in the optimal storage tier and RAID level based on usage and performance metrics.
SC Series Data Progression
The highest tier in multiple-tier SC Series arrays is typically comprised of high-performance, smaller capacity,
more-expensive disks. The lower tiers are typically comprised of slower, larger capacity, less-expensive disks.
SC Series arrays come in all-flash, hybrid, or spinning configurations, depending on the performance and
capacity needs of the workload.
In most environments, about 80% of all data is inactive or archival in nature and therefore, providing a lower
tier comprised of large capacity media (spinning or SSD) for Data Progression for long term storage is an
important part of the array design.
New data is automatically written to the highest storage tier for maximum performance (tier 1-RAID 10). Data
Progression will move inactive data to the lowest tier over time. Conversely, if data in a lower tier begins to
experience frequent activity, Data Progression will automatically move it to a higher performing tier.
4.1 Tuning Data Progression settings for Hyper-V
Since Data Progression is platform-agnostic, there are no extra steps required for Hyper-V to take full
advantage of Data Progression and data tiering. Choosing the Recommended (All Tiers) storage profile
when creating new volumes (including cluster shared volumes) generally works well and is recommended for
most Hyper-V environments.
Default storage profiles
Choosing a different storage profile for a volume might be advisable for some Hyper-V configurations.
Consider the examples in sections 4.1.1 and 4.1.2.