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 respect the
volume retention period.
Best regards,
Ana
On Fri, Oct 17, 201
On 10/17/2014 12:29 PM, Giuseppe
Vitillaro wrote:
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"
> co
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
Try running the "List Volumes used by selected JobId" query command for those
jobs with JobStatus = T.
__Martin
> On Tue, 14 Oct 2014 11:11:03 +0100, ALI LARAB said:
>
> Yes, I have used the purge commande. Two days after sending my mail, the
> available space was decrised to 1%. No space
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 ones you want
the data goes to that volume). Maybe you are having volume
On 10/17/2014 7:05 AM, Kern Sibbald
wrote:
Hello,
I have not seen your original post so I respond only to comments
you mention below without understanding the full issue. Yes,
there can be typically a few seconds delay betwee
All the messages that you show below seem to be very consistent with the
way that Bacula does/did pruning in version 5.2.x. To know exactly why
it chose to recycle a particular volume, you would have to look in
detail at the Volume information just before it was recycled. During
the pruning p
There is nothing I know in Bacula that specifically restricts concurrent
read jobs on a storage device. If you use defaults, read/write are
treated the same and are limited to maximum values configured. It is
possibly, however, to restrict the number of simultaneous read jobs (at
least in vers
Hello,
I have not seen your original post so I respond only to comments you
mention below without understanding the full issue. Yes, there can be
typically a few seconds delay between when a volume is chosen for use
and when it expires. The use duration is only checked when the volume
is fi
