No experience with it myself.  Dunno if you meant "disk pool" as below as
generic or TYPE=DISK....a reminder that it can't be a TYPE=DISK pool, it has
to be a TYPE=FILE pool....

On Thu, Dec 3, 2009 at 12:26 PM, Brian P. Boyd <boydbria AT duke DOT edu> wrote:

> It's going via TCP/IP and we created separate storage pools for NDMP
> backups.
>
> It looks like our other TSM admin turned dedupe off for that disk
> pool...so...  either he did it because he wasn't seeing any
> deduplication ratios...or?
>
> I'll follow up with him and see why he turned it off.
>
> Can you see any other reason why NDMP backups _wouldn't_ de-dupe?
>
> Thanks!
> Brian
>
>
> On Dec 3, 2009, at 12:00 PM, Wanda Prather wrote:
>
>  Is the NDMP backup going via TCP/IP and into the same storage pool
>> as your
>> other backup data?
>> How can you tell it is not getting deduped?
>>
>>
>> On Thu, Dec 3, 2009 at 11:54 AM, Brian P. Boyd <boydbria AT duke DOT edu>
>> wrote:
>>
>>  Hello,
>>> Currently we are using TSM 6.1 to do NDMP backups of our EMC Celerra.
>>> We are getting no de-duplication results from these backups.  I'm
>>> wondering if it is because the celerra is already sending a
>>> compressed
>>> image snapshot file to TSM and TSM just doesn't de-dupe a file like
>>> that.  We're thinking about going to a more traditional backup method
>>> for NDMP backups (going with weekly incrementally, and monthly
>>> fulls...etc) however it would be good to understand why this is
>>> happening.  I find it a bit strange because we still do file-level
>>> restores just fine...
>>>
>>> If someone could educate me a bit more that would be great for piece
>>> of mind!
>>>
>>> Thanks!
>>> Brian P. Boyd
>>> Sr. SAN Admin
>>> DUKE - OIT
>>> boydbria (at) duke (dot) edu
>>>
>>>