Bareos differential backup, if it fails, will it continue or restart?

Question

Backup

Good day! lifted recently bareos. Put the task on diff. backup. Just recently, he completed a task to back up a terabyte of data. But with mistakes. Three files and directories could not be found in the network folder. Apparently someone removed them during the operation.
And now I look, he again started the task of a full backup, he writes in the logs. There is no information in the logs about the full backup, I make a full backup. "bareos-dir JobId 39: No prior Full backup Job record found. bareos-dir JobId 39: No prior or suitable Full backup found in catalog. Doing FULL backup."
Did he start all over again? The last task for a full backup hangs with the status "orange execution".
I already need him to make differentials, he will never be able to make a backup like that, users will use network folders. No one will wait until he merges a terabyte, I thought the developers foresaw this.
How can this be fixed?

Answer 1

Dif it will only do after Full. If he writes that there is no fulla, then it must be done. Hint - if you touched the fileset definitions, then specifically for the new fileset it does not have a full, and it will do it again. For a data tera, bareos is not very suitable: the classic full-diff-inc scheme leads to the fact that from time to time you need to do a full, which is deadly inconvenient. The eternal ink does not help - there is some bug in bareos in it, and it constantly copies the same files. Therefore: snapshots, and replication to another storage.