|
From: Dan L. <da...@la...> - 2025-03-05 02:48:44
|
On Mon, Mar 3, 2025, at 11:43 AM, Bill Arlofski via Bacula-users wrote: > On 3/3/25 9:34 AM, Udo Kaune wrote: >> Am 02.03.25 um 20:56 schrieb Dan Langille: >>> 02-Mar 19:06 bacula-sd-04 JobId 373736: Recycled volume "FullAuto-04-15375" on File device "vDrive-FullFile-4" (/usr/local/bacula/volumes/FullFile), all previous data lost. >>> 02-Mar 19:06 bacula-dir JobId 373736: Max Volume jobs=1 exceeded. Marking Volume "FullAuto-04-15375" as Used. >> Hi Dan, >> >> Are we looking in the right direction? Why is the volume tagged as "Used" immediately after the purge? Is this the expected >> behaviour? >> >> Regards, Udo >> > > > Hello Udo, > > yes, this is normal behavior when a Pool has `MaximumVolumeJobs = 1` > set. AS soon as a volume is ready for use, Bacula marks > it in the catalog as `Used` so that no other jobs can be written to it, > even if the writing device > has `MaximumConcurrentJobs = <a number greater than 1>` Yes, confirming, this is my configuration. :) -- Dan Langille da...@la... |