Re: GPG (pub/prv keys) encrypted backups without secret key being present
Scott Hannahs via Duplicity-talk <[email protected]>
| Newsgroups | gmane.comp.sysutils.backup.duplicity.general |
|---|---|
| Message-ID | <[email protected]> |
Just the duplicity cleanup —force nice -n19 /opt/sw/bin/duplicity cleanup --force --num-retries 5 --tempdir /var/tmp/duplicity --encrypt-key XXXXX --sign-key YYYYY --gpg-binary /opt/sw/bin/gpg --gpg-options=--default-key=XXXXXX --force --verbosity Notice --s3-multipart-chunk-size 100 --s3-endpoint-url https://<host <https://host/> name>.io s3://sth-backup/documents just realized I have “force” in there twice. Probably redundant. -Scott > On May 18, 2024, at 8:04 PM, mirko via Duplicity-talk <[email protected]> wrote: > > On 5/18/24 11:26 PM, Scott Hannahs via Duplicity-talk wrote: > >> When I hit just return it went on to the next stage and did a cleanup. > > What's your clean-up line? Whatever I try after an interrupted backup attempt, I can't resolve the situation og get past it without either providing the corresponding secret key for decryption, or manually deleting the partial backup set on the destination host. > >> Today I removed the --asynchronous-upload option since it is still deprecated, but I remember so discussion that it was working correctly awhile ago. > > deprecated -> experimental (I assume) > > _______________________________________________ > Duplicity-talk mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/duplicity-talk _______________________________________________ Duplicity-talk mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/duplicity-talk