Reducing frequency of verification

[JonMikelV]

At present you can tell Duplicati how many files to verify with each run - including 0 (none) with parameters such as --backup-test-samples=# and --no-backend-verification. Using one of those and the --run-script-before parameter you could dynamically set the parameters at each run.

However, verification checks individual archive (dblock) files - so if you have 50 archive files in your destination and your --run-script-before script only allows for verification of 1 file every week, it will take 50 weeks to verify every archive file.

Here’s a description of what happens during verfication:

How often does duplicati test your backup archives?

Duplicati uses two levels of verification. Before doing anything, it lists all the remote files and checks that all files are found and have the correct size. It also checks that there are no new files. There is a feature request to also check the remote files against an MD5 or SHA-1 sum if the storage provider reports it. The second step is actually downloading a file and testing that it can be decrypted, decompressed and that its contents are as expected. This is done with a random sampling …