For various reasons, I'm trying to rehydrate my dedup volumes on a recently deployed File Server 2012 R2. There's 5 volumes with dedup turned on - savings ranging from 28% to 49%, and the sizes range from 200GB to 2TB.
I'm running the powershell command:
start-dedupjob -volume "I:" -type unoptimization -priority high
However, after a day, the result of "get-dedupjob" is that the unoptimization type is still running, but shows 0% progress. Shouldn't there be some indications that the job is running? I know the job is going to take awhile, but even the small volumes aren't moving.
I also ran "get-dedupstats" and compared the before and after "optimizedfiles" category, and that is unchanged as well.
Any ideas?
(Sidenote: prior to running the command, I put the volume folders in the "excluded" folder list so they wouldn't reoptimize after the job was done. Is this right?)
There's no error in the event logs, and in the Dedup log files, it shows that the job has started, and requested memory space, but nothing after that.