Hot answers tagged duplicity
Does it have something to do with Google Docs becoming Google Drive? Very likely as the Google Docs API is deprecated: Important: Version 3 of the Google Documents List API has been officially deprecated as of September 14, 2012. It will continue to work as per our deprecation policy, but we encourage you to move to the Google Drive API. I didn't ...
actually the above does merely achieve a backup everything while excluding some files/folders. the correct answer would be. use the highest common root folder that contains all folder you want to back up. using SOURCE="/" is the easy way to achieve that. now modify your .duply/<profile>/exclude as follows + /folder1 + /folder2 - ** Note: there ...
Make the source your system root SOURCE="/" and then create an exclude file at: ~/conf/<backupprofile>/exclude At this article there is a good example of exclude file: http://aguslr.github.com/blog/2012/04/18/backups-with-duply/ **/*[Cc]ache* **/*[Hh]istory* **/*[Ss]ocket* **/*[Tt]humb* **/*[Tt]rash* **/*[Bb]ackup **/*.[Bb]ak **/*[Dd]ump ...
does it have something to do with Google Docs becoming Google Drive? Check this interesting bug report https://bugs.launchpad.net/duplicity/+bug/1030868 could it be that API or urls have changes since then? Is very likely. If so, what can I do to make duplicity work? There is a fix in the way. You should wait till is committed to the main ...
Seems to be a bug with Duplicity: https://bugs.launchpad.net/duplicity/+bug/662442 That thread included a couple of workarounds such as running the verify on single directories at a time vs. the entire tree. Not ideal but better than nothing.
Duplicity will attempt to resume a previously aborted/failed/partial backup. the rsync options will not help, as duplicity encrypts each tardiff file as it it created, and deletes these not yet transferred files on failure. The rsync options will allow it to resume a transfer if no encryption is in use.
Only top voted, non community-wiki answers of a minimum length are eligible