On Sat, 18 Oct 2014 20:05:34 +0200, Giuseppe Vitillaro said:
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
I change my tape library volumes every friday, so I have an Admin Job that
do an update slots every friday night. It is working fine for me.
Regards,
Ana
On Mon, Oct 20, 2014 at 7:14 AM, Martin Simmons mar...@lispworks.com
wrote:
On Sat, 18 Oct 2014 20:05:34 +0200, Giuseppe Vitillaro said:
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. After it is
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 respect
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 can
Yes, the default for purge oldest volume is no.
So you have just two volumes in this pool. As Kern said Yes, there can be
typically a few seconds delay between when a volume is chosen for use and
when it expires. and this could be the issue you are facing.
Maybe another thing additionally Josh's
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 in the next week by your backup jobs. Because of your volume use
duration
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 in
Hi Giuseppe,
I think there is a misunderstanding here. You are talking about two
different jobs. From your first post, you talked about the
Job=Fs02Home.2014-10-13_21.00.00_33
and this last post you are talking about Job=MccwHome.2014-10-13_21.00.
00_34.
13-Oct 21:00 bl13-dir JobId 1761: Start
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
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
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
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 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 ones you
On 10/17/2014 12:29 PM, Giuseppe
Vitillaro wrote:
On Friday 17 October 2014 12:05:35 Ana Emlia
M. Arruda wrote:
Hi Giuseppe,
I would like to append some comments
here about your "volume use duration"
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, 2014
Apologies for appending to my own post, but I found
another occurence of the same pattern, I didn't notice,
in another job of some months ago, again attached to
this message. The same volumes are involved, and these,
for what I can see from my logs, are the only occurences
of the pattern.
It
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
18 matches
Mail list logo
