

- #ICLOUD VS DROPBOX VS CRASHPLAN VS IDRIVE VS CARBONITE ZIP FILE#
- #ICLOUD VS DROPBOX VS CRASHPLAN VS IDRIVE VS CARBONITE TRIAL#

Of course, scale will come into play at some point, where it will make a lot more sense to go back to Backblaze. Paying a year in advance nets a 10% discount with C2, making it another $0.50 more a month to not worry about paying for API calls, retrieval, or retention. So for less than $2 more a month, I could go with Wasabi and not have to think about API calls or retrieval costs - but I'd have to deal with their 90-day retention policy. They're not at all expensive as a buy-up, but my use case is about 2 TB. And once I started doing "real" backups, I was hitting a wall on the daily limit of 2,500 class B API calls. It seemed to take a long time for the site to accurately reflect cap counts and file info.
#ICLOUD VS DROPBOX VS CRASHPLAN VS IDRIVE VS CARBONITE TRIAL#
I wanted to like Backblaze and added a credit card to get over the 10 gig trial cap for using Hyper Backup with my Synology NAS.ĭoing same-job comparisons with Synology C2, Wasabi, and Backblaze B2 last week, Backblaze was typically a bit faster. I would rather build 2 more duplicate servers, and store one at a different location.ĮDIT: Even Dropbox unlimited would cost less than 800€ per year. Like I said in my original post, I would gladly pay twice the backup price. I realise that I am sort of abusing the unlimited backup for personal use. They way I see it, B2 is very expensive and in no way an attractive option for me. I know I didn't include power costs and data redundancy in this, but even if you went for RAID, or a third duplicate server, you would still be much cheaper off. B2 would cost another 3900$ the next year, but the duplicate server would only need another HDD if needed. So building a duplicate server would cost me less than half of the price of B2 and would be even cheaper in the next year. Let's be generous and add 300$ for other hardware (I build my own server for less than 150 so this is very doable on a 300$ budget). I have plenty of that laying around, but can be bought for very cheap. I have not included other hardware like a PSU, motherboard etc in this. I would need to get 4 of these drives: to be able to store that 65TB myself. Let's round it up to 65TB for the following calculations Ħ5TB would cost 5$ per TB per month. I back that up to Backblaze personal and pay for 1 year version history.

It is shrinking slowly, but is still very large.

#ICLOUD VS DROPBOX VS CRASHPLAN VS IDRIVE VS CARBONITE ZIP FILE#
I get that people aren't a fan of having to have double the available disk space for your restore (for the zip file itself, and then the space to unzip it), but I think the trade-off in time is ultimately well worth it given that external drives are so cheap these days. I essentially experienced the real-world difference between sequential vs random read speeds. I'm assuming because of the overhead of having to seek, send, and then verify each individual file. Doing the same restore on a different service that downloaded each file individually without bundling in a zip, even with a dozen threads going, took like 3 whole days. Restoring 1.5TB, a little over a million files, with BackBlaze on a 1Gbps connection took a couple hours (time for the server to prepare the zip files, saturating my bandwidth for the actual download, and then unzipping). I certainly took it for granted before my recent experience. I think it's underrated that Backblaze packages everything up neatly for you in a zip file for recovery. My reasons used to be price and unlimited storage, but now after experiencing restoring files with another provider, I'll say the recovery features might top those.
