> I suspect that 'job counter' get resetted if and only if all jobs in a
> volume get purged; this lead me to think that my configuration simpy does
> not work in a real situation, because sooner or later jobs get 'scattered'
> between volumes and virtual job of consolidation stop to work, so jobs and
> volume purging.
Sorry, i need feedback on that. I restate this.
Seems to me that if i use 'job based retention' on volumes, eg:
Maximum Volume Jobs = 6
on the pool, simply does not work. Because the 'job counter' on the volume
get resetted if and only if *ALL* job on that volume get purged.
If i have a volume in state 'Used' because got 6 job within, and i
purge/delete jobs but not all, media state does not switch to 'Append', and
even if i put manually in 'Append' mode, bacula reject the volume and put on
'Used' state because have reached 'Maximum Volume Jobs'.
If i delete *ALL* job in that volume, get correctly recycled.
It is right?
There's some 'knob' i can tackle with to make volume management more
'aggressive'?
Thanks.
--
dott. Marco Gaiarin GNUPG Key ID: 240A3D66
Associazione ``La Nostra Famiglia'' http://www.lanostrafamiglia.it/
Polo FVG - Via della Bontà , 7 - 33078 - San Vito al Tagliamento (PN)
marco.gaiarin(at)lanostrafamiglia.it t +39-0434-842711 f +39-0434-842797
Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA!
http://www.lanostrafamiglia.it/index.php/it/sostienici/5x1000
(cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA)
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
