#57 Add a retry mechanism in case of duplicity backend error

[3rjpq0d6x]

I sometime encounter error when the backend is temporarily unavailable.

In those case, duplicity just exit and display the traceback.
It would be really nice if duply would catch that and retry a few times

[ede]

hey @3rjpq0d6x,

duply is mainly meant to be run manually or by cron and be finished after it is done. i'm unsure if it is a good idea to have it sleeping and retry blindly if some error occurs. duplicity itself already has a retry mechanism build in that should be of help to you. look at the man page
https://duplicity.us/stable/duplicity.1.html
for the options
--num-retries
--backend-retry-delay

does that help? ..sunny regards ede

[3rjpq0d6x]

those options haven't always worked in my experienced, hence my request, but it might just be an issue on duplicity side.

I'll investigate that and come back here if needed.
Thanks a lot

BTW, I've seen that this SVN repo is only updated on release, is there any repo somewhere that is up to date with active developpement ?

[ede]

the options "should" work over all backends, but sure there might be implementation flaws. if so please open a ticket on

https://gitlab.com/duplicity/duplicity/-/issues/

and let's fix it :)

apart from the repo i only offer snapshots on https://duply.net/Code#Latest_Development_Snapshot if some issue needs double checking by the issuer. currently there not much developing on duply as it is quite mature and stable fortunately.