Hey Lloyd,

Am 09.11.2026 um 18:12 schrieb Lloyd Brown via Bacula-users:
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.

If I understand things correctly, there is a lot of processing and optimization of the bootstrap records needed to implement copy, migration and virtual backups. (I would assume the same applies to restores as well). A Storage Daemon needs to track what records it has already visited while reading data, and for performance reasons, that tracking of bootstrap file entries has been optimized to only be able to see each volume once.

When working with file / disk based storage, where Devices and Volumes are more or less available for free, this is usually easily solved, but it gets tricky with tape when you are limited by the number of tape drives.

A year ago, the solution I often suggested was to invest in a few more disks, but these days, the eyewatering prices of storage make this a bit inconvenient.

Anyway, short summary answer: For purely technical reasons, because we swapped a relatively easily circumvented functionality limitation against inacceptable performance degradation without workaround.

Cheers,

Arno

--
Arno Lehmann

IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück



_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to