Windows 10: Windows 11 and Storage Spaces / Tiered Storage

I have Windows 11 Pro not Workstation or Enterprise and I would create a Storage Space with the "Manage Storage Spaces" and I add 3 drives into a Simple non -mirrored/non-parity volume, 1 NVMe SSD and 2 HDD's, would this automatically make the Storage Space Tiered, e.g. WIll it start creating a "heatmap" of stuff that is used more often and move this automatically to the faster SSD and leave the unused data on the HDD's or is this not possible?

:)

 

Does Windows 10 support tiered storage?

Would also like to see this answered. Does Windows 10 Pro Storage Spaces support tiered storage?

 

Does Windows 10 support tiered storage?

Hi,

Respectfully, this question is not related to servers. The OP is asking if Windows 10 Pro supports tiered storage spaces. I came here with the same question. Does Windows 10 Pro allow for the creation of a tiered storage space with SSDs used to accelerate
the pool?

Please provide an answer related to Windows 10 Pro.

Thank you,

 

Does Windows 10 support tiered storage?

No prob.

These devices aren't susceptible to things like the samsung drives for firmware updates/etc. They have their own control layer and can still be updated and monitored once in the array.

I think till this gets flushed out, I'm just going to run a 2-column, 2-copy, 4 HDD setup and use the flash for other use cases right now. I can always rebuild this later if some kind of active tiering or tiering policies become available.

Let me know if I missed some rule setting somewhere that would control where the data lands.

It could be a difference between windows 10 and server 2012+, but I'm definitely not experiencing what this article shows:

Understand Storage Space Tiering in Windows Server 2012 R2

"Behavior of Storage Space Tiering

Here are the data flows start from the storage pool and virtual disk got provisioned.

• After virtual disk with tiered storage got provisioned, the virtual disk would have certain capacity for each tier (SSD and HDD). At that point of time, both of the tiers are empty. When there is new data coming in, the data would write to SSD Tier
  directly until SSD Tier is full.
• After SSD Tier is full, new incoming random writes will first go to write back cache and then flush to HDD tier. If write back cache is full (be default each virtual disk has only 1GB write back cache), then the data will be written to HDD directly.
• At the same time, Write Back Cache will continue flush data to HDD tier.
• When Write Back Cache is available again, it would handle new incoming random writes."

Thanks,

-- Dave