Did somebody already ask #backblaze regarding diversity? #unplugtrump

Sauvegarde en ligne : peut-on trouver mieux que Backblaze en 2025 ? http://dlvr.it/TJr6BL #Sauvegarde #Backblaze

Je viens de publier ce #playground https://github.com/stephane-klein/append-only-backup-playground qui permet de configurer des buckets Object Storage (#scaleway et #backblaze) pour mettre en place des systèmes de sauvegarde sécurisés en mode append-only (WORM).

Plus d'informations dans cette note : https://notes.sklein.xyz/2025-03-29_1017/zen/

Any recommendations for a good UK / EU alternative to #Backblaze? For backing up 3 Macs, plus I also back up my NAS to B2.

If you're using Backblaze B2 to host your media, you may be seeing errors mentioning "x-amz-checksum-algorithm" or "x-amz-checksum-crc32".

It's a known issue and the Mastodon dev team is looking into it.

https://github.com/mastodon/mastodon/issues/33624

In the link above there are some workarounds, like Mastodon locking the S3 gem to a pre-checksum version and some environment variables for your .env.production file.

OVH Object Storage, as per my tests, is not currently affected by this.

I’m getting a lot of Stoplight::Error::RedLight: object-storage and Aws::S3::Errors::InvalidArgument: Unsupported header 'x-amz-checksum-crc32' received for this API call. errors in sidekiq today. My images are all missing.

I’m using Backblaze B2 for object storage.

Any advice on what to do? Thanks!

Si vous utilisez #Backblaze pour vos sauvegardes de données, ne soyez pas surpris/inquiet d'avoir une erreur « bzfileids.dat file is too large », c'est apparemment un bug de la dernière version logicielle, en cours d'investigation.

À suivre ici :
https://www.reddit.com/r/backblaze/comments/1jam93w/bzfileidsdat_file_is_too_large/

Surely there is a better way to resolve this issue…

https://www.backblaze.com/computer-backup/docs/resolve-a-bzfileidsdat-file-error

Hey #backblaze! What other company do you think leaked that specific email address? Show your reasoning please.

I hate this passive "someone else must have done it" bullshit. Look carefully at the address they sent to..

#security #s3 #securityalert #breach #backblazebreach #b2 #b2breach

Tenía pendiente migrar los backups online de #Backblaze a #Intercolo (empresa norteamericana VS. empresa alemana), pero ya puedo tachar la tarea tranquilamente.

I know its like a drop in the ocean but we sat down today and went through #US based services we use here in #JP. We cancelled #Spotify , #Youtube Premium, #Netflix (no replacements for now), #Amazon Prime (#Rakuten), plan to move our #IBKR portfolios over to Rakuten Securities and #Degiro , #Adobe CC. I am still looking for good replacement for #Cloudflare , #Backblaze and we need to decide what to do with #Apple iCloud and #Google One, GMail and their other services.

#ProxmoxBackupServer es una maravilla. Lo que en copias de seguridad debería ocupar 1TB, con la deduplicación me ocupa 60GB.
Mi bolsillo lo agradece enormemente cuando he de pagar #Backblaze B2.

Trying out https://photosplus.app.

It is a bring-your-own-cloud #Mac, #iOS and #Android app for photo & video #backup. The apps are a little rough around the edges. For example, the menus and interactions are a bit weird.

But it does what it says on the tin. Keeping it around to see if this can help break dependency on Big Tech while also saving on storage costs.

I have tried both #Backblaze B2 and #Storj as storage backends on the app. So far Storj is much faster.

Can someone point me to a pragmatic guide to person information security best practices for backups?

Specifically, I’m wondering how offline backups should be secured when using Backblaze & Backblaze b2. How do I ensure that when I need to restore, I'll have the keys/passwords necessary, if I’m not relying on memory? #backblaze #encryption #offsite_backup #mymemorysucks

Just had a lovely interaction with #Backblaze support.

They completely, and in detail, answered my support request in the very first reply to my inquiry.

Thought I'd share something positive for a change

#Backblaze Drive Stats for #2024
The company had 301,120 #harddrives used to store data as of the end of last year.
Four drives had much higher annual failure rates: 12 TB HGST model (HUH7212ALN604) and three Seagate drives with 10 (ST10000NM0086), 12 (ST12000NM0007) and 14 TB (ST14000NM0138)
Five drive models had zero failures for the quarter: 4 TB HGST (HMS5C4040ALE640), Seagate 8 TB (ST8000NM000A), 14 TB (ST14000NM000J), 16 TB (ST16000NM002J), and 24 TB (ST24000NM002H)
https://www.backblaze.com/blog/backblaze-drive-stats-for-2024/