Re: [Bacula-users] 2 hours 11 mins 42 secs

2014-12-19 Thread Kern Sibbald
Hello, I have never found any reason to set the heartbeat to anything less than 300 (5 minutes). You have very likely missed turning on the heartbeat in all places (there are quite a few places). The other major point is: "why is your backup waiting over two hours before transferring any data?"

Re: [Bacula-users] 2 hours 11 mins 42 secs

2014-12-19 Thread Josh Fisher
On 12/19/2014 6:32 AM, Glen Searle wrote: >> On 12/16/2014 4:51 AM, Glen Searle wrote: >>> If they run for too long, all my backups fail with this in the error report. >>> Elapsed time: 2 hours 11 mins 42 secs >>> I've set heartbeat to 60 seconds in the fd and dir configuration. > > On 16/12/14 12

Re: [Bacula-users] 2 hours 11 mins 42 secs

2014-12-19 Thread Glen Searle
> On 12/16/2014 4:51 AM, Glen Searle wrote: >> If they run for too long, all my backups fail with this in the error report. >> Elapsed time: 2 hours 11 mins 42 secs >> I've set heartbeat to 60 seconds in the fd and dir configuration. On 16/12/14 12:17, Josh Fisher wrote: > It is still likely a ne

Re: [Bacula-users] 2 hours 11 mins 42 secs

2014-12-16 Thread Josh Fisher
On 12/16/2014 4:51 AM, Glen Searle wrote: > If they run for too long, all my backups fail with this in the error report. > > Elapsed time: 2 hours 11 mins 42 secs > > I've set heartbeat to 60 seconds in the fd and dir configuration. It is still likely a network issue. Something is dropping the TC

[Bacula-users] 2 hours 11 mins 42 secs

2014-12-16 Thread Glen Searle
If they run for too long, all my backups fail with this in the error report. Elapsed time: 2 hours 11 mins 42 secs I've set heartbeat to 60 seconds in the fd and dir configuration. As this is across multiple directors and clients I'm assuming people here have dealt with this, if this is unique