On Wed, Feb 15, 2012 at 4:13 PM, Randy Rue rrue@fhcrc.org wrote:
Hello All,
We're troubleshooting some performance issues and trying to determine how deduplication might be might be muddying the waters on an already busy v3170 HA filer pair. There's also some likelihood that snapshots are involved.
Why do you need to run the de-dup process daily? In our environment, we set the schedule to auto & let the filer manage it based on the threshold and still see very good de-dupe ratio and good performance. e.g.: Filesystem used saved %saved /vol/vmstore1/ 446GB 301GB 40% /vol/vmstore2/ 607GB 281GB 32% /vol/vmstore3/ 693GB 245GB 26% /vol/vmstore4/ 494GB 197GB 29% /vol/vmswap/ 81GB 95GB 54% /vol/vmstore5/ 1378GB 461GB 25% /vol/vmstore6/ 70GB 57GB 45% /vol/vmstore7/ 4598MB 624MB 12% /vol/vmstore8/ 329GB 109GB 25% /vol/vmstore9/ 446GB 90GB 17%
sis status /vol/vmstore1 Enabled Idle Idle for 43:34:28 /vol/vmstore2 Enabled Idle Idle for 10875:57:18 /vol/vmstore3 Enabled Idle Idle for 41:50:19 /vol/vmstore4 Enabled Idle Idle for 163:47:09 /vol/vmstore5 Enabled Idle Idle for 25:51:08 /vol/vmstore6 Enabled Idle Idle for 32:22:59 /vol/vmstore7 Enabled Idle Idle for 27:20:30 /vol/vmstore8 Enabled Idle Idle for 56:33:27 /vol/vmstore9 Enabled Idle Idle for 50:51:38 /vol/vmswap Enabled Idle Idle for 39:46:32
Hope that helps
-net