Chapter 4 ("Backing up your data") in the client manual has a section
"Performing an incremental, selective, or incremental-by-date backup" that
discusses the criteria that TSM uses to treat a file as changed, and thus
eligible for backup. At least one of those criteria for the files has
changed, which is why TSM is backing them up. (Note: More than the
directory must have changed. If only the directory itself had changed,
then TSM would only back that directory up again, not the files beneath
the directory.)

Since the files have changed, and it is TSM's job to back up changed
files, there really isn't anything you can do to prevent them from being
backed up again, outside of excluding them from backup (which will expire
any existing backup versions).

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2005-02-07
08:08:09:

> I need help understanding how the incremental backup works in TSM.
>
>
>
> We have a TSM 5.1 environment. We have a 600gb folder on NTFS that has
> just had its timestamp changed. Now
>
> TSM looks like it's backing up all 500GB worth of files again, even
> though the timestamp on the files has not changed.
>
>
>
> My Question is. How does the timestamp on the directory effect TSM
> baclient and secondly how do I prevent TSM from
>
> Backing up all the files again?
>
>
>
> Thanks in advance.
>
>
>
>
>
>