View Issue Details

IDProjectCategoryView StatusLast Update
0001143bareos-coredirectorpublic2023-09-05 16:48
Reporterjoergs Assigned Tobruno-at-bareos  
PrioritylowSeverityfeatureReproducibilityhave not tried
Status closedResolutionwon't fix 
Product Version19.2.4~pre 
Summary0001143: Update a Job to Accurate instead of Full backup on FileSet changes.
DescriptionCurrently (19.2.4) changes to the File directive in a FileSet result that the next backup job is upgraded to a Full backup, see https://docs.bareos.org/master/Configuration/Director.html#fileset-resource.

It has several disadvantages:
  * The job is only upgraded on changes to the File directive. Changes to the options, which may also result into a different fileset are not covered.
  * Even if the fileset does only include one file more (or in effect does not change anything, as the path do not exist), all files would be backed up again.
  * If your backup uses the Accurate option, upgrade to Full is not even required.

A better solution would be to upgrade a backup to an Accurate backup instead of a Full backup.
This has the same benefits like an upgrade to a Full backup (not missing any newly included files),
but instead instead of a Full backup, it does not backup all files again, but only the changed and newly added files (or mark removed files as removed).

Also a Accurate job produces more load on the network and on the client than a normal Incremental job, however, much less than a Full backup.

An further improvement would be to upgrade a Job on any change to a fileset. The current behavior does not cover all relevant cases (e.g. switching OneFS from on to off may result in a lot more files to backup. However, these files will no be covered by an Incremental Non-Accurate job.)
TagsNo tags attached.

Relationships

related to 0001115 closed changing onefs value in fileset should force a full backup 

Activities

bruno-at-bareos

bruno-at-bareos

2023-09-05 16:48

manager   ~0005383

After 4 years, this issue doesn't find the PR which would fix it.

Issue History

Date Modified Username Field Change
2019-11-26 12:09 joergs New Issue
2019-11-26 12:10 joergs Relationship added related to 0001115
2019-11-26 12:12 joergs Status new => confirmed
2019-11-26 12:13 joergs Product Version => 19.2.4~pre
2023-09-05 16:48 bruno-at-bareos Assigned To => bruno-at-bareos
2023-09-05 16:48 bruno-at-bareos Status confirmed => closed
2023-09-05 16:48 bruno-at-bareos Resolution open => won't fix
2023-09-05 16:48 bruno-at-bareos Note Added: 0005383