ok, so here's what I have so far:
The director is set to read files from /etc/bacula/conf.d (see 13.2.3
in the latest bacula manual)
The client creates a special conf file.
The client uses scp to copy that file to /etc/bacula/conf.d in the director
So far this works ok, now the problem is how
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?"
Hello,
This "error" doesn't look too serious to me, but it is also not
normal behavior. Bacula is writing until it gets a bad status,
which it does when it reports "got -1". That should happen when
it hits the end of tape marker. Normally there is still
ok, so here's what I have so far:
The director is set to read files from /etc/bacula/conf.d (see 13.2.3
in the latest bacula manual)
The client creates a special conf file.
The client uses scp to copy that file to /etc/bacula/conf.d in the director
So far this works ok, now the problem is how d
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
> 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
Here is a log from a backup that run yesterday, it tells me it was okay
but when you take a look at the log it always tells that ther is a error
befor he changes tape.
18-Dec 11:49 fg-back-dir JobId 11002: Start Backup JobId 11002,
Job=ArbeitsdatenExtern.2014-12-18_11.36.25_35
18-Dec 11:49 fg-
