Re: [Duplicity-talk] Restart duplicity without private key

[edgar . soldin]

On 19.06.2014 10:00, Radomir Cernoch wrote:
> Dear all,
> 
> I would like to use duplicity (v0.6.23 from Debian) without saving the
> private key or its passphrase on the computer. After having abandoned
> signing and started using encryption only, there is still an issue.

while it sounds easy enough duplicity has no complete support for this 
scenario. mainly because of the issue you are facing

read here
 https://bugs.launchpad.net/duplicity/+bug/687295
and here
 http://thread.gmane.org/gmane.comp.sysutils.backup.duplicity.general/4245

> If a backup is interrupted, the local metadata go out of sync with
> remote metadata. A subsequent backup needs to synchronize and
> decrypt them from the remote server. However, this  procedure fails,
> because of the missing private key. The result is undesirable: Every
> interrupted backup requires a human intervention.

you are right
 
> As a compromise, I hoped to use "cleanup" before every backup, which
> would have enforced a full backup after an interrupted one.
> Nevertheless, even the "cleanup" command requires the passphrase.

yes every time duplicity is run it syncs the archive dir first
 
> Why is it the case? A cleanup should only delete remote files,

no idea. Ken?

> shouldn't it? Is there a way to escape the "interrupted backup" trap?

as a workaround you can delete the unfinished backup's files manually on your 
backend. the files are neatly named with date.
run a verify afterwards to be sure.

finally. you should update to 0.6.24 which fixes some critical issue's.

also read my other mail about - why i think that duplicity without private key 
is not a good idea.

..ede/duply.net