In case you’ve missed it, Crashplan announced yesterday that they are no longer offering a family backup plan but instead focusing on business plans. Immediately people started asking me on twitter for alternatives.
Well one option would be to upgrade to the more expensive Crashplan business plan or another option would be to check out Backblaze!
In this post I’ll be showing you just how easy it is to use Backblaze on your Synology Diskstation NAS – all with native Synology apps. No need to worry about upgrades breaking your backups or 3rd party solutions!
Install Backblaze on Synology NAS
- First you obviously need a Backblaze account, if you haven’t already signed up do so now.
- After the account has been created we need to create a “bucket” where all the files will be stored, so click on Create a Bucket.
- Now give your bucket a name and more importantly make sure you set your bucket to “Private” – unless you want everyone to see your files.
- After you’ve create a bucket, now click on the Show Account ID and Application Key link.
- Next click on the Create Application Key button and then make note of both your Account ID and Application Key.
- Now log into your Synology admin interface.
- Install Cloud Sync package. Go to your Package Manager > Backup > and click on Install under Cloud Sync.
- Next open Cloud Sync and click on the plus (+) button in the bottom left corner.
- Then select Backblaze B2 from the list of providers and click on Next.
- Now enter your Account ID and Application Key from Step 5 above and select your bucket from the drop down menu, then click on Next.
- Now you’ll want to select a Local Path (a folder on the NAS) you want backed up, then adjust the other settings to your liking and click Next.
- Finally, confirm the settings and click on Apply.
At this point your files will start being backed up to Backblaze using the Synology Cloud Sync app and you’ll have little worry about a Backblaze and/or Synology update breaking your backups!
Let me know what you think about Backblaze in the comments below.
Avoid Class C Transaction Cap
I’ve had a couple people state they’ve had issues with getting messages from Backblaze regarding reaching the Class C Transaction Cap, which is 2,500 daily. To fix this issue you just need to change the polling period in Cloud Sync from the default 60 seconds to something more manageable, I’ve set mine currently to 3,600 without any issues:
But Mike is this backup?
I have also received a few comments stating this couldn’t possibly be backup because it’s sync and doesn’t support versioning. The only thing I can say to that is those individuals simply have not even bothered trying this method. Because by default, Backblaze sets all bucket lifecycle policies to “Keep all versions of the file (default)” as shown below:
Further, here is a test file I’ve uploaded, made a few changes a couple times and you can see the different versions, time stamps and file sizes:
Simply put, give Backblaze a try. THEN come back and let us know your thoughts. 😉