Forum Discussion
b26063 - Bug Bash - Enabling the new ReFS Dedup will fail - not enough space on the disk
I have little experience here Joachim_Otahal as this Dedup (+ Compression) is new approach of Dedup.
Good news activating Dedup in Server Manager / Feature will install the new Dedup as it seems in my lab.
I understood that we had to disable the old dedup (when enabled before 2025, as-is) and then enable the new one.
The new Dedup differs from the old as per announcement of Ignite. It is designed to achieve a higher dedup and lesser CPU utilization. It can handle to dedup write, where as the old did Dedup on time based schedules. That's what I take from the demo at Ignite.
This all is depending on the ReFS version. Unfortunately the otherwise great inoffical document stopped at ReFS 3.9, we are at 3.14 now.
- Joachim_OtahalMar 04, 2024Iron Contributor
Karl-WE Actually compression is part of dedup since Server 2012 (without R2). It is one of the reasons why windows server deduplication quite often beats storage appliances. You can even specify which file extension should never be compressed during deduplication. Try
(Get-DedupVolume).NoCompressionFileType
which is still missing 7z in its default set...
- Karl-WEMar 05, 2024MVPinteresting didn't know. Maybe there are different compressions?
Before 2025 I never seen this could be enable or disabled. It was even in WAC for a short time but broke things and they removed the compression flag.
"Added post process compression with LZ4 & ZSTD, transparent decompression."