Re: [Bacula-users] max run time

2012-07-29 Thread Steve Thompson
On Thu, 19 Jul 2012, Dan Langille wrote: On 2012-07-15 13:48, Steve Thompson wrote: On Sun, 15 Jul 2012, Thomas Lohman wrote: This actually is a hardcoded sanity check in the code itself. Search the mailing lists from the past year. I'm pretty sure I posted where in the code this was and

Re: [Bacula-users] max run time

2012-07-19 Thread Dan Langille
On 2012-07-15 13:48, Steve Thompson wrote: On Sun, 15 Jul 2012, Thomas Lohman wrote: This actually is a hardcoded sanity check in the code itself. Search the mailing lists from the past year. I'm pretty sure I posted where in the code this was and what needed to be changed. Excellent;

Re: [Bacula-users] max run time

2012-07-19 Thread Steve Thompson
On Thu, 19 Jul 2012, Dan Langille wrote: On 2012-07-15 13:48, Steve Thompson wrote: On Sun, 15 Jul 2012, Thomas Lohman wrote: This actually is a hardcoded sanity check in the code itself. Search the mailing lists from the past year. I'm pretty sure I posted where in the code this was and

Re: [Bacula-users] max run time

2012-07-15 Thread Steve Thompson
On Sat, 14 Jul 2012, Boutin, Stephen wrote: Try changing (or adding if you don't have it already) the heartbeat interval variable. I have about 160TB I'm currently backing up total some of the boxes are 8-29TB jobs. Heartbeat is must, for large jobs, as far as I'm concerned. Good idea,

Re: [Bacula-users] max run time

2012-07-15 Thread Thomas Lohman
This actually is a hardcoded sanity check in the code itself. Search the mailing lists from the past year. I'm pretty sure I posted where in the code this was and what needed to be changed. We have no jobs that run more than a few days so have not made such changes ourselves so I can't

Re: [Bacula-users] max run time

2012-07-15 Thread Steve Thompson
On Sun, 15 Jul 2012, Thomas Lohman wrote: This actually is a hardcoded sanity check in the code itself. Search the mailing lists from the past year. I'm pretty sure I posted where in the code this was and what needed to be changed. Excellent; thank you! I have found your post and the

Re: [Bacula-users] max run time

2012-07-14 Thread Joseph Spenner
On Jul 14, 2012, at 5:38 PM, Steve Thompson s...@vgersoft.com wrote: Bacula 5.0.2, CentOS 5.8. I have this in my job definitions: Full Max Run Time = 29d but still they are terminated after 6 days: 14-Jul 20:27 cbe-dir JobId 39969: Fatal error: Network error with FD during

Re: [Bacula-users] max run time

2012-07-14 Thread Steve Thompson
On Sat, 14 Jul 2012, Joseph Spenner wrote: That's insane! :) Heh :) Ok, can you maybe carve it up a little? How big is the backup? I have already carved it up just about as much as I can. I have to back up about 6 TB in 28 million files (that change very slowly) to a remote offsite SD. I

Re: [Bacula-users] max run time

2012-07-14 Thread Boutin, Stephen
Try changing (or adding if you don't have it already) the heartbeat interval variable. I have about 160TB I'm currently backing up total some of the boxes are 8-29TB jobs. Heartbeat is must, for large jobs, as far as I'm concerned. - Steve Sent from my iPhone On Jul 14, 2012, at 8:19 PM,

Re: [Bacula-users] Max Run Time behavior

2012-05-09 Thread Jeremy Maes
Op 8/05/2012 11:06, Silver Salonen schreef: Hi. Does anyone know how to interpret Max Time directives from http://www.bacula.org/en/dev-manual/main/main/New_Features_in_3_0_0.html#SECTION00132417000 ? Should the Max Run Time indicate Run Time + Blocked (Max Wait Time) + Run

Re: [Bacula-users] Max Run Time exceede with 0s run time!

2010-04-12 Thread Harald Schmalzbauer
Harald Schmalzbauer schrieb am 08.04.2010 20:18 (localtime): Am 08.04.2010 14:20, schrieb Matija Nalis: On Mon, Apr 05, 2010 at 12:46:25PM +0200, Harald Schmalzbauer wrote: Absurdly canceled job 47: Fatal error: Max run time exceeded. Job canceled. Scheduled time: 04-Apr-2010 21:01:03

Re: [Bacula-users] Max Run Time exceede with 0s run time!

2010-04-08 Thread Matija Nalis
On Mon, Apr 05, 2010 at 12:46:25PM +0200, Harald Schmalzbauer wrote: Absurdly canceled job 47: Fatal error: Max run time exceeded. Job canceled. Scheduled time: 04-Apr-2010 21:01:03 Start time: 04-Apr-2010 21:39:41 End time: 04-Apr-2010 21:39:41 Elapsed

Re: [Bacula-users] Max Run Time exceede with 0s run time!

2010-04-08 Thread Harald Schmalzbauer
Am 08.04.2010 14:20, schrieb Matija Nalis: On Mon, Apr 05, 2010 at 12:46:25PM +0200, Harald Schmalzbauer wrote: Absurdly canceled job 47: Fatal error: Max run time exceeded. Job canceled. Scheduled time: 04-Apr-2010 21:01:03 Start time: 04-Apr-2010 21:39:41 End time: