Re: [Duplicity-talk] File *.gpg was corrupted during upload.

[edgar . soldin]

On 07.11.2011 12:59, Jan Niggemann wrote:
> Hi all,
> 
> just throwing my 2ct in...
> 
> Am 07.11.2011 10:16, schrieb address@hidden:
>> i want to treat it as a warning until the last try. if that fails it
>> of course is a fatal error.
> I'm positive about this and see it the same way Edgar does.
> If it's no performance hug I'd gladly see it implemented.
> 
> Will this check take long and increase the time needed for a backup run?
> I'm asking because I'm re-thinking my backup windows...
> Do I understand correctly, the (potential) increase in time will depend on 
> the backend, won't it?
> 

currently every data volume put up to the backend is checked for it's size 
there, which is then compared to the local size. if they don't match a fatal 
error is thrown.

my suggestion is to expand this to every file uploaded (including manifest 
etc.) and on failure to retry configured --numretry times before throwing a 
fatal error.

performance-wise this will lead to one extra request (if backends support it, 
otherwise nothing is done) fetching the size per uploaded file.


ede/duply.net