On Wednesday 22 October 2014 10:24:53 Robert Oschwald wrote:
> Using Bacula Server 7.0.4 on CentOS6_64.
>
> One thing which annoys me is that the sg device node for TapeAlert changes
> with every reboot from /dev/sg4 to /dev/sg6 and vice versa.
> Is there any setting I can set in udev to get stic
On Saturday 18 October 2014 11:01:28 Ana Emília M. Arruda wrote:
> Just a comment here. Since you have "volume use duration = 7 days" and your
> volume was used until 12:58 next day, I'm quite sure (don't know how is
> your schedule configured) that this volume will be available (append) for
> use
On Friday 17 October 2014 09:11:54 Josh Fisher wrote:
>Generally, schedules are starting jobs at the same time of day. It follows
>that the time period between successive runs will tend to be very nearly an
>integer number of days. If the use duration is also an integer number of days,
>then it
On Friday 17 October 2014 21:41:49 Ana Emília M. Arruda wrote:
> Hi Giuseppe,
>
> Yes, this could happen if bacula couldn't find a reciclable volume and you
> have the "purge oldest volume = yes" directive configured and this is, for
> Bacula, the oldest volume. The purge oldest volume doesn't res
> Consider how Bacula treats the case where "maximum volume jobs = 1". The job
> starts to run and selects a volume marked "append", possibly first recycling
> a volume if no available "append" volumes are empty. It then marks the volume
> as "used" so that no other jobs will try to select it. A
On Friday 17 October 2014 12:05:35 Ana Emília M. Arruda wrote:
> Hi Giuseppe,
>
> I would like to append some comments here about your "volume use duration"
> configuration. As the directive name says, this is used to leave the volume
> available for Bacula "during" your backup jobs (at least the
0529L4" on device "lto1"
(/dev/nlto1), all previous data lost.
This configuration of bacula had been running for quite a while without
a glitch, almost 10 months now and I had not any hardware error on my
library at the time of this job, at least for what I can see.
I ca
I can't understand why the bacula director, 5.2.13 under a stable
updated gentoo, recycled one volume "000506L4", the correct one in
the slot 9 of my changer, but instead the storage daemon recycled
the current volume mounted in drive1, from slot4, volume "000529L4"
and without actually doing any p
