|
From: | Trevor Hemsley |
Subject: | [Duplicity-tracker] [bug #24027] --full-if-older-than uses end time of backup not start time |
Date: | Fri, 08 Aug 2008 16:38:31 +0000 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.16) Gecko/20080702 Firefox/2.0.0.16 |
URL: <http://savannah.nongnu.org/bugs/?24027> Summary: --full-if-older-than uses end time of backup not start time Project: duplicity Submitted by: trevorph Submitted on: Friday 08/08/08 at 16:38 Category: None Severity: 3 - Normal Item Group: None Status: None Privacy: Public Assigned to: None Originator Email: Open/Closed: Open Discussion Lock: Any _______________________________________________________ Details: If you use the --full-if-older-than 7D parameter to duplicity to perform backups then the time is calculated from the end time of the previous backups not from the start time. For example, if you have a duplicity run in crontab scheduled for 00:01:00 and it takes 8 hours to run, then a duplicity run on the same day the following week using --full-if-older-than 7D will not perform a new full backup because 7 days have not elapsed since the end of the last full backup. This means that your scheduled backups will wander around the week. It should either calculate the time from the start of the last full backup or it should be documented that 7D really means 8! _______________________________________________________ Reply to this item at: <http://savannah.nongnu.org/bugs/?24027> _______________________________________________ Message sent via/by Savannah http://savannah.nongnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |