The local disk supports SHA1 checksums so large file transfers from local disk will have an SHA1. 2įor a large file to be uploaded with an SHA1 checksum, the source needs to support SHA1 checksums. Since Backblaze only supports SHA-1 checksums, the Rclone docs indicate the source must also support SHA-1 checksums. Pretty neat! List Folders Syntax: lsdĪfter setting up your remote with rclone config, use the list directory command lsd to double check your source/target folders.įor example, if the B2 remote name is called b2-remote1 then the command to list the root is:ĩ 16:53:44 DEBUG : CAM A/private/M4ROOT/CLIP/C0001.MP4: Cancelling large file upload due to error: unexpected EOFĩ 16:53:45 DEBUG : CAM A/private/M4ROOT/CLIP/C0001.MP4: Received error: unexpected EOF - low level retry 1/10ĭouble Check the Source Supports (and has) Checksums In fact that’s what I mainly did: transferred assets from a personal B2 bucket to the organization’s new B2 bucket. The computer running Rclone will stream data in RAM as it shuttles data between the two. Keep in mind Rsync supports copying between two remotes directly. To Keep in Mindįirst, the overall workflow.
Rclone backblaze archive#
With trial and error, I was able to archive 8 TB of footage from my Synology NAS to Backblaze B2 in about a month.
This post will outline the workflow and some gotchas to keep in mind when doing massive data loads over the internet. The previous post detailed how Rclone can reliably upload large files with their checksums to Backblaze unlike other programs.
0 kommentar(er)
