A change of permissions is necessarily going to be a true change to the
file's attributes at the filesystem level. As such, the filesystem is
going to update the change time (st_ctime) for the file,
When not using Accurate mode, Bacula selects files for backup that have
a change in st_ctime or st_mtime since the last backup.
When using Accurate mode, the accurate attribute can be set in the
FileSet with a number of options on how to select the files, including
ctime, mtime, change of permissions, change of signature, change of
size, etc. You will need to use accurate mode and be sure not to select
files based on st_ctime changes.
On 2/5/26 03:16, Andrea Venturoli wrote:
On 2/2/26 10:13, Andrea Venturoli wrote:
Hello.
In an installation I manage, there's a NAS with lot of data that is
backed up with the usual Full/Diff/Inc schedule.
On this NAS it's quite frequent to have sweeping permission changes;
alas these almost translate an Incremental backup into a Full one.
I don't care about permissions: I can set them up automatically after
a restore, so I'd like to avoid this.
What's the proper way to tell Bacula NOT to backup a file if only its
permission changed?
Or, again, don't backup permissions at all, if the above is not
feasible?
I also thought about using "accurate: mco1", which should backup the
permissions, but not the files themself. This could do...
Before putting it into production, though, are there any caveat?
Any other idea?
No one?
bye & Thanks
av.
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
