Re: [Duplicity-talk] Problem with completing fill signature to b2 backblaze

[edgar . soldin]

On 27.10.2016 10:29, Martin Eskdale Moen via Duplicity-talk wrote:
> I'm getting the following problem below, this is my third attempt running it 
> from scratch and the same issues comes up every time.
> I'm backing up to b2 backblaze, and I can push files manually without any 
> problems and all the preceding tars have been fine.
> 
> Any ideas would be great
>  
> 
>     Writing duplicity-full.20160814T140140Z.vol6118.difftar.gpg
>     Deleting /tank/tmp/duplicity-ZAnAWE-tempdir/mktemp-kuhS2w-3
>     AsyncScheduler: task completed successfully
>     Processed volume 6118
>     Writing duplicity-full-signatures.20160814T140140Z.sigtar.gpg
>     Attempt 1 failed. URLError: <urlopen error [Errno 104] Connection reset 
> by peer>
>     Writing duplicity-full-signatures.20160814T140140Z.sigtar.gpg
>     Attempt 2 failed. URLError: <urlopen error [Errno 104] Connection reset 
> by peer>
>     Writing duplicity-full-signatures.20160814T140140Z.sigtar.gpg
>     Attempt 3 failed. URLError: <urlopen error [Errno 104] Connection reset 
> by peer>
>     Writing duplicity-full-signatures.20160814T140140Z.sigtar.gpg
>     Attempt 4 failed. URLError: <urlopen error [Errno 104] Connection reset 
> by peer>
>     Writing duplicity-full-signatures.20160814T140140Z.sigtar.gpg
>     Giving up after 5 attempts. URLError: <urlopen error [Errno 104] 
> Connection reset by peer>
> 
> 
> 

hey Martin,

check if your backend has max size restraints for files. most likely the 
signature file exceeds it.

you might make a test backup to a local file:// target to check what files are 
generated and how big they get.

currently duplicity only splits data volume files according to vol.size, 
meaning big backups w/ lots of files can generate signature files sized 2GB or 
bigger. only workaround is to ensure that the backup does not contain too many 
files by splitting it into smaller parts.

..ede/duply.net