View Issue Details

IDProjectCategoryView StatusLast Update
0000958bareos-core[All Projects] Generalpublic2020-02-17 04:30
ReporterMarceloRuizAssigned To 
PriorityhighSeveritymajorReproducibilityhave not tried
Status newResolutionopen 
PlatformLinuxOSUbuntuOS Version18.04
Product Version17.2.5 
Fixed in Version 
Summary0000958: Always incremental backups always upgraded to full
DescriptionAfter upgrading bareos from 16.2 to version 17.2, each "always incremental" backup job is upgraded to a full backup. This happens all the time and the unmodified configuration used to work fine with 16.2.
Client: Ubuntu 18.04
Server (Director, Storage Daemon): FreeNas 11.1 (Freebsd 11.1-RELEASE-p10)
Steps To ReproduceOn a fresh installation, create an always incremental job. The job will be upgraded to full during the first backup (expected) and subsequent ones (not expected).
Additional InformationI figured maybe the script that upgraded the tables had a problem, so I dropped the whole database and recreated it again and reset bareos to zero (deleting all the stored data and status on every single component including the 2 clients I have). In this way I ruled out problems with the upgrade from one version to another, but the problem remains.
Looking at the logs I see the confirmation the first full backup upgraded from incremental finished with status OK, but the following same job (which should run as incremental) is upgraded "from Full to Full" and the reason is that a prior failed full job was found in the catalog, but the database table has the right information for the OK status.
I am attaching a sanitized version of the log file with the two Job Ids involved. The rest of the logs belong to the second client failing jobs (that on purpose I turned off) to see what was going on more easily.
Tagsalways incremental, freebsd
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




2018-06-01 16:22


bareos.log (6,342 bytes)


2020-02-17 04:30

reporter   ~0003818

Problem still present in version 19.2.6 and Postgres 11.
The message: "Prior failed job found in catalog. Upgrading to Full." is not very helpful. At least it should show the previous JobId its referencing to and the job status (in my latest test it will show that the JobID is 1 and the status is T).
Is there any way to debug this behavior?

Issue History

Date Modified Username Field Change
2018-06-01 16:22 MarceloRuiz New Issue
2018-06-01 16:22 MarceloRuiz File Added: bareos.log
2020-02-17 04:23 MarceloRuiz Tag Attached: always incremental
2020-02-17 04:23 MarceloRuiz Tag Attached: freebsd
2020-02-17 04:30 MarceloRuiz Note Added: 0003818