If you really desperately want to use the non-B2 version of Backblaze, sync your files to the remote server using rsync and use Backblaze to backup the whole files, not the chunked up Hyper Backup.Apologies for the repost if so but I need help understanding the functionality of the cloud tech and services. It's relatively cheap and can be used natively. Just use B2 if you want to use Backblaze. Backblaze is blindly pushing chunks and new versions of the database up to their backup servers it introduces the possibility that you'll end up with an incomplete backup if there's a failure, because changes to the database or the chunks are not fully married up at the remote end. I'm also not certain this would be highly robust. Backblaze won't be able to tell what file is what, it'll just have a directory full of chunks and you'd have to pull the whole directory down. Unfortunately, what will also happen, is that it will be impossible to restore anything from a backup without downloading the entire Backblaze backup (including your version history), because you won't be able to tell which chunks contain the files you want. Which would successfully get your Hyper Backup files moved to Backblaze. If you went this route, what you'd end up with is all of your chunked up Hyper Backup files, and the Hyper Backup database, sitting on a server and getting pushed to Backblaze. Hyper Backup doesn't write out normal, whole files to the filesystem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |