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.
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 ***
--
Lloyd Brown
HPC Systems Administrator
Office of Research Computing
Brigham Young University
http://rc.byu.edu
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users