If you change the command to
test from a to commandline exported backup configuration, you’re not doing a full verification.
Basically, you supply all options used to make a backup to the
test command. Some of them are required (URL, credentials, passphrase), but most of the options used for the backup are ignored by the
test command does exactly the same as verifying the backup after each backup operation is completed: it downloads a number of DBLOCK files (default 1) and checks the integrity and contents of that DBLOCK file. If the file looks as expected, the verification completes successfully.
So instead of a full verification of your backup, you probably let Duplicati download just one random DBLOCK file and let it check if the contents are what Duplicati expects.
If you want to test and be 100% sure that all files can be restored, the only option is doing a full restore. Another option is to supply the
--backup-test-samples option to the
test command and give it a value that is the same as the current number of DBLOCK files at the backend. This will force Duplicati to download all DBLOCK files and check the integrity of these files.