Hi there,
I have a fresh install of a Windows Server 2012 R2 as fileserver with deduplication enabled on several volumes. One volume shows a strange behavior after a couple of weeks in productive environment: Initially I had a dedup saving rate of ~10% (volume contains mainly images), but after a few weeks, both UI and PowerShell report savings of 0 bytes.
What is really bad about this is, that the original size of the un-deduplicated files is about 880 GB and my volume has filled up to nearly 1 TB (no, data has not increased that much over time, only a few gig). Watching the volume using TreeSize (JamSoft) I found out, that the dedup folder has grown to 990 GB!
I tried to run optimization and garbage collection with no luck. The main folder is DFS replicated and (still) doing initial sync - this may change files, but dedup is configured to dedup files after 0 days.
Any ideas?
Regards,
Marc