but can't android drive guess believe using a ... Nudge. I'm having same problem with the new pydrive backend. I've been using the gdocs backend but based on the Google warnings about deprecati
as backends are quite independent in duplicity and only knitted API-wise wrt. put/get/list etc. file operations, there is a high probability that you can use IP6 under the hood without duplicity even
There is no mechanism in duplicity to force IPv6, and currently no plans to implement one. On Thu, Apr 2, 2015 at 8:58 AM, Marc Evans <address@hidden> wrote: Hello, I am using duplicity successfully
Hello, I am using duplicity successfully to backup with google cloud storage. However I am finding that although the target host for such storage has an IPv6 address: $ host storage.googleapis.com st
Hi, I have successfully made and verified a backup using the pydrive backend written by Yigal Asnis. As per the man page, I made a service account in the Google developers console; I did this while l
On 10 February 2015 at 14:04, Rupert Levene <address@hidden> wrote: Maybe the gdocs backend in duplicity should be updated to use this API? It 100% should. Google makes no promises about the gdocs
[Please CC me on replies.] Any plans to migrate to the Drive API? Also, switching to the new API would avoid the need to supply a Google username and password; instead, Duplicity could obtain an acce
shouldn't be an issue consider using timeout http://serverfault.com/questions/539665/setting-timeout-for-cron-jobs depends on the size of your backup. it does an unnecessary dry run first. also it is
my mistaken, this is a hand-compiled installation of 0.6.25 i did that before my first post, the output is from the CLI. My question here was precisely that unless this bug becomes fixed, is my only
You may want to go for AES256, not AES128, for the encryption and SHA512 for the signature in that case. Actually I am. Thanks. As for the keyfile verses passphrase, I would still recommend the k
You may want to go for AES256, not AES128, for the encryption and SHA512 for the signature in that case. As for the keyfile verses passphrase, I would still recommend the keyfile, there's quite a few
After some digging around I found the following discussion of hardlinks: http://wiki.zimbra.com/wiki/Hard_links The script as written was almost useful to me, though it used what appears to be a linu
Hi, I'm trying to setup a backup from a locally CIFS mount into S3 but I'm struggling with a strange behavior. After the first full backup, the next incremental backup detects several deleted files.
in fact now it connect but failed after when uploading: Duplicity 0.6 series is being deprecated: See http://www.nongnu.org/duplicity/ Using archive dir: /root/.cache/duplicity/42c50b0eead9ebba415b3f
ok it was my fault, my google account was not configured to allow some application to connect. BackendException: Invalid user credentials given. Be aware that accounts that use 2-step verification re
Thanks for the answer! I'm trying to understand the implications of this. Will it have a speed penalty to do so? I.e., does duplicity use resources to re-create a meaningful cache with data from olde
You can't avoid the cache creation, but you can safely delete it after backup if you wish. It will be recreated on the next backup. On Mon, Oct 13, 2014 at 8:22 AM, Manuel Strehl <address@hidden> w
Hello, I do unencrypted backups to a local USB storage, mounted directly. As I understand, the information of ~/.cache/duplicity is only there to ease look-up in the case of network backups, possibly