@NICKBARTON,
Thanks for the reply. I understand what you're saying about creating the finder and filter. I think I could possibly make that work. I'll give it a try and let you know if I have any issues.
I am very curious about your other statement though. You said that, "standard policy now is that all volumes should have an automatic dedupe schedule as the overhead for this kind of work is not what it used to be back in the 7Mode days when this feature was first introduced". I just found this in the OnTap 9 documentation. Is this what you are referring to? I am definitely going to have to look into this. I'm a little nervous about these kicking off during production hours, but I guess if I set the policy to make them a "background" process, it should have minimal impact, correct?
From docs at: http://docs.netapp.com/ontap-9
You can modify the efficiency operation schedule to run deduplication or data compression when the number of new blocks written to the volume after the previous efficiency operation (performed manually or scheduled) exceeds a specified threshold percentage.
About this task
If the
schedule option is set to
auto, the scheduled efficiency operation runs when the amount of new data exceeds the specified percentage. The default threshold value is 20 percent. This threshold value is the percentage of the total number of blocks already processed by the efficiency operation.
Step
- Use the volume efficiency modify command with the auto@num option to modify the threshold percentage value.
num is a two-digit number to specify the percentage.
Example
The following command modifies the threshold percentage value to 30 percent for the volume VolA:volume efficiency modify -vserver vs1 -volume -VolA -schedule auto@30