Question #107216 on Duplicity changed: https://answers.launchpad.net/duplicity/+question/107216
Status: Open => Answered edso proposed the following answer: This was true until duplicity version 0.6.0 .. This version keeps the necessary metadata for incrementing backups in an archive/cache folder. Duplicity checks it against the repository and only downloads/decrypts these files if outdated(backup from another machine) or missing/corrupted. Hence you can do it this way, but will have to keep an eye on duplicity's output. On smaller backup's I'd suggest going for fulls only, which never need a private key, except for verifying/restoring. But what good is your backup anyway if the hacker has access to your private key, he has access to the duplicity backend credentials as well as to the data itself. ede -- You received this question notification because you are a member of duplicity-team, which is an answer contact for Duplicity. _______________________________________________ Mailing list: https://launchpad.net/~duplicity-team Post to : duplicity-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp