Duplicity fails to add incremental backups to chain (Ignoring incremental Backupset)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Critical
|
Unassigned |
Bug Description
Duplicity version: trunk
Python version: 2.6
OS Distro and version: Debian squeeze
Type of target filesystem: Linux
Log output from -v9 option:
...
Ignoring incremental Backupset (start_time: Wed Nov 2 02:50:03 2011; needed: Wed Nov 2 03:50:03 2011)
...
Detailed description:
Only full backups are created. When I tried to create incremental backup with duply, everything seems fine, but incremental backups are not added to chain. Verbose logs show error line:
Ignoring incremental Backupset (start_time: Wed Nov 2 02:50:03 2011; needed: Wed Nov 2 03:50:03 2011)
The problem appeared after updating tzdata. My time zone is YEKT.
I use duplicity backups on all company servers and have a *lot* of frustration about this bug.
Related branches
- Kenneth Loafman: Pending requested
-
Diff: 122 lines (+45/-24)2 files modifiedduplicity/dup_time.py (+15/-8)
testing/dup_timetest.py (+30/-16)
Changed in duplicity: | |
status: | New → Fix Committed |
milestone: | none → 0.6.17 |
Changed in duplicity: | |
importance: | Undecided → Critical |
Changed in duplicity: | |
status: | Fix Committed → Fix Released |
To be exact, incremental backups were created, but later on reported as orphaned on any operation and cleaned up on CLEANUP.
Probably error was caused by tzdata update from 2011d to 2011k. Inclemental backups created before update are still usable.