Is a legitimate concern for any space-efficient backup format that does things like only saving changes rather than entire files. If one document gets damaged, I can download others It checks that the backup files look as the local database says they should, and it also self-checks the local database. There is also a complete file listing on every backup to check remote file names and sizes, and this theoretically will catch most problems of damage on the remote, avoiding need to download to look.Ī fine but important point is that this does not do or replace doing file restore tests. The TEST command explains what a sample is – typically 3 files in 1 sample set, but may be less.
Option is provided, no remote files are verified. Is the maximum implied by the two options. If theīackup-test-samples option is also provided, the number of samples tested The percentage (between 0 and 100) of files to test. Remote backend are selected for verification. This procedure increases the reliability of the backup files, but backups take a bit longer to complete and use some download bandwidth.īackup-test-samples defaults to 1, but you can make it far higher with backup-test-samples or this one: -backup-test-percentage (Integer): The percentage of samples to test afterĪfter a backup is completed, some (dblock, dindex, dlist) files from the The contents of these file is checked against what Duplicati expects it to be.
#Iperius backup manual manual#
The manual says more, and note that it’s not in the background:Īt the end of each backup job, Duplicati checks the integrity by downloading a few files from the backend. Do you mind Duplicati do it automatically in the is correct that it’s automatic.
0 kommentar(er)
