duplicity-team team mailing list archive

Thread
Date

Re: [Question #228855]: Duplicity does not recognize Network down - full backup is not complete

To: duplicity-team@xxxxxxxxxxxxxxxxxxx
From: Paul Bernet <question228855@xxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 06 Jun 2013 12:56:19 -0000
Reply-to: question228855@xxxxxxxxxxxxxxxxxxxxx
Sender: bounces@xxxxxxxxxxxxx

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

    Status: Answered => Solved

Paul Bernet confirmed that the question is solved:
To wrap this up:
- I am able now to detect the duplicity exit codes, see: http://duplicity.nongnu.org/epydoc/duplicity.log.ErrorCode-class.html
- In the case above a Network-Downtime of less than 45 seconds does not affect duplicity: Full- and Diff-Backups return with exit code 0 and the backup is usable and can be restored.
- A Network-Downtime above  around 45 seconds does affect duplicity: Full- and Diff-Backups return with exit codes 30 or 50 - the (old) backup is usable and can be restored.
- The default tcp timeout on ubuntu is 60s and probably the default smbclient 3.4.7 timeout is 20s

Thx again for your help
Paul

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