 |
Seems you miss the max-full-consolidations parameter https://docs.bareos.org/TasksAndConcepts/AlwaysIncrementalBackupScheme.html#max-full-consolidations |
|
|
That is the full, but it's the total number that can be a problem on the disk... If you have 200 servers (example), the running 20 consolidations at the same time is still too heavy even if they are not full... It's reading and writing at same time. While regular backups may suffer from lower network speeds and writing only, they concurring number can be way higher! |
|
|
For that purpose, normally you will adapt the number of device so running 20 consolidations at the same time will require 10 read and 10 writer device. Usually the job being incrementals the consolidation is fast. So I'm sorry but without any PR code proposal, we don't see things changing here. Would you mind to propose a code change in a PR, otherwise I will just close here with won't fix. If you want to see that implemented by Bareos, then I suggest you contact our sales team for a quote. |
|
|
won't fix without community code proposal PR on github. |
- Anonymous
