| Thanks, it was a real bug. I was starting to wonder if the time specification had changed or I was doing something else wrong. That patch make sense. Just wringing out version 2.X.X!
-Scott
Note: I have a slightly different file to patch. This is what I changed, I assume you are working from newer source.
if not config.restart and action in ["inc", "backup"] and config.full_if_older_than is not None and \ last_full_time < dup_time.curtime - config.full_if_older_than: log.Notice(_("Last full backup is too old, forcing full backup")) action = ""
On Oct 14, 2023, at 2:55 PM, Kenneth Loafman <kenneth@loafman.com> wrote:
Regrettably, yes, but fixed now in the source. A one line patch.
...Ken
diff --git a/duplicity/dup_main.py b/duplicity/dup_main.py
--- a/duplicity/dup_main.py (revision c790ab52eb0393cdff22cbdd9a06389eb99792dd)
+++ b/duplicity/dup_main.py (revision d2bdb824d6c04907ab982c04eea0380b21b91518)
@@ -1629,7 +1629,7 @@
not config.restart
and action in ["inc", "backup"]
and config.full_if_older_than is not None
- and last_full_time < config.full_if_older_than
+ and last_full_time < dup_time.curtime - config.full_if_older_than
):
log.Notice(_("Last full backup is too old, forcing full backup"))
action = ""
Duplicity 2.1.3 / MacOS 13.6
Duplicity seems to be working and backing up incremental fixes. However I was trying to force a new full backup by reducing the time to trigger a full backup. The incremental backup seems to be working (at least for the last 3 days now that I rebuilt duplicity). Note the "--full-if-older-than 1D” flag which should be triggered since the last full backup was 9/23/2023. After updating requests all those warnings about version mismatch went away.
Here is the command line I used:
nice -n19 /opt/sw/bin/duplicity backup --full-if-older-than 1D --num-retries 5 --tempdir /var/tmp/duplicity --volsize 500 --encrypt-key ZZZZZ --sign-key
WWWWW --gpg-binary /opt/sw/bin/gpg --gpg-options=--default-key=VVVVVV --force --verbosity Notice --allow-source-mismatch
<bunch of excludes delete>
—s3-endpoint-url https://YYYYY /Users/sth/Documents s3://XXXXX/documents
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Sat Sep 23 01:10:06 2023
--------------[ Backup Statistics ]--------------
StartTime 1697260209.03 (Sat Oct 14 01:10:09 2023)
EndTime 1697260354.12 (Sat Oct 14 01:12:34 2023)
ElapsedTime 145.09 (2 minutes 25.09 seconds)
SourceFiles 503626
SourceFileSize 119490403344 (111 GB)
NewFiles 52
NewFileSize 409904 (400 KB)
DeletedFiles 1
ChangedFiles 4
ChangedFileSize 135430603 (129 MB)
ChangedDeltaSize 0 (0 bytes)
DeltaEntries 57
RawDeltaSize 135760518 (129 MB)
TotalDestinationSizeChange 136639824 (130 MB)
Errors 0
-------------------------------------------------
And here is the status report for the repository. It seems to me that the last full backup was certainly longer than 1 day.
Found primary backup chain with matching signature chain:
-------------------------
Chain start time: Sat Sep 23 01:10:06 2023
Chain end time: Sat Oct 14 01:10:07 2023
Number of contained backup sets: 5
Total number of contained volumes: 210
Type of backup set: Time: Num volumes:
Full Sat Sep 23 01:10:06 2023 200
Incremental Thu Sep 28 01:10:09 2023 3
Incremental Thu Oct 12 01:10:13 2023 5
Incremental Fri Oct 13 01:10:11 2023 1
Incremental Sat Oct 14 01:10:07 2023 1
-------------------------
No orphaned or incomplete backup sets found.
-Scott
_______________________________________________
Duplicity-talk mailing list
Duplicity-talk@nongnu.org
https://lists.nongnu.org/mailman/listinfo/duplicity-talk
|