![]() ![]() In case tragedy strikes (ransomware), my remote hyperbackup will be affected. This way, I can save bandwidth by using synology's own versioning system and uploading only the changes necessary, instead of whole files (as would happen with the cloudsync solution). They will be in synology's proprietary format, versioned. I mean, there will be a folder inside a backblaze bucket named "my hyperbackup", with all my hyperbackup files. Now, I'm reconsidering Hyperbackup, but leaving it versioned in backblaze. Also, any file change will require a full file upload, instead of uploading changes as in hyperbackup. The cost in API calls alone will go through the roof and, if I limit myself to the daily free cap, it will take forever. Upon further consideration, I realized recovering from a previous backup might prove impractical and costly, for I'll have to re-download a multitude of files in order to reassemble my system. I initially considered using hyperbackup, it was fantastic, until I read from someone who had a system failure half-way through a hyperbackup update and it destroyed the hyperbackup (can't recall if it was local or remote, presumably local).Īfter hearing that, I decided to leave my versioning to a third-party, most likely backblaze through Cloudsync. ![]() Guys, I'm going nuts planning my off-site backup. TL DR: Can I store my hyperbackup folder in backblaze B2 and, if necessary, recover from an older hyperbackup folder version? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |