Re: [Duplicity-talk] Orphaned signature files, backup broken?

[edgar . soldin]

On 12.06.2014 13:51, Marc Hoersken wrote:
> On 12.06.2014 12:54, edgar.soldin wrote:
>> try
>> - update to the latest release 0.6.24 
>> - run the verify command
>>
>> ..ede/duply.net
>>
> 
> Thanks, I updated to the 0.6.24-1 debian package and ran the verify command:
> 
> ...
> Verify complete: 9645 files compared, 9 differences found.
> 13:45:30.268 Task 'VERIFY' failed with exit code '1'.
> --- Finished state FAILED 'code 1' at 13:45:30.268 - Runtime
> 00:15:28.650 ---
> 
> The warnings still show up, but I did a full backup inbetween, so the
> warnings are related to a secondary backup chain.
> 
> I think it's interesting that the local orphaned signature files match
> the remote onces, but are unencrypted sigtar.gz files while the remote
> onces are encrypted sigtar.gpg files.
> Any clue about why this happened? Attached you will find the whole
> output of the status command.
> 

you know that you can verify past backups via -t (time) option? duply 
essentially routes that through
see duplicity manpage
 http://duplicity.nongnu.org/duplicity.1.html

duplicity/duply has a cleanup command in case that files get leftover or from 
incomplete backups (interrupted & unresumed). we also had/have a bug that 
leaves old signatures lying around.

..ede/duply.net