![]() If anyone has any questions about this setup, please let me know. The data I'm backing up does not change often, and it actually has not changed at all since I've been on B2. So far, I've uploaded ~900GB and downloaded ~400GB at a cost of about $7.50. 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. I've set Backblaze to only keep one version of my files (Lifecycle Settings), as I don't believe having versioning would be useful since I have client-side encryption set up. How to Backup a Synology NAS to Backblaze B2 1. Transfer encryption and client-side encryption were enabled on the Synology device. ![]() This did not use up all my available download bandwidth. Then, click Connect and wait for Recoverit to establish a connection. Step 3 Connect to Your Synology NAS Enter the IP, Port, User Account, and Password. Select the NAS where you’ve lost files if you have multiple devices. The restore took about a day to complete. Step 2 Select Your Synology NAS Wait for Recoverit to find your NAS device. I attempted a test restore of about 400GB worth of the data, which worked perfectly. The initial backup saturated my 20Mbps upload speed and took 3-5 days to complete. ![]() I've been using the Backblaze B2 S3 API with Hyper Backup for a few weeks now and wanted to share an update on my experience.
0 Comments
Leave a Reply. |