I can think of couple of possibilities.   First one that comes to my mind
is the copygroup mode setting for this node.  If the mode is absolute,
regardless what schedule type is, the file can be backed up.  So I would
check there.  Another instance where  I have seen is sometimes a certain
program running on the client machine that touches all the files and
changes last time/date modification causing the files to be backed up.
Check the files on the client and see if last access modification time
stamp has changed.

Also in the TSM client manual there is a section that describes which files
are backed up.  Maybe it can give you some clues.

Thanks,

Sung Y. Lee


"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 07/21/2005
02:38:23 AM:

> Hello,
>
> I have a problem with incremental backups on a windows 2003 file server.
> It seems as if TSM always does a full backup.
> We did a successful initial full backup on the weekend ( 404 GB ).
> The following days we always had more than 100 GB in the morning and had
> to cancel the backup sessions. Today we had even > 230 GB of
> "incremental" Backup Data when we canceled it. Nobody renamed or moved a
> large directory, nor did we set any option in dsm.opt that forces a full
> backup. We would except not more than 70 GB of changed data.
> Anyone having similar problems?
>
> TSM Server Version 5.2.5 Linux s390x
> Client Version 5.3 on Windows 2003 Server
> Backed up Filesystem is NTFS (compressed)
>
> I do the backup via schedule (action is "incremental backup").
>
> regards,
>
> Volker