View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001143 | bareos-core | director | public | 2019-11-26 12:09 | 2019-11-26 12:13 |
| Reporter | joergs | Assigned To | |||
| Priority | low | Severity | feature | Reproducibility | have not tried |
| Status | confirmed | Resolution | open | ||
| Product Version | 19.2.4~pre | ||||
| Summary | 0001143: Update a Job to Accurate instead of Full backup on FileSet changes. | ||||
| Description | Currently (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.) | ||||
| Tags | No tags attached. | ||||
| 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 | |||||
| related to | 0001115 | closed | changing onefs value in fileset should force a full backup |
