Hi Tim

We use native TSM deduplication (software).

It's generally accepted that you perform one or the other and not both.
This is because additional deduplication results in an additional latency
and often results in zero or negligible improvements.  Deduplication
functions as a result of finding repetitive patterns, and the result are
blocks with little repetition.  Performing deduplication against disk or
files that is already deduplicated (and now have few repeating patterns) is
a waste of time and resources.

Best regards,

Mike Ryder
RMD IT Client Services

On Thu, May 14, 2015 at 8:44 AM, Tim Brown <TBrown AT cenhud DOT com> wrote:

> Can anyone provide insight to how they use deduplication within TSM.
>
> TSM with SW based deduplication, no HW deduplication
>
> TSM with no SW based deduplication, using HW deduplication
>
> TSM with both SW and HW deduplication
>
> The only major restriction that I have read is that TSM file based primary
> storage pools should
> not be deduplicated at both SW and HW levels.
>
> Any insights appreciated!
>
> Thanks,
>
> Tim Brown
> Supervisor Computer Operations
> Central Hudson Gas & Electric
>