Do you have any tools that scan the machine on a weekly basis, and perhaps
flip the archive flag?

What I don't understand is how this could cause havoc with your
incremental backup. TSM ignores the archive flag when determining whether
the file has changed, nor does it change the flag after the backup (unless
you use the RESETARCHIVEATTRIBUTE option).

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 08/04/2004
06:56:48:

> Has anyone seen a situation where the archive attribute gets turns on
> but the data hasn't changed ?  I have a server that appears to have this
> problem.  I don't see any scheduled tasks running that could cause this.
> It happens weekly and causes havoc on my incremental.  I also see files
> that have the attribute still on after the backup has ended (sometimes
> the backup has to be cancelled because it bleeds into 1st shift.  Could
> that leave the attribute on?).  I am thinking about using
> RESETARCHIVEATTR to see if this helps.  Any suggestions would be
> welcome.  This is a windows 2000 server version 5 sp 4 build 2195 with
> TSM client 5.1.7.
>
> Thanks,
> Ralph