This would rely on dedup being enabled though for it to work.Īs for a report to see which files are in a dedup state, I’m not aware of one. If you want to know what is being worked on directly, I find looking in Resource Monitor and under disk utilisation, filtering down to the fsdmhost process, this will then show what files are being touched by the dedup process. Check the number of in-policy files with Get-DedupStatus in PowerShell and then wait for the excluded files to fall out of policy and be re-inflated. You could also possibly set an exclusion, so name some specific VHDX files in the exclusions. In the same way if you have two separate dedup enabled volumes and you move the VHDX file for a VM between the two, it will be re-inflated in transit and then re-deduped on it’s target volume. My understanding is, because dedup is done on a per volume basis, if you migrated the VM storage to another volume that doesn’t have dedup enabled on it, that will effectively re-inflate the VHDX file, as it no longer lives on a dedup enabled volume. I would guess this is just a bug, but it seems once a volume has been touched by the deduplication processes, it never goes back to a blank value for dedup rate. When all this is done, the volume will still show in some places like server manager sat at 0% deduplication rate, which is fine, as we’ve turned it off. Start-DedupJob -Type GarbageCollection -Volume E: -Fullįinally, after that, the final step is to turn off dedup on the volume with the following command Īnd that should save you any unnecessary drama. Once this is done, the next step is to run the following command to start your garbage collection on the volume Since there’s still the garbage collection job to run, we need to rather counter-intuitively turn dedup back on for the volume with the following command Enable-DedupVolume -Volume E: When that job has completed, which you can check with the Get-DedupJobĬommand, you’ll then find that deduplication has been disabled on the disk. Start-DedupJob -Type Unoptimization -Volume E: -Full So with that in mind the, step two would be to run the following command in PowerShell If you disable dedup on the volume first, you simply stop new data being processed, rather than rehydrating your already deduplicated data. In this example, the volume in question is E:ĭO NOT DISABLE DEDUPLICATION ON THE VOLUME I just thought I’d post about this, as it’s something I’ve come up against recently, how to disable deduplication on a volume on Server 2012, 2012 R2 or 2016 and inflate the data back to it’s original form. Update – : I’ve added a link here to Microsoft’s updated Server 2016 documentation that details deduplication – Understanding Data Deduplication
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |