|
From: | Kenneth Loafman |
Subject: | Re: [Duplicity-talk] Resume backup after failed attempt |
Date: | Fri, 25 Feb 2022 11:31:50 -0600 |
Hi Ken,I use duplicity-0.8.21 and Python 3.9.5. The command is `duply data1 backup` which extends to:eval TMPDIR='/tmp' duplicity --name duply_data1 --no-encryption --verbosity '4' --exclude-filelist .duply/data1/exclude /PHShome/tb571/tmp/my_dir 's3+http://data1'Now I am thinking about your mention of serious problem: if s3 remote rejects a put request for being larger than 5 GB, do the manifest and sigtar remain corrupted in ~/.cache/duplicity/duply_data/ directory? For what it is worth, I am testing duplicity on 1 TB data with 2 GB volsize. Everything seems to have worked fine until the last sigtar which is 7.5 GB.Best,
TashrifOn Fri, Feb 25, 2022 at 11:39 AM Kenneth Loafman <kenneth@loafman.com> wrote:Hi Tashrif,What command line did you use? What's the version of duplicity? of Python?Normally duplicity will restart with the last full difftar vol sent to the remote. You can tell that by looking at the log file. If there was a serious problem, i.e. corruption in the manifest or sigtar, then duplicity will restart from the beginning....KenOn Thu, Feb 24, 2022 at 10:14 PM Tashrif via Duplicity-talk <duplicity-talk@nongnu.org> wrote:Hi all,_______________________________________________For whatever reason, my duply backup failed towards the very end. I see many *vol1.difftar.gz in my s3 bucket but I do not see the two familiar files:duplicity-full-signatures.20220218T171052Z.sigtar.gz
duplicity-full.20220218T171052Z.manifestSo I rerun `duply my_bucket backup`, see a console message that indicates resumption of backup from the failed volume. But then I see many lines like:Selection: examining path /path/to/my_file.nii.gz
Selection: + no selection functions found. Including
Selecting /path/to/my_file.nii.gz
Comparing my_file.nii.gz and None
Getting delta of (my_file.nii.gz) and None
A my_file.nii.gzThe many lines give me a feeling that duplicity started the whole backup again instead of resuming from the failure point. Can someone explain me the actual behavior or refer me to a proper documentation?Best,
Tashrif
Duplicity-talk mailing list
Duplicity-talk@nongnu.org
https://lists.nongnu.org/mailman/listinfo/duplicity-talk
[Prev in Thread] | Current Thread | [Next in Thread] |