On Wed, 13 Jan 2010 20:18:19 -0600, Steve Costaras said:
            

Ok, found out why when I do a restore of files bacula keeps thinking 
that they are 'new' and will back them up again.   Seems that bacula 
changes ctime to the time of the restore of the file not the original 
ctime.   atime & mtime are properly set on the files at restore but not 
ctime.

I didn't see anything in the on-line docs, is there a flag in the 
fileset directive to keep ALL time values (atime, mtime, ctime) to be 
exactly as they were on the original file when doing a restore?
    

No, there is no way to do that.  It is impossible to modify the ctime on unix
without hacking the disk directly.

__Martin

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users