Re:Backblaze submitting names and sizes of files in B2 bucke...
by ocdtrekkie on Monday March 22, 2021 @12:26AM
(#26536859)
Also, you know OVH will be investing significantly in fire prevention strategies, so that will all be state of the art.
Re:Backblaze submitting names and sizes of files in B2 bucke...
by spzb on Monday March 22, 2021 @06:06AM
(#26538753)
Well, you would hope they would be but then they thought they had done so already and look how that worked out.
Re:Backblaze submitting names and sizes of files in B2 bucke...
by ocdtrekkie on Monday March 22, 2021 @09:51AM
(#26540754)
Before you experience a major problem, you tend to guess what is good enough to mitigate it. Once you've experienced a major problem, you tend to ensure that exact failure mode never happens again.
I would be surprised if OVH had another fire in the future.
Re:Backblaze submitting names and sizes of files in B2 bucke...
by celsoazevedo on Thursday March 25, 2021 @03:14PM
(#26584193)
And that's why we should always keep backups somewhere else.
OVH has two interesting products here:
OVH cloud archive works with rsync, costs roughly half as much for storage as blackblaze, roughly the same for egress, but charges for ingress (at the same rate as egress).
OVH object store is s3 compatible (like blackblaze), charges roughly the same for bandwidth, 2x for storage.
https://www.ovhcloud.com/en/public-cloud/prices/#439
Digitalocean has a blob store with the same pricing on bandwidth, 4x the pricing on storage, a minimum spend of $5/month on storage, but the first tb ($10) of bandwidth free.
https://www.digitalocean.com/pricing#spaces-object-storage