Force dedupe

[tech-man]

Hello

 

I have just copied a fair amount of data on to a deduped drive, how can I force a dedupe to run?

 

Thanks

[Achandler]

Use Powershell and the Start-DedupJob command.

 

https://technet.microsoft.com/en-us/library/hh848450.aspx

[tech-man]

Awesome - thanks. Do I need to use any of the other commands first?

[Achandler]

I think you just need the drive letter as a parameter (been a while). You need to setup dedupe on the volume first like normal that that command should start it off.

 

It hammers the processers and RAm etc unless you use parameters to limit it.

[tech-man]

It's been setup on a volume for a while, just moving more data to it and want to force it to run.

[Arthur]

@tech-man. I run these commands when I need to force a dedupe.

 

Start-DedupJob -Type Optimization -Memory 75 -Priority High -Volume [color="#FF0000"]X:[/color] -Wait
Start-DedupJob -Type GarbageCollection -Full -Memory 75 -Priority High -Volume [color="#FF0000"]X:[/color] -Wait
Start-DedupJob -Type Scrubbing -Full -Memory 75 -Priority High -Volume [color="#FF0000"]X:[/color] -Wait

 

Source: http://deploymentresearch.com/Research/Post/397/Running-the-Data-DeDuplication-process-in-PowerShell

[ADMaster]

If you just moved the data to the drive you will need to set the MinimumFileAgeDays to 0. I think the default is 5 days. I'm not finding a source for that, but that is what mine is currently set to. You will want to set it back once done, or the drive will constantly try to dedupe files after every change.

[Cache]

You configure the dedupe age in the deduplication config - the default date is 5 days. I slipped up on this recently, using robocopy and copying the date attribute will allow you to dedupe straight away.

[Arthur]

Also quite useful is the following command to check for corrupted files after they have been deduped.

 

Get-WinEvent -LogName Microsoft-Windows-Deduplication/Scrubbing | where ID -EQ "12800" | Sort-Object -Property Message