Update docs for "Backing up a crypted remote"

given this output where the source is gdrive which uses MD5 and onedrive which uses SHA1/QuickXorHash

rclone copy gdrive:crypt odrive:crypt -vv 
DEBUG : piviejsu06b8311vk99cqb1t6c: Size and modification time the same (differ by -502ms, within tolerance 1s)
DEBUG : piviejsu06b8311vk99cqb1t6c: Unchanged skipping
INFO  : There was nothing to transfer

rclone check gdrive:crypt odrive:crypt -vv 
ERROR : No common hash found - not using a hash for checks
DEBUG : piviejsu06b8311vk99cqb1t6c: OK - could not check hash
NOTICE: One drive root 'crypt': 0 differences found
NOTICE: One drive root 'crypt': 1 hashes could not be checked
NOTICE: One drive root 'crypt': 1 matching files

for https://rclone.org/crypt/#backing-up-a-crypted-remote

"rclone sync will check the checksums while copying"
to
"rclone sync will check the checksums while copying only if the encrypted source remote and encrypted dest remote support the same hash. For example, when copying encrypted files from google drive to microsoft onedrive, which have dissimilar hashes, rclone will not compare the hashes."

and

"And to check the integrity you would do"
to
"And to check the integrity you would do the following, only if the encrypted source remote and encrypted dest remote support the same hash"

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.