He would assure me that it would speed up eventually and the screens that said “3.4 months to go” weren’t correct. Even when things appeared to be working, CrashPlan would upload at a positively glacial speed. 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. When Lawrence was helping, he seemed to know what he was talking about and do some real work. 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. My little friend Lawrence from Code42 and I began a long and stressful relationship.

On December 28th I finally wrote to Code42, the makers of CrashPlan. I failed to get CrashPlan to complete a single successful backup on my new machine for a full month. It gets bored with that though and goes back to the old standby of synchronizing block information. Sometimes it even likes to start running the backup. One of my favorites is Cache Pruning versions. It likes to synchronize block information. It likes to synchronize file information. CrashPlan goes through several phases during initial backup and also during adoption. I happily installed CrashPlan and told it to adopt the backup of my 2013 Retina MacBook Pro. 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.įast forward to November of last year when I got the new Touch Bar MacBook Pro. One of the features I liked about CrashPlan is that when you get a new machine, they allow you to adopt the previous backup. Once I had CrashPlan running, it ran flawlessly for three and a half years. Backups in general are the kind of task that sounds hard and annoying but if you haven’t tried lately are easy. In March of 2013 I finally got on the bandwagon of doing offsite backups.

Code42 crashplan pricing