 |
Hi, I think I've found the error. This looks like implementation error. This looks related to the accurate implementation and the situation where 2 incrementals (different jobs but on same client, sharing same accurate informations) are run sequentially on the same Client. As a try, I've inverted the backup order : Launching the AI before the original Incremental, and... The result is also inverted ! So, I created a "testmodif1.txt" file, then launching AI Job then Incr job with tracelog enabled and the result is : root@pve-support:~# grep testmo /var/lib/bareos/pve-support-fd.trace.* /var/lib/bareos/pve-support-fd.trace.ai:pve-support-fd (100): filed/accurate.cc:186-21381 accurate /root/testmodif1.txt (not found) /var/lib/bareos/pve-support-fd.trace.incr:pve-support-fd (100): filed/accurate_htable.cc:87-21382 add fname=</root/testmodif1.txt> lstat=P0A DAAKQ IGk B A A A A BAA A Bck55J Bck55J Bck55J A A d delta_seq=0 chksum= /var/lib/bareos/pve-support-fd.trace.incr:pve-support-fd (100): filed/accurate.cc:101-21382 lookup </root/testmodif1.txt> ok As you can see, the file is not backed up on the second incr job. Again, modified the testmodif1.txt file and launching AI then Incr job : root@pve-support:~# grep testmod /var/lib/bareos/pve-support-fd.trace* /var/lib/bareos/pve-support-fd.trace.ai:pve-support-fd (100): filed/accurate_htable.cc:87-21383 add fname=</root/testmodif1.txt> lstat=P0A DAAKQ IGk B A A A A BAA A Bck55J Bck55J Bck55J A A d delta_seq=0 chksum= /var/lib/bareos/pve-support-fd.trace.ai:pve-support-fd (100): filed/accurate.cc:101-21383 lookup </root/testmodif1.txt> ok /var/lib/bareos/pve-support-fd.trace.ai:pve-support-fd (99): filed/accurate.cc:276-21383 /root/testmodif1.txt st_mtime differs /var/lib/bareos/pve-support-fd.trace.ai:pve-support-fd (100): findlib/bfile.cc:1101-21383 bopen: fname /root/testmodif1.txt, flags 00000000, mode 0000, rdev 0 /var/lib/bareos/pve-support-fd.trace.incr:pve-support-fd (100): filed/accurate_htable.cc:87-21384 add fname=</root/testmodif1.txt> lstat=P0A DAAKW IGk B A A A F BAA I Bck6Aw Bck6Aw Bck6Aw A A d delta_seq=0 chksum= /var/lib/bareos/pve-support-fd.trace.incr:pve-support-fd (100): filed/accurate.cc:101-21384 lookup </root/testmodif1.txt> ok Then as you can see, as soon as the file have been backed up a first time, it will never be backed up again even if the job is not the same. As a result : Inconcistent backups I know it should not happen with a proper jobs setup but in some cases, it could. |
|
|
Hello cleaning our bug db entries, we would like to know if you can still reproduce this with a recent version like 22.1.0? Regards |
|
|
Should work normally if you adapt your configuration to the rule one-client-one-fileset-> give one job, one accurate entity. So if you double your fileset, then inc and AI inc should react the same. |
|
|
configuration issue |
- Anonymous
