Server address: S3 Address from your Backblaze B2 bucket Endpoint (step three)Ĭ. When ready, enter the information as follow:Ī. If you receive errors, give it a little more time and try again. You may have to wait upwards of 10-15 minutes for your Bucket, KeyID, and Application Key to work properly in Hyper Backup.

Since we are dealing with a cloud provider, the provisioning is not always immediate. We need to configure our server information, but before doing so, I want to make an important point. Under the “S3 Server” select “Custom Server URL”.Ĩ. Add a new “backup task” and select “S3 Storage”.ħ. Now that Backblaze B2 is configured, launch DSM and open Hyper Backup.

Without this setting, Hyper Backup will be unable to find your bucket.Ħ. Also, ensure that “Allow listing all bucket names including bucket creation dates” is checked off. Make sure that you note down the KeyID and Application Key as we will need this information for Hyper Backup.

This is what will ensure that Hyper Backup can connect to the bucket using these credentials. If you need to, create a new Application Key that has permission to your new bucket and ensure that it has an Amazon S3 Endpoint. The next step is to ensure that you have an Application Key that is compatible with the Amazon S3 API.ĥ. If it doesn’t exist, you will need to create a new bucket that will automatically add an endpoint.Ĥ. To see if your existing bucket is, check to see if an “Endpoint” exists.ģ. It’s important to know that older buckets are not compatible with the new Amazon S3 API endpoint. If you have used Backblaze B2 in the past, you will know that all data is stored in a bucket and you can configure credentials for that bucket. How to Backup a Synology NAS to Backblaze B2Ģ.

Conclusion – How to Backup a Synology NAS to Backblaze B2.

How to Backup a Synology NAS to Backblaze B2.

Backblaze server backup