Author: Giuseppe Vitillaro <giuseppe AT vitillaro DOT org>
Date: Wed, 15 Oct 2014 11:57:51 +0200
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
Author: Giuseppe Vitillaro <giuseppe AT vitillaro DOT org>
Date: Fri, 17 Oct 2014 01:28:58 +0200 (CEST)
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 inv
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
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 hav
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
Author: Ana Emília M. Arruda <emiliaarruda AT gmail DOT com>
Date: Fri, 17 Oct 2014 12:05:35 -0300
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
Author: Giuseppe Vitillaro <giuseppe AT vitillaro DOT org>
Date: Fri, 17 Oct 2014 18:29:38 +0200
The volume 000529L4 had status "Append" at the time the jobs started, then moved to status "Used", at the time of the "mount". Beside that the volume 000529L4 was written the day before the run, has
On 10/17/2014 12:29 PM, Giuseppe Vitillaro wrote: On Friday 17 October 2014 12:05:35 Ana Emília M. Arruda wrote: here about your "volume use duration" says, this is used to leave the volume ba
Author: Ana Emília M. Arruda <emiliaarruda AT gmail DOT com>
Date: Fri, 17 Oct 2014 21:41:49 -0300
The volume 000529L4 had status "Append" at the time the jobs started, then moved to status "Used", at the time of the "mount". Beside that the volume 000529L4 was written the day before the run, ha
Author: Giuseppe Vitillaro <giuseppe AT vitillaro DOT org>
Date: Sat, 18 Oct 2014 10:21:03 +0200
The reason for which bacula marks "used" the volume 000529L4 "after" the job started is clear and for me would be perfectly acceptable if the jobs continue to write on this volume for this particula
Author: Giuseppe Vitillaro <giuseppe AT vitillaro DOT org>
Date: Sat, 18 Oct 2014 10:57:54 +0200
I was almost sure, but I just "grepped" all my bacula conf file. I'm sure the directive "purge oldest volume" is not present in my files, so the default, for what I can read, should be a plain "no".
Author: Giuseppe Vitillaro <giuseppe AT vitillaro DOT org>
Date: Sat, 18 Oct 2014 11:13:14 +0200
Beside understanding the reason why the storage daemon recycled a non empty volume, you advice seems to go in the direction to minimime the probability this accident, use duration expiring at the beg
Author: Ana Emília M. Arruda <emiliaarruda AT gmail DOT com>
Date: Sat, 18 Oct 2014 10:14:01 -0300
I was almost sure, but I just "grepped" all my bacula conf file. I'm sure the directive "purge oldest volume" is not present in my files, so the default, for what I can read, should be a plain "no"
Author: Ana Emília M. Arruda <emiliaarruda AT gmail DOT com>
Date: Sat, 18 Oct 2014 11:01:28 -0300
I was almost sure, but I just "grepped" all my bacula conf file. I'm sure the directive "purge oldest volume" is not present in my files, so the default, for what I can read, should be a plain "no"
Author: Giuseppe Vitillaro <giuseppe AT vitillaro DOT org>
Date: Sat, 18 Oct 2014 20:05:34 +0200
It didn't used the volume incorrectly recyled, 000529L4, bacula storage daemon just recycled it, marked as used and proceeded, correctly to backup on 000506L4 after a manual intervention. The manual
Author: Ana Emília M. Arruda <emiliaarruda AT gmail DOT com>
Date: Sat, 18 Oct 2014 23:59:09 -0300
It didn't used the volume incorrectly recyled, 000529L4, bacula storage daemon just recycled it, marked as used and proceeded, correctly to backup on 000506L4 after a manual intervention. The manua
Author: Martin Simmons <martin AT lispworks DOT com>
Date: Mon, 20 Oct 2014 11:14:09 +0100
The media.InChanger field tells the Director which tapes are in the changer, so maybe that was set incorrectly? Also, check that the Storage definition in the Director's bacula-dir.conf contains Aut
Author: Ana Emília M. Arruda <emiliaarruda AT gmail DOT com>
Date: Mon, 20 Oct 2014 10:10:40 -0300
The media.InChanger field tells the Director which tapes are in the changer, so maybe that was set incorrectly? Also, check that the Storage definition in the Director's bacula-dir.conf contains Aut