Discussion:
[bareos-users] Date Modified
mds
2018-07-30 20:29:45 UTC
Permalink
I have a client on a Windows machine which is used for audio file editing. There are a lot of .wav and .mp3 files on this machine. The way the files are organized is such that there are many audio files in a small number of folders. The phenomenon I'm noticing is that when Bareos is checking the date modified for the files it doesn't travel all the way down the folder tree. In other words, if the date is modified for a folder, which happens for trivial actions like moving a new file into said folder, Bareos will back up the entire folder. It seems to be misunderstanding the difference between a file and a folder. Is this behavior to be expected? Another weird thing is that this behavior isn't even consistent. Some folders that have a date modified won't have all their contents backed up.
--
You received this message because you are subscribed to the Google Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+***@googlegroups.com.
To post to this group, send email to bareos-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Bruno Friedmann
2018-07-31 06:17:54 UTC
Permalink
Most of the time when this kind of behavior is surprizing, it's more non understanding what happen.
Of course if an attribute of a folder or a file is changed, between two backup with level incremental and accurate = yes the new attribute have to be backuped, (well otherwise ...)

Check carefully with stat, getfacl and getattr the difference. It of course also depend of the Verify options you have setup in your fileset.

If you work a bit with your software (to have rought mental vision about what you think that have changed) and thus run an estimate job with level=incremental accurate=yes list file you will know what bareos want to backup due to changes.
Post by mds
I have a client on a Windows machine which is used for audio file
editing. There are a lot of .wav and .mp3 files on this machine. The
way the files are organized is such that there are many audio files in
a small number of folders. The phenomenon I'm noticing is that when
Bareos is checking the date modified for the files it doesn't travel
all the way down the folder tree. In other words, if the date is
modified for a folder, which happens for trivial actions like moving a
new file into said folder, Bareos will back up the entire folder. It
seems to be misunderstanding the difference between a file and a
folder. Is this behavior to be expected? Another weird thing is that
this behavior isn't even consistent. Some folders that have a date
modified won't have all their contents backed up.
--
You received this message because you are subscribed to the Google
Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
--
You received this message because you are subscribed to the Google Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+***@googlegroups.com.
To post to this group, send email to bareos-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Loading...