Are your JOBS set to expire soon enough to recycle the tape? There are
per-job retention periods to contend with.
---- _ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | | Ryan Novosielski - User Support Spec. III
|$&| |__| | | |__/ | \| _| | [EMAIL PROTECTED] - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.| IST/AST - NJMS Medical Science Bldg - C630
Patrick Van der Veken wrote:
Kern Sibbald wrote:
On Tuesday 14 March 2006 15:34, Ryan Novosielski wrote:
Wanted to chime in here because after a long period of time spent
tinkering with Bacula, I have had my first successful automatic tape
rotation. I am running 1.38.5 at the moment, so I can say that tape
recycling really does NOT appear to be broken in 1.38.5 and if you are
having a problem it is probably misconfiguration. In my case, the reason
it was not working previously was because I was new to using incremental
tapes and was attempting to have them expire 1 day too early. Perhaps
the tape is due to be pruned when you run the command, but not due a few
mins earlier when the backup is scheduled? It helps to write out
everything on paper or -- even better -- a calendar.
Thanks. Good point. I have never been able to reproduce the problem. One
problem is that recycling is fairly sophisticated (or complicated if you
want) and probably some users are forgetting that Bacula will not recycle
a
Volume even if it is totally pruned if the Volume Retention period has not
expired ...
Hi,
Good to know it works for some. But it still does not explain why it
consistently keeps failing for us. I know *for sure* that the Volume
period has indeed expired. We have 18 tapes rotating daily with a 10 day
retention time. I have checked manually and counted (!) the days since the
"Last written" value by hand before inserting a tape and the difference is
at least 2,3 days, not seconds.
If the volume retention was not expired then why did the prune work
perfectly right before the mount request was generated? My suspicion is
that the pruning does indeed work but that the volume status update does
not happen correctly (or not fast enough). How else it possible that this
happens:
1. Start backup
2. Check tape (in status 'Used') and prune *all* jobs automatically as
volume retention has expired (because Recycle Current Volume, Autoprune
and Recycle are set)
3. Check tape (still in status 'Used')
4. Generate mount request.
5. Confirm manually the mount request (with the same tape and just seconds
later than the mount request!)
6. Backup starts on the same tape.
My err for calling this a "pruning bug". More likely a "volume update issue"?
Regards,
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
