CrashPlan Shuts Down

Code42, the company behind CrashPlan, has decided to shut down its popular home cloud backup service to focus on its business customers. Bigger fish to fry!

At first, I received a few emails to migrate to CrashPlan for Small Business for free, then get 75% off. I had enough with CrashPlan and its intricacies, and I’ve been meaning to cancel my subscription as I purchased a year long subscription well before I switched to something else. I decided to cancel my subscription. A day later, I get an email saying that CrashPlan is quitting their home subscriptions. SUPPLIES!

Having used CrashPlan for a few years now. Personally and for my business and also for some of my clients. The service was excellent albeit with a few hiccups, but it did it’s job and in the end all good things must come to an end.

CrashPlan as a service did have quite a few nice concepts. The revision based file restores, the deduplication, the ability to use a friend’s computer as a remote backup destination. All of this was quite nice an innovative.

Unfortunately, innovation comes at a cost and even after all these years, I still didn’t quite manage to completely backup the computer I was “backing up.”

Backed up: 17.1TB/25TB

Plenty of things to backup, right? Yes, but fortunately, I never had to use CrashPlan for real, except for some ridiculous finger slips of the Delete button.

The CrashPlan software is also written in Java, which made things quite… Interesting and frustrating. In the beginning, when my backup size approached 5TB, it kept crashing and restarting and spontaneously just plain stopping. Fiddling with the memory within its console seemed to fix things up for a while, but it would be so memory hungry some times, it would actually eat up more than its fair share of RAM. You could feel the effects of it running even when you had a few terabytes of HDD free, 64 GB of RAM and eating up 50%+ CPU.

My frustration and the decision to look for something else came at the point where my computer ran out of space completely.. (remember, several terabytes free) Mysteriously filled up by?? CrashPlan updates.

The client would download and redownload the same update executable over and over and over again, filling up the entirety of the free space I had, completely crashing and simply not backing up anymore.

Monitor your free space, you say? Background service shouldn’t take up a few terabytes of space downloading an update, I say!

These days, I have switched completely to Backblaze and the difference is staggering with their native client. The only thing left is for them to have a native Linux client.

Until the next Titanic, thank you for flying Fremen Air.