Hello, śr., 29 sty 2020 o 17:51 William Muriithi <will...@perasotech.com> napisał(a):
> Hello, > > Was trying to reduce the number of mails coming from Bacula, and was > combing through the logs to see what I can filter out. Currently, almost > all noise comes from bacula attempting to schedule a job and then realizing > the previous isn't yet done. I have configured bacula not to allow > duplicates to avoid jobs piling up in case I miss replacing tapes when all > are full. > > Anyway as I was doing so, I noticed that, sometime, bacula do consider > duplicate fatal? Yes, this is correct. > How would this make sense considering it was intentionally configured? I think I do miss your point. Why anyone on Earth would like to configure a backup job in such a way that the next job will intentionally run when a previous job did not complete and intentionally setup cancelation of the duplicated job? IMVHO if I knew that my backup job is running for i.e. 8H then I'll never schedule next backup job on 4H period and setup a cancellation of the duplicate job because it will cancel every second job by design. It would be insane, right? > Kind of confused by these instances. > > 22-Jan 17:50 bacula-dir JobId 25338: Fatal error: JobId 25266 already > running. Duplicate job not allowed. > > Well, this is a job message which inform you about the cause of the job cancelation, as the job termination status is "cancelled" and not "fatal error". What would you like to change in this message? best regards -- Radosław Korzeniewski rados...@korzeniewski.net
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
