Here is an example of what I am seeing. I can't explain why it is backing up everything over and over and over again. (fyi..The date April 28 is significant because the server was rebuilt on that day.)
Ralph -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Raibeck Sent: August 04, 2004 10:12 AM To: [EMAIL PROTECTED] Subject: Re: archive attribute - windows 2000 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/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] 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" <[EMAIL PROTECTED]> 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
<<attachment: backup_prob.gif>>
