View Issue Details

IDProjectCategoryView StatusLast Update
0001161bareos-core[All Projects] directorpublic2019-12-15 22:43
ReporterembareossedAssigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
PlatformLinuxOSDebianOS Version9
Product Version18.2.5 
Fixed in Version 
Summary0001161: JobId 0: Prior failed job found in catalog. Upgrading to Differential.
DescriptionDifferential backups always produce this error. It is confusing on two counts: 1) Scheduled differential backups should not generate this message since the backup is scheduled to be differential, and 2) Message does not indicate which backup is being (falsely) "upgraded." Since I have 5 differential jobs every week (except once a month when full backups are run), there are exactly 5 of these messages, so apparently such message is generated for each differential job.
Steps To ReproduceSchedule differential jobs. One such message will be generated for each job.

NB: My backup schedule is identical for all backup jobs. I have it set to perform monthly full backups, then differentials once a week, and incrementals all other days.
Additional InformationI am simply following the model offered in the documentation, so I assumed that this was a valid, workable approach.

These messages show up in separate emails from the backup emails.
TagsNo 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

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2019-12-15 22:43 embareossed New Issue