duplicity-team team mailing list archive

[Kenneth Loafman <question253609@xxxxxxxxxxxxxxxxxxxxx>]

Question #253609 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/253609

Kenneth Loafman proposed the following answer:
You can remove the .part files at any time.  Those were prior to applying
gpg and will be larger.

The naming convention is bad for those .part files.  We should have used
something else that did not imply transmission.  Normally, .part files
would appear on the receiving end and be renamed once the transfer was a
success.

On Sat, Oct 18, 2014 at 5:46 PM, Northrock <
question253609@xxxxxxxxxxxxxxxxxxxxx> wrote:

> Question #253609 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/253609
>
> Northrock posted a new comment:
> As a BTW would I be correct in thinking that having the manifest and
> signature files on s3 are needed only if the local cache files are
> missing i.e. incremental backups and restoration can continue without
> those files saved remotely as long as a local cache exists?  … al a
> local manifest and signatures with remote archives?  (then I could nurse
> those files as necessary etc).
>
> Notice duplicity-full-signatures.20141011T024928Z.sigtar.gpg and
> duplicity-full-signatures.20141011T024928Z.sigtar.gpg.part are also
> different sizes.
>
> Does .part mean that the file was just queued for transfer (locked
> state), or is it suspect?  Should I just remove .part from the manifest
> filename?
>
> My command:
>
> duplicity \
>     --num-retries 20 \
>     --archive-dir "~/.cache/duplicity/" \
>     --tempdir "/tmp" \
>     --s3-use-new-style \
>     --exclude "**cyrus.squat" \
>     --file-prefix-archive "_" \
>     --include-globbing-filelist "duplicity.list" \
>     --exclude "**" \
>     --encrypt-key {removed} \
>     --volsize 256 \
>     --verbosity 5 \
>     ${SOURCE} ${DEST} > ${DAILYLOGFILE} 2>&1
>
> I assume the stats from this first big job are lost.
>
> PS: Thanks for the tip on re-checking the archives… there are about
> 3,000+ of them.
>
> Thank you.
>
> --
> You received this question notification because you are a member of
> duplicity-team, which is an answer contact for Duplicity.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~duplicity-team
> Post to     : duplicity-team@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~duplicity-team
> More help   : https://help.launchpad.net/ListHelp
>

-- 
You received this question notification because you are a member of
duplicity-team, which is an answer contact for Duplicity.