On 11/10/26 10:20 AM, Lloyd Brown via Bacula-users wrote:
The difficulty here is that, if we use one of the tools to keep no
more than one job per disk volume (eg. `Maximum Volume Jobs=1` or
`Volume Use Duration=N` where N is less than the normal job cycle), we
end up with smaller disk files, and more of them. In this or similar
circumstances, how do people control their disk pools to prevent them
from filling up?
I don't think that is necessary. The important thing is that there not
be multiple volumes that the incremental job can write to at any single
point in time. For example, if there is a pool of available volumes for
JOB_1 and multiple drives on which they can be loaded, such as when
using a virtual disk autochanger, then JOB_1 may select VOLUME_1 and
Monday, then on Tuesday other simultaneously running jobs may force
JOB_1 to select Volume_2 on Tuesday, then go back to writing on VOLUME_1
and Wednesday. The incremental jobs will run fine, but a virtual full
will not be possible.
One solution is to assign each job its own pool for incremental jobs.
This ensures that the job keeps writing to the same volume as long as it
is active, then never reuses it until after it is recycled.
Another way is to limit volume use to 1 day (assuming you don't run
incrementals more often), which also prevents a previously used volume
from being used again after another volume is used, but in a different way.
In the past (eg. Bacula 9.6.x, where VF worked great, BTW), I've used
a combination of `Maximum Volume Bytes` and `Maximum Volumes`. I
can't use the `Maximum Pool Bytes`, since that seems to only be
available for Bacula Enterprise. Therefore what? I just have to
guess the oversubscription ratio, and hope I'm right?
On 11/10/26 00:59, Eric Bollengier wrote:
Hello Lloyd,
On 11/9/26 18:12, Lloyd Brown via Bacula-users wrote:
Can anyone explain the reasoning behind the volume cycle detection
for VirtualFulls in Bacula 15.0.3? I'm running into problems like
what's shown below, and it's not clear to me why it's a problem.
I understand that the VF code doesn't like to go back to a
previously-read volume, and that triggers this behavior. What I'm
struggling to understand is why it's a problem to revisit a volume.
This is a limitation of Bacula, we read volume per volume
(optimisation as Arno
mentioned), and if a volume is used multiple times with other volumes
in the
middle, the virtual full is not possible.
Ensure that your disk volume are used once per specific job, and
everything
will be fine.
Hope it helps,
Best Regards,
Eric
07-Nov 17:05 backupdir-dir JobId 2671: Start Virtual Backup JobId
2671, Job=backupworker1job.2026-11-07_17.05.00_06
07-Nov 17:05 backupdir-dir JobId 2671: Consolidating
JobIds=2355,2378,2395,2424,2440,2476,2489,2507,2543,2566,2595,2614,2646,2660
07-Nov 17:05 backupdir-dir JobId 2671: Found 88360 files to
consolidate into Virtual Full.
07-Nov 17:05 backupdir-dir JobId 2671: Fatal error: Found a volume
cycle in the bootstrap, Virtual Full is not possible on this Job
07-Nov 17:05 backupdir-dir JobId 2671: Error: Bacula backupdir-dir
15.0.3 (25Mar25):
Build OS: x86_64-pc-linux-gnu redhat (Green
JobId: 2671
Job: backupworker1job.2026-11-07_17.05.00_06
Backup Level: Virtual Full
Client: "backupworker1-fd" 15.0.3 (25Mar25)
x86_64-pc- linux-gnu,debian,trixie/sid
FileSet: "backupworker-set" 2026-09-30 15:23:02
Pool: "Disk-granite2" (From Run NextPool
override)
Catalog: "MyCatalog" (From Client resource)
Storage: "granite2-sd-disk" (From Run NextPool
override)
Scheduled time: 07-Nov-2026 17:05:00
Start time: 07-Nov-2026 17:00:04
End time: 07-Nov-2026 17:00:09
Elapsed time: 1 sec
Priority: 10
SD Files Written: 0
SD Bytes Written: 0 (0 B)
Rate: 0.0 KB/s
Volume name(s):
Volume Session Id: 0
Volume Session Time: 0
Last Volume Bytes: 0 (0 B)
SD Errors: 0
SD termination status:
Termination: *** Backup Error ***
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users