Hi Alex,

I believe that on NTFS, last access time has a resolution of 1 hour. Thus
if the file was accessed within the last hour, accessing it again won't
change the last access time. If the file was accessed over an hour ago,
then accessing the file will change the last access time. So in some
cases, yes, it is possible that if TSM access the file, it won't cause the
last access time to change. It depends on when the file was last accessed
prior to the TSM backup.

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.




Alex Paschal <AlexPaschal AT FREIGHTLINER DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/27/2002 11:54
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Windows NTFS last accessed date set by TSM
client



Andy,

What exactly is the issue?  Personally, during my testing, it looked like
the TSM client maintained the last access date and NTFS didn't
automatically
update the Last Access date as you describe when TSM accessed the file (on
WinNT4 SP6, I think).  The updated access time issues I encountered had to
do with interoperability with the McAfee virus scan software.  Here is the
message I posted with one of my actual tests copied and pasted in it.
http://msgs.adsm.org/cgi-bin/get/adsm0109/460.html

I believe your statement that NTFS updates the Access Date when TSM access
the file possibly occurs under situations I didn't test.  Could you give
us
more detail?


Thanks,
Alex Paschal
Storage Administrator
Freightliner, LLC
(503) 745-6850 phone/vmail