As soon as I got wind of the ACD stuff going down, I setup rclone for backblaze b2. Got my pro-rated refund from Amazon.
Pricing is $5/TB/month for storage, free uploading, and $20/TB for downloading. There’s some minor API transaction costs, but it doesn’t appear that they will add up to anything significant.
From the East Coast US, backblaze is pretty quick. Easily 150-180mbps uploading, which is flooding my FIOS. Fantastic, really. I’ve got reasonable enough speeds that I wasn’t gonna mess with a VPS or similar to do cloud->cloud.
My storage requirements are in the single digit TBs. The only time I’ll be downloading is to test the backup, which will consist of spot-checking by downloading 10s of GBs throughout the directories, and then hashing the original vs uploaded. I think b2 might store a checksum in its metadata, however I’ll have to think through whether that’s sufficient. I suppose there could be some bitrot after initial upload.
rclone doesn’t support b2’s versioning with filename encryption due to appended date/time stamp of the versions, and b2 doesn’t support --backup-dir option of rclone due to lack of server-side moves.
While b2 is much more than google drive, I don’t feel like screwing around with yet another provider where I’m the undesirable part of the equation. Basically just waiting to be marginalized, slowed, and excluded. I’m a full-paying customer of b2 – I pay what all customers of b2 pay for storage. If I use more, I pay more.
No real quirks with b2 that I’ve found yet – everything seems to be working as before.