>>>>> On Fri, 24 May 2024 10:39:06 +0200, Marco Gaiarin said: > > > 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?
Yes, that is how volumes work. Bacula can only append at the end of a volume, so the volume size would increase forever if it could switch back to Append after purging some jobs. To reuse a volume, it needs to be recycled, which only happens when all jobs have been purged. > There's some 'knob' i can tackle with to make volume management more > 'aggressive'? I think you need to configure it somehow to put all jobs with the same lifetime on the same volumes, so they can all expire at the same time and those volumes will then be recycled. __Martin _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
