I’m currently running Duplicacy-Web 1.3.0 inside a docker container on a Synology NAS. My original backup was started on March 15th with Duplicacy-Web 1.2.0. I normally do not use the “-hash” option for my backups, but was trying it out in a dry-run. (FWIW even the original backup did not use the -hash option either according to the logs.)
To my great surprise the log of this dry-run with the “-hash” option showed that the backup actually picked up every single file in my backup source for backup. Shouldn’t Duplicacy keep track of the hash values (even when no “-hash” option is specified) and so only pick up those files whose hash value has changed? Certainly the extra effort to calculate the hash value of changed files would be negligible.