Re: [Duplicity-talk] Operation of verify command

[edgar . soldin]

You got a point.

It's documented, duplicity complains if it is not there. But it shouldnt be 
needed.
Ken are you reading?

ede/duply.net 

On 11.12.2010 12:55, Chris Poole wrote:
> One final question then:
> 
> The verify command grabs a volX.difftar.gpg file from the backup
> location, checks the files inside against the hashes made at backup
> time, then removes the volX.difftar.gpg file, and grabs the next one.
> 
> So why do we need to give it a target directory? Can't it just put the
> files it downloads in /tmp or somewhere, given that it's going to
> remove them straight after?
> 
> 
> On Fri, Dec 10, 2010 at 1:33 PM, Chris Poole <address@hidden> wrote:
>>> read here, that should resolve your question
>>> https://answers.launchpad.net/duplicity/+question/116587
>>
>> Thanks, I hadn't noticed that.
>>
>> So when files are added to the backup fileset, a hash is taken. This
>> is stored in some other file that also gets encrypted and backed up.
>>
>> The verify command downloads the complete fileset and the file with
>> the hashes stored, and computes the hashes in each volume file again,
>> comparing them with the ones taken at the original backup time.
>>
>> If all is the same, the verify command passes.
>>
>> I'm happy with this, but occasionally would feel more secure by
>> checking the backed up fileset with the local fileset that they're
>> from. I've written a script to do this, essentially just using
>> md5deep. For some reason, I makes me feel more safe.
>>
>> Thanks.
>>