Misleading "Ignoring incremental Backupset" message

Bug #1512055 reported by Tobias G. Pfeiffer
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Duplicity
New
Undecided
Unassigned

Bug Description

For a while I have been doing my duplicity backups to Glacier now. First I used a kind of hack to do a normal AWS upload, then rename all the difftar files to match S3 lifecycle rules. Using that method, I got "Ignoring incremental Backupset" messages on subsequent backups, maybe because there were no data files found using the expected file name pattern.

Then recently I upgraded to the latest duplicity version and switched to the `--file-prefix-archive` method, which feels a lot better. However, I still had the "Ignoring incremental Backupset" message in my logs which confused me a bit, since all commands seem to behave correctly. I found out that when an incremental backupset is found, `chain.add_inc(set)` is called on all chains until one of these calls returns True, and every call before will emit an "Ignoring incremental Backupset" message. So the very normal operation of "finding the correct chain" emits a message that indicates something is ignored or missing or not matching etc.

I think the functionality of finding the correct chain should be changed so that no such warning message is emitted in order to avoid user confusion.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.