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.
#Crashplan 6.7 download for mac trial#
So while I was waiting for Lawrence, this week I downloaded the free 15 day trial of Backblaze. In her Apple Certified consultant’s role, she’s found it easier and better than CrashPlan and highly recommended it. My good friend Pat Dengler of Dengler Consulting has been nagging me for ages to dump CrashPlan in favor of Backblaze. 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.īut here’s where the story takes an interesting turn. Seriously, I wasn’t mean at all, I really wondered if he was ok.Īfter that tweet, Donny stepped in for a few days at which point Lawrence and I were reunited. Finally in desperation I tweeted Code42 simply asking them to check to see if Lawrence was ok. 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. 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).īut the worst part of all of this is that twice Lawrence fell ill. 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.
#Crashplan 6.7 download for mac full#
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.
0 kommentar(er)
