ADSM-L

ADSM Backup and its alteration of file "last access" timestamp

1996-08-27 16:38:12
Subject: ADSM Backup and its alteration of file "last access" timestamp
From: Richard Sims <rbs AT BU DOT EDU>
Date: Tue, 27 Aug 1996 16:38:12 -0400
An historic problem with ADSM Backup is its alteration of a file's
"last accessed" timestamp, which is highly undesirable, particularly in
the case of mail files where handling programs detect unread mail via
"modified" and "accessed" timestamps.  This is also a privacy and
security issue.
    I scanned the ADSM-L archives to review past discussions of this
issue.  It has been the subject of customer complaints, but as yet seems
to have no resolution.  One circumvention I've considered it to mount the
subject file system a second time on the client, at a different mount
point, in read-only mode, and then perform the ADSM backup.
But I'd like to see a more natural solution to this problem from IBM.
    So I seek whatever perspectives list members have on this.
         thanks,   Richard Sims, Boston University OIT
<Prev in Thread] Current Thread [Next in Thread>
  • ADSM Backup and its alteration of file "last access" timestamp, Richard Sims <=