If one of those repositories become corrupted, you’re just backing up corrupted data. Most of the data on my NAS is archives backed up from client systems using proprietary applications that take care of the incrementing, dedupe, versioning, and compression locally.Ī backup of a backup is not really a backup. I'd be happy to reconsider Backblaze once they've improved their EU/UK server infrastructure and portability between buckets. I do like Backblaze and B2, but the limitations of your service mean I need to find another service. I post this to inform other users who might have similar needs and to inform Backblaze. Unlike B2, Wasabi allows you to create buckets in different server locations and move data between differing geolocated buckets. The Wasabi web interface is impressive and functional.

Having a land connection to a local server is faster and more reliable. This is important because from the UK, EU servers require that data travel across the submarine cables through the North Sea. Wasabi has many EU servers, including several in the UK (as opposed to Amsterdam or Germany). Even more important, their EU/UK servers are very fast. They cost me a few pennies more than B2, but with no retrieval or other fees. I had used Wasabi several years ago and found them to be pretty competent. I am now using Wasabi ( ) and all I can say is w.o.w. I've tried iDrive three times in the past 15 years.never again. iDrive offered me 10TB for about $3.50 a month, so I gave them a chance. I wasn't happy about that, but I liked B2, so I started the process, but I found that the B2 EU server was actually slower than the U.S. The only solution was to create a new account, choose the EU server, and start over with my complete cloud upload. I wasn't aware that I could not move my B2 data from their US servers to their EU server in Amsterdam. So, I really only need to copy that data to a cloud without versioning. Most of the data on my NAS is archives backed up from client systems using proprietary applications that take care of the incrementing, dedupe, versioning, and compression locally. I backup up about 4TB of data to the cloud as a worst-case recovery option. Badly designed UI's, incorrect count and storage data, and slow response from support eventually made me realize that iDrive was a mistake. I recently posted an article about moving from Backblaze to with some reasons why it seemed to be a good idea for me.

Backblaze reddit