Then if you do this how you do you check that the Backups are good or you just the tar archive.
You'd untar them.
That is a full check. But without paying to download the file you just uploaded, you hash the file first and send the hash along with the upload. B2 will hash it when completed and verify that it matches your supplied hash. If it doesn’t, it asks it to reupload.
@matteo-nunziati That's pretty bad design if there is no automated way to backup to a remote blob provider or to push said backups to said outside provider. . .
That $399 is sounding incredibly reasonable now.
A main goal of any cloud service from major vendors is to lock in. Try to access a backup in GCP to export data: you can't.
I'm digging a bit to understand if the SQL backup in azure is accessible or managed by any infrastructure account which prevents users to access them directly...
"A Group is a collection of Backblaze users. All Groups have billing centrally managed by an administrator and allow administrators to keep track of the Group member’s backup statuses, B2 usage, and any alerts that members may have on their Backblaze accounts. Best of all, Groups bring added functionality to Backblaze at no extra cost."