 |
This one affects me as well. Currently it is impossible to use bareos in production if you have a lot of data (backup duration > 24h) and AlwaysIncremental is not working. Without getting it working with AllowDuplicateJobs=no the AlwaysIncremental feature is nearly useless. |
|
|
Just wondering if anyone has a solution to this? I'd really like to roll out Bareos for all my company's backups but this one fatal flaw in AlwaysIncremental is blocking that... |
|
|
+1 I wrote a quick and dirty patch to fix this issue. Here it is: --- a/src/dird/job.c 2017-12-14 13:57:08.000000000 +0300 +++ b/src/dird/job.c 2018-01-06 17:27:25.897508235 +0300 @@ -996,4 +996,8 @@ } + if (djcr->is_JobType(JT_CONSOLIDATE)) { + break; + } + if (cancel_dup || job->CancelRunningDuplicates) { /* |
|
|
+1 |
|
|
Is anyone from Bareos going to look at this? It's been almost a year and a half now since this was opened and not a word from the authors at all. Even just a quick yes/no on whether the above three-line patch is good or not would be appreciated because at least then I know whether it's safe to patch my local build. |
|
|
This issue definitely needs fix. I have feeling that development is directed more towards new features then bugfixes. |
|
|
Tested on 19.2.6 can confirm issue still remains, jobs are canceled as duplicates when running Consolidate jobs even if you set the consolidate job to allow duplicates as the jobs all inherit form the jobs they are consolidating from. |
|
|
FYI: We figured a configuration workaround which you could use until it is fixed. Configuration Workaround ====================== In principle we simply use an extra job for AI which is not scheduled but used by the consolidation job for the AI Cycle. The configuration workaround looks like following. We do have a normal job named "ai-backup-bareos-fd" which is automatically scheduled, one initial full backup and only incremental backups afterwards, no AI directives set in here. We introduce another backup job named "ai-backup-bareos-fd" which is NOT and NEVER automatically scheduled, it is just used by the generated Virtual Full from the Consolidation job, we'll set our AI directives in here. As the normal first initial full backup is gone after consolidation and the generated virtual full has another name (ai-backup-bareos-fd-consolidate) in comparison to the original backup job (ai-backup-bareos-fd), we simply use a run script after the job is done to rename ai-backup-bareos-fd-consolidate to ai-backup-bareos-fd. The renaming via the run after script is required so we don't get a full backup fallback when the normal backup job ai-backup-bareos-fd is scheduled again. The initial full backup has been consolidated into the virtual full as mentioned above. If you look at the jobdefs below you'll see that by this configuration we are able to use the "AllowDuplicateJobs = no" setting in normal backup jobs and "AllowDuplicateJobs = yes" for consolidation. File: /etc/bareos/bareos-dir.d/job/ai-backup-bareos-fd.conf Job { Name = "ai-backup-bareos-fd" JobDefs = "DefaultJob1" Client = "bareos-fd" Accurate = yes } File: /etc/bareos/bareos-dir.d/job/ai-backup-bareos-fd-consolidate.conf Job { Name = "ai-backup-bareos-fd-consolidate" JobDefs = "DefaultJob2" Client = "bareos-fd" Accurate = yes AlwaysIncremental = yes AlwaysIncrementalJobRetention = 1 seconds AlwaysIncrementalKeepNumber = 1 AlwaysIncrementalMaxFullAge = 1 seconds Run Script { console = "update jobid=%i jobname=ai-backup-bareos-fd" Runs When = After Runs On Client = No Runs On Failure = No } } File: /etc/bareos/bareos-dir.d/job/consolidate.conf Job { Name = "Consolidate" Type = "Consolidate" Accurate = "yes" JobDefs = "DefaultJob3" Schedule = Consolidate } File: /etc/bareos/bareos-dir.d/jobdefs/DefaultJob1.conf JobDefs { Name = "DefaultJob1" Type = Backup Level = Incremental Client = bareos-fd FileSet = "SelfTest" Storage = File Messages = Standard Pool = AI-Incremental Priority = 10 Write Bootstrap = "@working_dir@/%c.bsr" Full Backup Pool = AI-Consolidated AllowDuplicateJobs = no CancelLowerLevelDuplicates = yes CancelQueuedDuplicates = yes CancelRunningDuplicates = no Schedule = "ai-schedule" } File: /etc/bareos/bareos-dir.d/jobdefs/DefaultJob2.conf JobDefs { Name = "DefaultJob2" Type = Backup Level = Incremental Client = bareos-fd FileSet = "SelfTest" Storage = File Messages = Standard Pool = AI-Incremental Priority = 10 Write Bootstrap = "@working_dir@/%c.bsr" Full Backup Pool = AI-Consolidated AllowDuplicateJobs = yes CancelLowerLevelDuplicates = no CancelQueuedDuplicates = no CancelRunningDuplicates = no } File: /etc/bareos/bareos-dir.d/jobdefs/DefaultJob3.conf JobDefs { Name = "DefaultJob3" Type = Backup Level = Incremental Messages = "Standard" Storage = "file-storage" Pool = "Full" FullBackupPool = "Full" IncrementalBackupPool = "Incremental" DifferentialBackupPool = "Differential" Client = "bareos-fd" FileSet = "linux-server-fileset" Schedule = "WeeklyCycle" WriteBootstrap = "/var/lib/bareos/%c.bsr" Priority = 99 AllowDuplicateJobs = no SpoolAttributes = yes } File: /etc/bareos/bareos-dir.d/schedule/Consolidate.conf Schedule { Name = "Consolidate" run = at 12:00 } File: /etc/bareos/bareos-dir.d/schedule/ai-schedule.conf Schedule { Name = "ai-schedule" run = Incremental Mon-Fri at 21:00 } |
|
|
Fix committed to bareos master branch with changesetid 14803. |
- Anonymous
