Hi Ryan,
Ryan Novosielski wrote:
I'm fairly certain that is not actually the case. Run `llist
volume=volname`. VolUseDuration should show 16 hours in seconds,
which is 57,600. My guess is you have something else there (probably
0).
Okay, that was a excellent tip. For some bizarre reason
Ryan Novosielski wrote:
Volume retention is a minimum, not a maximum. If there is no pressing
need to recycle/prune a tape, Bacula will not (if it's still appendable,
for example). You need to limit tape usage by size/jobs/time in order
for this to work as you expect, I think.
Ok, so I should
Hi,
We use Bacula in a medium size setup, with 16 machines being backed up
to tape on a Daily Tape Rotation schedule. We're having some problems
with the volume use duration not being applied correctly and we were
wondering if anyone has any suggestions with trying to find the source
of this
The change occurs at the next attempted backup. That tape will be
suggested for use, Bacula will check the duration and see that it is
unacceptable because of the Volume Use Duration. Bacula will then use a
different tape.
_ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | |Ryan
Hi Ryan,
Okay yes that is a good point.
However, the behaviour we are seeing is that the volume is still on
status 'Append' 2 weeks later (tapes get re-used every 2 weeks). Bacula
will happily start writing to the tape, and not recycle it first, which
it should because Volume Retention is 11
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bacula will also not purge an appendable volume, as far as I know. You
need to make sure that the tape is not in a writable state prior to when
you expect it to be purged; others reading this list feel free to
correct me if I'm wrong.
Volume
