View Issue Details

IDProjectCategoryView StatusLast Update
0001090bareos-core[All Projects] directorpublic2019-07-09 11:40
ReporterBurningKarlAssigned To 
Status feedbackResolutionopen 
PlatformLinuxOSCentOSOS Version7
Product Version17.2.7 
Fixed in Version 
Summary0001090: Consolidation does not include empty incrementals for Always Incremental Backup Scheme
DescriptionWhen using the Always Incremental Backup Scheme for a folder that never (in reality: only very rarely) changes, empty incremental backup jobs are produced and they are never consolidated with the last Full backup. This causes two problems:
1) The empty Incremental Backup Jobs are never pruned, when you rely on volume retention and don't specify a job retention period.
2) The last full backup does not change and (at some point) will be pruned, because it exceeds the volume retention period. At this point a complete Full Backup is necessary and the advantages of the Always Incremental Backup Scheme are lost.
Steps To ReproduceCreate a new Always Incremental Backup Job on a folder that does not change and setup a corresponding Consolidate job. Only set up the Volume Retention period and Auto Prune in the pool resource, but don't use Auto Prune in the client resource. After a while the problems above will show up.
Additional InformationThis behavior seems to be a fix to issue 0000793, but it is rather counter-intuitive to the idea of Always Incremental.

Temporary fixes I can think of:
1) Set the Job Retention period of the AI-Incremental pool to match the Volume Retention period and prune regularly.
2) Set the Volume Retention period for AI-Consolidated pool to a extremely high value or disable Auto Prune for this pool, because normally no job in this pool should be pruned.
Tagsalways incremental
bareos-master: impact
bareos-master: action
bareos-19.2: impact
bareos-19.2: action
bareos-18.2: impact
bareos-18.2: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action




2019-07-09 11:40

developer   ~0003423

Could you please try to reproduce the issue with the latest nightly-build:

Issue History

Date Modified Username Field Change
2019-06-06 22:54 BurningKarl New Issue
2019-06-06 22:54 BurningKarl Tag Attached: always incremental
2019-07-09 11:40 arogge Status new => feedback
2019-07-09 11:40 arogge Note Added: 0003423