I have a strange phenomenon: though there is definitely a full backup, a
job set to incremental claims there weren’t and wants to run a full backup.
Very unfortunate, as the tapes needed are not in place. Any idea how I could
find out what went wrong?
Did you modify the job or fileset since
I added three new jobs, two new pools and one fileset. But I kept that one job
as it was. I checked and noticed the last incremental backup failed due to an
error of the autochanger. Could that be the reason? How does bacula determine
what it has to do? I would have thought a failed job should
On 28/05/12 00:50, Henrik Zawischa - SONIC Performance Support wrote:
I added three new jobs, two new pools and one fileset. But I kept that one
job as it was. I checked and noticed the last incremental backup failed due
to an error of the autochanger. Could that be the reason? How does
Hello list.
I need to backup several machines from different networks (VLANs), so to
facilitate, I just plugged several network interfaces on my SD and Director
server (both are on the same machine), with each interface on a different
network with it's own IP address. That is great, because now
Hello,
On May 27, 2012, at 11:28 PM, Rodrigo Renie Braga wrote:
My ideal solution which Bacula, apparently, DOES NOT SUPPORT: make the
Address option on the Storage resource optional, meaning that if not
specified, the SD Address that Bacula will send to the FD is the same one
that the
Bryan, that ideia is just BRILLIANT It worked like a charm...
With only one note: I was using the storage option inside the Pool
resource (not in the Job), and apparently the Pool resource overrides any
other resources, so I just had to remove this option from the Pool to add
it to the Job
