Hello Josh,

On 11/11/26 18:36, Josh Fisher via Bacula-users wrote:


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.

Thanks for the example, it's a little bit more complicated, but the spirit is
here. The first job is on Volume1, if the second job starts on Volume2, fill it
up, and switch back to Volume1 to finish, we end up with a cycle, one file might be spread between the two volumes, and this is causing the cycle.

This is a rare case and restore jobs will handle the situation automatically.
The BSR handling part is working pretty well and is one of the most critical
piece of Bacula, I have ideas to solve this issue but no time for the moment.

The configuration can prevent this problem, and if it's important, it is
possible to migrate the jobs that are creating the loop to an other set of
volumes to fix the situation and restart the VF.

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.



Thanks to use Bacula,

Best Regards,
Eric



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

Reply via email to