![]() Got everything setup and things were running fine for a number of months. I still had my Cloud Sync going, so worse case it just was.a waste of time. So when Backblaze announced the S3 compatible API and that Hyperbackup would work with it, I was excited and set it up even with the knowledge that it was a beta. Thanks for all that tested things and /u/ssps for finding the solution. I will be informing Backblaze that I've resolved the issue and that they need to make sure to verify that the minimum version of Hyper Backup should be 2.2.5-1261. So manually installing it and relinking worked at that point. And for some reason that update is not showing up when my NAS or others look to see If there are any updates. ![]() Turns out that there was a package update for Hyper Backup that fixed the issue with it not respecting the API version that was selected when you had used client encryption and it needing to use your encryption key to decrypt the backup. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |