Morning Radosław,
> 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? That is how I initially set it up. The problem is, sometimes, the tapes run out on weekend or at night and jobs fall behind. So over time, you end up with 2 or 3 jobs scheduled to backup the same file. Instead of restarting to cleanup the backlog, I thought rejecting duplicates was less involving. How do you handle these cases without configuring bacula to avoid duplicates? > 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? Agree, cancelled is fine. I find fatal a bit excessive. That name, I would only use for things that require intervention, not something configured to happen intentionally. Its just a view point, and understand how hard to code against all edge cases. Thought the feedback is worth it though. Regards, William _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
