View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001377 | bareos-core | director | public | 2021-08-10 23:30 | 2023-03-22 10:11 |
Reporter | hostedpower | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | reopened | ||
Platform | Linux | OS | Debian | OS Version | 10 |
Product Version | 20.0.2 | ||||
Summary | 0001377: Cannot set max number of jobs for consolidations | ||||
Description | Hi, We set the server to backup up to 20 clients at the same time in order to get maximum network speed. However this means also 20 concurrent consolidations will be done later on. The consolidation is a very heavy process, not to compare with just synching data to the backup server with normal backups. We really need a separate option to limit the max concurrent consolidations that can be run at the same time :) Setting the job max to for example 5 doesn't seem to work, probably because there is only "1" consolidate job. | ||||
Tags | No tags attached. | ||||
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. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2021-08-10 23:30 | hostedpower | New Issue | |
2023-03-21 17:40 | bruno-at-bareos | Assigned To | => bruno-at-bareos |
2023-03-21 17:40 | bruno-at-bareos | Status | new => closed |
2023-03-21 17:40 | bruno-at-bareos | Resolution | open => no change required |
2023-03-21 17:40 | bruno-at-bareos | Note Added: 0004921 | |
2023-03-21 21:01 | hostedpower | Status | closed => new |
2023-03-21 21:01 | hostedpower | Resolution | no change required => reopened |
2023-03-21 21:01 | hostedpower | Note Added: 0004923 | |
2023-03-22 10:10 | bruno-at-bareos | Note Added: 0004926 | |
2023-03-22 10:11 | bruno-at-bareos | Assigned To | bruno-at-bareos => |
2023-03-22 10:11 | bruno-at-bareos | Status | new => closed |
2023-03-22 10:11 | bruno-at-bareos | Note Added: 0004927 |