|> > Why is Veritas Netbackup changing inode change timestamp on every
|> > backuped file? Is it possible to change the Netbackup-configuration
|> > in order to avoid changing inode change time?
|> I don't have the manuals at hand right now. But I seem to remember
|> that Netbackup has 2 options dealing with atime/ctime.
|> 1) The default. After having read the file and backed it up (and
|> therefore having modified atime of the file), NetBackup resets the
|> atime of the file (and therefore modifies ctime). IIRC, this is
|> done to be able to cooperate nicely with HSM products
|> 2) After having read the file and backed it up (and therefore having
|> modified atime of the file), just leave everything as is and
|> The second behaviour can be reached with a combination of 2 options in
|> bp.conf. Something like DONT_MODIFY_ATIME and
|> USE_CTIME_FOR_INCREMENTALS or somesuch. Read the docs to find out how
|> the options are called exactly.
With the options described above Netbackup can preserve atime and mtime,
but only at the expense of ctime. There is no option to preserve all the
timestamps. This is a shortcoming of Netbackup since the timestamps are
valuable metadata that belong to the owner of the file. If ctime is
preserved, it can be used to provide auditability to insure files have not
been tampered with (as with tripwire). If it is changed by the backup then
it is useless for this purpose.