Anders. You are correct, I misspoke. In the TSM NDMP
implementation, it uses a FULL+Diff backup approach, not the Full+Incr.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Granhagen Anders
Sent: Thursday, March 09, 2006 1:21 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: ndmp limitations

<snip>
        The Full -incr -incr -incr ..-Full methodology is a step
backwards and if your retentions are very long, you will end up keeping
MUCH more data in TSM than through normal TSM backups.
<...>

Are you really using "full + incr" backup methodology though?

I was under the impression that IBM haven't implemented support in TSM
for Full+Incr, only Full+Diff, which in turn will generate even more
data than the Full+Incr. 

We are not running NetApp but Celera, but I think the lack of support
for Full+incr is on the "TSM"-side, since Full+incr is part of the
NDMP-standard, just not implemented in TSM (yet?).

This is a big grief if you need to keep the same retention settings that
you normally have on your fileservers, since it generates very large
amount of backup data and from my perspective one of the biggest CONs of
using NAS/NDMP. 

Best regards,
___________________________________
Anders Granhagen
Atea System Platforms
Phone: +46 8 4708104   Mobile: +46 709 197218