Hi there
Today in the middle of the backup there has been a network connectivity issue and backup has failed with " dial tcp X.X.X.X:YYYY connect: no route to host"
is there any option to tell duplicity to retry several times in such cases?
No, there isn’t a global option to handle this error. Which backend are you using?
1 Like
Hi, it is a minio server (S3 Like) on a private location accessed via IPSec tunnel During a few seconds the tunnel restarted, but the backup stopped. I can control exit codes and do retries on a script but it would be easier from a user perspective to allow some retries in command line / config.
1 Like
Yeah, ive seen this even on my Google Drive the rare time. the issue is, it will Kill the job and require it to re-index. maybe an “-r 5” for retry 5 times or something or r “-r 5 -t 10” so retry 5 times every 10 seconds.
that be nice! 
2 Likes