#Backblaze backup server password
Enter the encryption password if prompted.Ĥ. Pick the task that is backing up to Backblaze B2. Select the “Restore” button and select “Data”.ģ. I will be deleting a few files from my test directory and restoring them to ensure the process works.Ģ. Backing up your data is only half the battle – you need to ensure that you can restore the data if it is ever lost. Click “Yes” – the backup will now start! Restorationġ.
#Backblaze backup server download
Download the key and place it somewhere SECURE! This key can save you!ġ1. You will also be prompted to download the encryption key if you enabled client-side encryption. You should now be prompted to backup your system. Click yes, configure the backup rotation and “Apply”. If you enabled client-side encryption, you will be warned that you will be unable to retrieve your data if you lose the password or encryption key. When backing up to a cloud provider, it’s always a good idea to use client-side encryption so you know your data is always secure.ġ0.
At the final step, enter the settings you’d like. Select the shared folders and applications you’d like to backup. Directory: File name you’d like to use.ĩ. Bucket name: Bucket name you created in Backblaze B2.į. Secret Key: Application Key (from Backblaze B2 – step five)Į. Access Key: KeyID (from Backblaze B2 – step five)ĭ. 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.
#Backblaze backup server how to
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.
0 kommentar(er)
