B2 crypt restoration

What is the problem you are having with rclone?

I have an encrypted backup stored in b2. The backup is large, around 1.5TB. My HDD died and I restored the backup by ordering a copy of my bucket on a USB drive by mail from Backblaze, so I don't have to download 1.5 TB. The backup restored, everything is fine. Now if I attempt to sync my local files with the remote backup rclone attempts to upload every signle file because all file modifications dates got messed up. Cryptcheck works just fine, indicating no changes. How can I avoid reuploading everything and still use the same remote?

What is your rclone version (output from rclone version)

rclone v1.50.1

  • os/arch: linux/amd64
  • go version: go1.13.4

Which OS you are using and how many bits (eg Windows 7, 64 bit)

Synology/DSM

Which cloud storage system are you using? (eg Google Drive)

Backblaze b2 + crypt

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone sync --dry-run /data b2-crypt:

A log from the command with the -vv flag (eg output from rclone -vv copy /tmp remote:tmp)

Backblaze supports setting the modification time now, so what rclone should do is

  • notice mod times are different
  • check file size and checksum, if the same then
  • set the modification time of the remote file.

Is that not what you see?

Yes, that's exactly what I need.

Interestingly, that b2 messed up only a fraction of file dates.

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