On 2/10/22 10:15, egoitz--- via Bacula-users wrote:
> and you try to add some new volumes, each one with a specific capacity, as
> you launch the label command for this purpose in
> bconsole, the new volume gets started using at just that very brief moment.
> This causes you, to unable to then
Good afternoon,
If you have a pool in a "Non appendable volumes" state, with jobs in a
awaiting storage state so running, and you try to add some new volumes,
each one with a specific capacity, as you launch the label command for
this purpose in bconsole, the new volume gets started using at
Hi!
I think I solved it. I have defined the path in "Archive Device" of the
Device, defined in bacula-sd.conf, to point to the same directory as the
path in "Archive Device" of the Device for incremental backups. I have
read this advice in "Bacula : Network backup strategies and solutions".
I
Hi!,
Concretely for all this set up I have borrowed ideas from
https://www.bacula.lat/bacula-virtual-synthetic-full-and-forever-incremental-backups/?lang=es
But it seems not to work as its... directly
Cheers!
El 2022-02-09 19:48, egoitz--- via Bacula-users escribió:
> ATENCION: Este
On 2022-02-10 05:21, Larry Rosenman wrote:
[snip]
Looks like it was my firewall not allowing an ESTABLISHED session over
2 hours. I've increased it to 1 Day, and all seems(!) better.
You might want to turn on Heart Beat Interval, both in the File daemon
and the Storage daemon.
You can set it
