[bareos-users] Absolute Job Timeout

[Jason Bailey]

I have a question about the Absolute Job Timeout directive. If I have a
backup job that takes longer than "absolute job timeout" (in seconds) to
complete, will Bareos fail/stop the job? Or is this directive more about
lack of activity in a given job?

I'm running Bareos 14.2 on client, director and the storage daemon.

Jason

[Marco van Wieringen]

I have a question about the Absolute Job Timeout directive. If I have a backup job that takes longer than "absolute job timeout" (in seconds) to complete, will Bareos fail/stop the job? Or is this directive more about lack of activity in a given job?
I'm running Bareos 14.2 on client, director and the storage daemon.

Absolute Job Timeout was added to 14.2 to replace the Bacula hard coded
limit of 6 days for a Job which some people ran into when doing long running
jobs. Its now by default set to 0 which means don't care about how long a Job runs.
But if you have the idea you have the need to automatically kill jobs that run
longer then this is known to work well in Bacula as all jobs longer then 6 days
got nicely killed there. Given you can properly cancel Jobs I see no real reason
to set it that is also why the new default is 0 and not the old arbitrary 6 days.
--
Marco van Wieringen ***@bareos.com
Bareos GmbH & Co. KG Phone: [phone]
http://www.bareos.com

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens,
P. Storz, M. v. Wieringen