{"id":10990,"date":"2017-02-09T17:59:34","date_gmt":"2017-02-10T01:59:34","guid":{"rendered":"http:\/\/www.podfeet.com\/blog\/?p=10990"},"modified":"2017-02-12T18:13:00","modified_gmt":"2017-02-13T02:13:00","slug":"backblaze","status":"publish","type":"post","link":"https:\/\/www.podfeet.com\/blog\/2017\/02\/backblaze\/","title":{"rendered":"Why I Switched to Backblaze from CrashPlan"},"content":{"rendered":"

\"Backblaze<\/a>In March of 2013 <\/a> I finally got on the bandwagon of doing offsite backups. Backups in general are the kind of task that sounds hard and annoying but if you haven’t tried lately are easy. Once I had CrashPlan running, it ran flawlessly for three and a half years.<\/p>\n

One of the features I liked about CrashPlan is that when you get a new machine, they allow you to adopt the previous backup. That means that you don’t have to re-upload all of your data, you just tell CrashPlan to point the old backup to the new machine.<\/p>\n

Fast forward to November of last year when I got the new Touch Bar MacBook Pro. I happily installed CrashPlan and told it to adopt the backup of my 2013 Retina MacBook Pro. And that’s when the nightmare started.\"CrashPlanCrashPlan goes through several phases during initial backup and also during adoption. It likes to synchronize file information. It likes to synchronize block information. One of my favorites is Cache Pruning versions. Sometimes it even likes to start running the backup. It gets bored with that though and goes back to the old standby of synchronizing block information.<\/p>\n

I failed\u00a0to get\u00a0CrashPlan to complete a\u00a0single successful \u00a0backup on my new machine for a full month. \u00a0On December 28th I \u00a0finally wrote to Code42, the makers of CrashPlan. My little friend Lawrence from Code42 and I began a long and stressful relationship. To give you an idea of how many conversations we’ve had trying (unsuccessfully) to get this working, I copied and pasted our email thread into ByWord and found we have written 9450 words to each other … so far.<\/p>\n

\"CrashplanWhen Lawrence was helping, he seemed to know what he was talking about and do some real work. He was trying to clean out files that appeared to be boogering up the database (my words, not his) and doing other maintenance that required me to uninstall and reinstall. Even when things appeared to be working, CrashPlan would upload at a positively glacial speed. I’m talking 300KB\/sec on a good<\/em> day. He would assure me that it would speed up eventually and the screens that said “3.4 months to go” weren’t correct. I have around 700GB online at CrashPlan, so at the speed of 300KB\/sec, that would be 216 days to complete (if my cipherin’ is correct).<\/p>\n

But the worst part of all of this is that twice Lawrence fell ill. Worse for him than me, I’m sure. But CrashPlan had no one reading his email to ensure that his customers were cared for! At one point, 8 days went by with no response from my repeated attempts to ask him what was going on. Finally in desperation I tweeted Code42 simply asking them to check to see if Lawrence was ok. Seriously, I wasn’t mean at all, I really wondered if he was ok.<\/p>\n

After that tweet, Donny stepped in for a few days at which point Lawrence and I were reunited. As I explained to both of them, I think it’s inexcusable for a company to leave a customer unable to use the service for which they’re paying just because the one person they were working with was out ill.<\/p>\n

But here’s where the story takes an interesting turn. My good friend Pat Dengler of Dengler Consulting<\/a> has been nagging me for ages to dump CrashPlan in favor of Backblaze. In her Apple Certified consultant’s role, she’s found it easier and better than CrashPlan and highly recommended it.<\/p>\n

So while I was waiting for Lawrence, this week I downloaded the free 15 day trial of Backblaze. I told Pat that I was doubtful this would be enough time for a real test, because in 2013 when I did my initial backup to CrashPlan, it took 3 weeks for all of my data to go up to their servers. I soldiered on with my testing in spite of my concerns.<\/p>\n

\"BackblazeWhere CrashPlan is a Java application (which is inaccessible by the way), Backblaze installs as a System Preference pane. It has six tabs within it and my favorite is the Performance tab. By default, Backblaze has automatic throttling. You can imagine that if you’re trying to watch Netflix, you probably don’t want your backup sucking up all of your available bandwidth. But in my case I actually do<\/em> want to flood the pipes.<\/p>\n

If you disengage automatic throttle, you get a slider from left to right with faster network on the left, and faster backups on the right. Needless to say, I pushed it to 11. You also get an option to set the number of backup threads. They recommend 1 thread, but since they gave me an option of 10, I chose that.<\/p>\n

At this point, I should mention that I’m lucky enough to have FiOS in my house, so I regularly see 80-100mbps upload on speed tests. After I cranked up Backblaze to the fastest possible, I was shown a transfer speed of 208.14Mbps. Remember CrashPlan? That was at 2.4mbps. So 100x the speed. But could Backblaze really do this in an actual upload?<\/p>\n

I deselected only my Movies directory and which left it close to 650GB to back up to the Backblaze servers. And I pushed back up now. I left it running in the background, fully expecting this to take weeks. But it didn’t.<\/p>\n

\"BackblazeInstead….it only took Backblaze 18 hours to upload 641GB of data. 735 thousand<\/em> files. Seriously. It finished in far less than the elapsed time between any of my requests to Lawrence to receive a reply.<\/p>\n

The entire time it was uploading, it showed me what file it was working on and how many files were left and how much data was left to upload. Great feedback so I knew exactly how well it was going.<\/p>\n

The system preference pane for Backblaze also has a schedule tab which you can change from continuously (which they recommend) which is actually hourly, or you can choose once a day, or only when you push the backup now button. You can use the Exclusions tab to keep Backblaze from backing up specific folder, or even by file extension type. There are a fair number of file types not included by default. For example if you have sparse image bundles or you save disk images of installers, those aren’t backed up. Probably good to take a look at that section to make sure nothing you care about is in the list.<\/p>\n

On the security tab, they outline their default security:<\/p>\n

Files scheduled for backup are encrypted on your machine using AES military grade encryption. These encrypted files are then transferred over a secure SSL connection directly to the Backblaze data centers, where they’re stored encrypted on disk. Data will only be decrypted per your request using your email and password.<\/p><\/blockquote>\n

If that’s not enough for you they go on to explain how you can create a private encryption key to secure your data. If you choose this option, you have to safeguard this private encryption key, because they will never be able to decrypt your data for you.<\/p>\n

\"BackblazeFinally they have reports that are really fun. \u00a0I can see how many files I have backed up, and a high level understanding of their final types. For example, it shows that I have 400 GB of photos and movies, and only 16 GB of music. And to be honest, I’m pretty sure it’s mostly podcasts in that music category, stored in my iTunes library. In that same report tab you can also check to see if there are any issues pending for your next backup.<\/p>\n

On the settings tab you can set when you want to be warned if you haven’t been backed up, anything from 1 to 7 days or even never. Also on the settings tab you can inherit a back up state from a previous computer. This is exactly like the backup adoption that I mentioned you can get with CrashPlan.<\/p>\n

I also ran a successful test to make sure I can retrieve files. You log into your Backblaze account on the web, identify the files that you want to retrieve, and then they zip them up and send you a link to download those files. Zip file downloads are limited to 500GB (which is probably enough for most normal people), but if it’s not you can submit up to 5 concurrent.<\/p>\n

If you have a medium-size catastrophe, up 128 GB GB of data you need to retrieve, you can choose to have them send you your data on a USB flash drive for $99. If things really go belly up on you, they’ll send you up to 4 TB of data on a hard drive for $189. Get this though, if you send the flash drive or the hard drive back, you get a full refund<\/em>. That’s pretty cool.<\/p>\n

For a single computer, CrashPlan and Backblaze are the exact same price. If you pay for a full year in advance, they both charge $5\/month. CrashPlan has one edge over Backblaze, and it’s that they also offer a family plan. You can back up 2-10 computers for $12.50\/month. Backblaze doesn’t offer a family plan, so if you have a lot of computers for which you require offsite backups, CrashPlan would be a better deal for you. CrashPlan also allows you back up network attached storage, which I always thought I’d do but never even tried. Backblaze recommends Synology NAS because they have their Cloud Sync software which syncs to Backblaze’s B2 service.<\/p>\n

Needless to say, I’m switching over to Backblaze because of the nice interface, and because of the speed, and well, mostly because they actually can<\/em> back up my computer.<\/p>\n","protected":false},"excerpt":{"rendered":"

In March of 2013 I finally got on the bandwagon of doing offsite backups. Backups in general are the kind of task that sounds hard and annoying but if you haven’t tried lately are easy. Once I had CrashPlan running, it ran flawlessly for three and a half years. One of the features I liked […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":true,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[147],"tags":[63,1090,1462],"class_list":["post-10990","post","type-post","status-publish","format-standard","hentry","category-blog-posts","tag-backups","tag-customer-service","tag-offsite-backups"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/10990","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/comments?post=10990"}],"version-history":[{"count":11,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/10990\/revisions"}],"predecessor-version":[{"id":11016,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/10990\/revisions\/11016"}],"wp:attachment":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/media?parent=10990"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/categories?post=10990"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/tags?post=10990"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}