Re: [Duplicity-talk] Question about restore vs verify

[edgar . soldin]

to cite the man page
"
verify [--compare-data] [--time <time>] [--file-to-restore <rel_path>] <url> <local_path>

Verify tests the integrity of the backup archives at the remote location by downloading each file and checking both that it can restore the archive and that the restored file matches the signature of that file stored in the backup, i.e. compares the archived file with its hash value from archival time.
"

so, your understanding is correct. ..ede/duply.net

On May 26, 2023 2:45:35 PM GMT+02:00, Felix Natter via Duplicity-talk <duplicity-talk@nongnu.org> wrote:

Dear duplicity community,

I am currently testing my backup in two ways:

(a) running a "duplicity verify" right after having created the backup:
$ duplicity verify $DUPLICITY_OPTS --compare-data file://$DEST/weekly/ /repos/TOBEBACKEDUP/

(b) (every week) copying the backup from the cloud to file://.../weekly/ and then using "duplicity restore":

$ duplicity restore $DUPLICITY_OPTS file://.../weekly/ /repos/restored/

-> (b) had already detected a checksum error when the backup on the cloud had not been uploaded properly.

Question: Is there a benefit of additionally using "duplicity verify" on the downloaded cloud backup
(obviously without --compare-data):

$ duplicity verify $DUPLICITY_OPTS file://.../weekly/ /repos/TOBEBACKEDUP/

In other words: Is the purpose of "verify" that it only temporarily stores the restored backup contents
(more convenient), or does it do something else that "restore" doesn't do?

Of course I read the man page, but couldn't find this piece of information.

Many Thanks and Best Regards,

Felix