Duplicity

Duplicity fails to add incremental backups to chain (Ignoring incremental Backupset)

Bug #885670 reported by Ivan Gromov
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Duplicity
Fix Released
Critical
Unassigned
Duplicity 0.6.17

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

lp://qastaging/~summer-is-gone/duplicity/tz-incremental-fix
Kenneth Loafman: Pending requested
Diff: 122 lines (+45/-24)
2 files modified
duplicity/dup_time.py (+15/-8)
testing/dup_timetest.py (+30/-16)
Revision history for this message
Dmitry Fedoseev (dmitry-fedoseev) wrote :

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.

Revision history for this message
megari (megari-mbnet) wrote :

I wonder if this is related to bug #881727?

Revision history for this message
megari (megari-mbnet) wrote :

I am seeing similar messages in duplicity's output when running with -v9.

Ignoring incremental Backupset (start_time: Mon Aug 8 17:17:14 2011; needed: Mon Aug 8 02:51:33 2011)
Ignoring incremental Backupset (start_time: Mon Aug 15 01:03:29 2011; needed: Mon Aug 8 02:51:33 2011)
Ignoring incremental Backupset (start_time: Mon Aug 15 03:20:23 2011; needed: Mon Aug 8 02:51:33 2011)
Ignoring incremental Backupset (start_time: Mon Aug 22 03:10:32 2011; needed: Mon Aug 8 02:51:33 2011)
Ignoring incremental Backupset (start_time: Mon Aug 29 02:42:40 2011; needed: Mon Aug 8 02:51:33 2011)
Ignoring incremental Backupset (start_time: Tue Sep 13 04:00:14 2011; needed: Mon Aug 8 02:51:33 2011)
Ignoring incremental Backupset (start_time: Mon Sep 19 03:11:19 2011; needed: Mon Aug 8 02:51:33 2011)
Ignoring incremental Backupset (start_time: Sun Sep 25 23:39:14 2011; needed: Mon Aug 8 02:51:33 2011)
Ignoring incremental Backupset (start_time: Mon Oct 3 01:51:53 2011; needed: Mon Aug 8 02:51:33 2011)
Ignoring incremental Backupset (start_time: Mon Oct 10 00:50:22 2011; needed: Mon Aug 8 02:51:33 2011)
Ignoring incremental Backupset (start_time: Mon Oct 17 03:48:49 2011; needed: Mon Aug 8 02:51:33 2011)

This might suggest this bug is indeed a duplicate of bug #881727.

Revision history for this message
Dmitry Fedoseev (dmitry-fedoseev) wrote :

It looks like this bug is related to #881727 very close, but there was no duplicity related updates on Debian Squeeze theese days - current version is 0.6.08b.

There is bug in duplicity.dup_time module:
>>> from duplicity import dup_time
>>> import time
>>> t = int(time.time())
>>> dup_time.stringtotime(dup_time.timetostring(t))-t
-3600L

Ivan's patch fixes it.

Kenneth Loafman (kenneth-loafman)
Changed in duplicity:
status: New → Fix Committed
milestone: none → 0.6.17
Kenneth Loafman (kenneth-loafman)
Changed in duplicity:
importance: Undecided → Critical
Kenneth Loafman (kenneth-loafman)
Changed in duplicity:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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