Can some explain verify parameter full-remote-verification?

#1

As I understand:

verify with no parameter checks ONE random dlist with a index-file belonging to this dlist and with the dbblock for this index file. Correct?

I can also give a number of samples or ALL to verify all files.

What I don’t understand is what full-remote-verification does and how to use it.

Which one is correct?
–full-remote-verification
–full-remote-verification=true

I tried to understand it using --verbose=true but there was no really difference in the output.

What does the “normal” verify and what does the “full” verify?

Is the full-remote-verification also usable with a sample and with all?

0 Likes

#2

They do the same. The logic is that you can supply an argument to enable it (all boolean options are false by default).
If you write some value to the boolean option, it is parsed and checked against (false, 0, off, no) and a match will make it false, any other value will make it true.

The option itself, --full-remote-verification is used to trigger “deep” verification. By default Duplicati downloads the file, and checks that the file hash matches. The --full-remote-verification changes this and actually decrypts the file, opens it, compares the content of the file with the database contents. For dblock files it also samples a random 30% of the files inside the compressed archive and checks that they can be extracted, and that the extracted files have the correct hash.

1 Like

Patching files with local blocks
Backup issues following NAS crash - Hash mismatch
Metadata error, llistxattr, error: ERANGE (34)