ctrl+c or kill <pid> should both send SIGINT to the duplicity python process and having it stop gracefully. if that leaves a lockfile then thisd is a bug and should be fixed. ..ede/duply.net
Sorry for the utterly simple question, but I legitimately cannot find an answer, and I feel stupid for not being able to find it. Question simply is, how do I correctly kill duplicity? Every method I
On 9/3/14, 1:55 PM, address@hidden wrote: On 03.09.2014 20:19, Carlos Chavez wrote: On 9/2/14, 4:14 AM, address@hidden wrote: On 02.09.2014 00:12, Carlos Chavez wrote: I just installed a new CentOS 6
2014-06-09 17:33 GMT+02:00 Elvis Stansvik <address@hidden>: Hi all, I got interested in the archive format described at [1]. Is there still an interest in developing this format further and eventuall
Hi all, I got interested in the archive format described at [1]. Is there still an interest in developing this format further and eventually replacing the use of TAR in Duplicity? I have no particula
Hi Edgar, Unfortunately I do not seem to be able to reproduce the issue anymore. Found 1 secondary backup chain. Secondary chain 1 of 1: -- Chain start time: Sat May 3 03:30:22 2014 Chain end time: M
Just some feedback in case other people want to try Google Cloud Storage. I have been using Duplicity with GCS for 1,5 months now and so far so good. It's cheap at ~$4 / month for 200GB+ (inbound tra
Hi all, I understand that Duplicity supports both Google Drive and Google Cloud Storage through gdocs:// and gs:// respectively. Does anyone have a view on the (dis)advantages of using GD vs GCS as a
After some reading, it looks like Amazon Drive is comparable to Dropbox, with auto-sync. (But no Linux version.) Amazon Cloud Storage is a more typical cloud backend with APIs, but the prices there a
Hi, I see on the list that some people are using the gdocs backend for duplicity to use this service, but it sounds a little iffy. Can anyone weigh in with recent experiences? At those prices, I'm
In case you missed it, Google Drive's new pricing is far lower than before. http://googleblog.blogspot.com/2014/03/save-more-with-google-drive.html 15 GB/Month: Free 100 GB/Month: $1.99 1 TB/Month fo
Germar, i'd like you to rename the backend file to ~par2wrapperbackend.py to make sure that a theoretical future zzzbackend.py would be included as well. also could you please add documentation to th
let's place this topic on the mailing list for others to find, shall we ;) Kostas, we already use checksums. "un"fortunately they are encrypted, in the manifest i think, so actual distorted gpg files
Well my guess is the main pain factor is the total size of the full backup plus all of the incrementals. I'd suggest running increments only for a while (say a month or two) and see how big they are
Thanks for the response, it is much clearer now. So how much pain is it to restore a full incremental backup going up to a year? Let's say the base is 150GB, and the variance about 1GB a month. Doing