Am 27.04.19 um 16:54 schrieb [email protected]: > After implementing AlwaysInc schema, I've payed attention that my incremental > backup are quite large. Probably it was also true for classic Full-Diff-Inc > schema or not, I am not sure. Inspecting files included in Incremental > backup, I can see same static unchanged files backed up every day. I thought > about MD5 hash collision, then I've replaced the signature to be SHA256. > After Full backup, a next Incremental brings me almost same list of backed up > files. The noatime directive also not helped.
You may have hit a bug here. We have heard of issues like that before but could never pinpoint what exactly happens here and why. As we cannot reproduce what is broken here, we will need somebody who can reproduce and test in his envrionment. Are you able and willing to do this? You might need to run patched versions of the file-daemon and director for that. > What is strategy of selecting files to be backed up ? > If "accurate=pins5" in fileset is works in AlwaysInc mode , or its own > "accurate=yes" in jobdef breaks selection ? I did not understand this. Can you rephrase it please? > Also, I saw still open bug https://bugs.bareos.org/view.php?id=907 related to > Windows. I see the same problem on linux. While the bug has been filed for a Windows client this will probably happen on every type of system. Best Regards, Andreas -- Andreas Rogge [email protected] Bareos GmbH & Co. KG Phone: +49 221-630693-86 http://www.bareos.com Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: S. Dühr, M. Außendorf, J. Steffens, Philipp Storz -- 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 [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
