

I use it for personal archives and some client collaboration (photo and video). My goal is to have an unlimited cloud backup on Dropbox of my Synology NAS archive. Instead roll up your sleeves are get cracking with rclone on the Synology.Apologies for the repost if so but I need help understanding the functionality of the cloud tech and services. If you care about checksums for files over 4 GB, don’t use Synology Cloud Sync. Best practices of using rclone with using B2 coming soon. How to use the rclone sync and rclone verify commands are deatiled in Rclone B2 docs. Run rclone config, enter cloud credentials, etc.Verify it is installed with rclone -V and rclone -h.Installing rclone is super simple on the Synology. However, it’s only for folks not afraid of the terminal. It’s actively maintained, and writes and verifies checksums with B2 perfectly 5. Rclone is a command line workhorse for syncing files with cloud storage. So what can upload to B2 with checksums for large files? Rclone FTW B2 in fact supports and encourages 4 sending checksums for large files- and they can even be sent at the end! Cloud Sync is simply not sending SHA-1 checksums to Backblaze. To be clear, the checksum limitation is on the Synology end. As you can see I had it set to 512 MB the maximum is 4 GB. Hash values are not available for files uploaded to Backblaze B2 via b2_upload_part upload.ī2_upload_part upload… After consulting the B2 API documentation 3, that command is used for uploading large files in segments. Please refer to the bottom of the page for more information. This will require more time and system resources, and depends on the public clouds’ support for advanced attributes. With Enable advanced consistency check ticked, Cloud Sync compares the hash (in addition to file size and last modified time) of each file between the public cloud and the NAS to enhance the integrity check of the sync results. Not knowing this limitation was my mistake, as I did not understand the Cloud Sync documentation 2 thoroughly beforehand. That meant all the actual video files didn’t have checksums sent to B2. In fact, it worked great and I created a bunch of jobs to archive nearly 8 TBs.Ĭloud Sync even offers an Advanced consistency check option to compare checksums! All good right? Hash me NotĪlthough I had selected the checksum option I was surprised to realize not all files uploaded had their checksums written in B2.

Synology offers a built-in tool that syncs to many cloud providers, called Cloud Sync. I had a few TBs of large file video footage stored on a Synology NAS that I wanted to archive to B2, in case anything happened to my local array. Backblaze B2 is an incredibly cost-effective cloud-based archival platform.
