make_recovery changing file access times

[Richard Nettleton]

When running "make_recovery -A" it is changing the access times of all file in /home as it backs them up. Is there anyway to stop it changing the access time as we delete files in /home which have not been accessed in 10 days, which now never exist as our make_recovery runs every week. I know i can use "mtime" in my find command but i then don't know if its been accessed by a user.

[James R. Ferguson]

Hi Richard:

This was a relative recent change made to the Ignite 'make_tape_recovery' (and hence, 'make_recovery') process.

In earlier releases of Ignite, the access timestamps of files were restored. The side effect of this restoration, however, was that the inode change timestamp (as seen by 'ls -c' or 'find -ctime') was changed reflecting the restoration of the access timestamp at the conclusion of the file copy. This, in turn, triggered certain security monitoring tools to flag an event against the file denoting possible "tampering". Thus, the restoration of the last access timestamp was eliminated.

Regards!

...JRF...

[James R. Ferguson]

Richard:

BTW, this change occurred in Ignite release A.3.3/B.3.3 (April 2001).

Regards!

...JRF...

[harry d brown jr]

Richard,

Move /home to another Volume Group, like vg01, that way it doesn't become part of the make_recovery, which in my opinion, it shouldn't. Or you might be able to change the configuration files for make_recovery to exclude /home.


live free or die
harry

[James R. Ferguson · Accepted solution]

Hi (again) Richard:

Harry's suggestion can be accomodated without moving /home out of vg00. The 'make_tape_recovery' command allows the inclusion and exclusion of files and/or directories. You could exclude /home at that level if you so chose ('-x exclude=/home'):

# /opt/ignite/bin/make_tape_recovery -x inc_entire=vg00 -x exclude=/home -I -v -a /dev/rmt/0mn

Regards!

...JRF...