![]() I haven’t accepted a solution yet.įor now, the situation is unresolved, and my data is still gone. He also confirmed that I’m the only account that this data loss situation happened with, and that they’re interested in finding a suitable solution. this evening about the issue – he was a nice, knowledgable guy, and offered me a 2tb seed drive to re-seed my data. I had a brief call with tech manager Brad W. So when I received the below email this afternoon, I was extremely disappointed and immediately concerned for the safety of my now un-backed-up data, but unfortunately I wasn’t very surprised – this is just the kind of disaster I’ve come to expect from Crashplan.īelow you’ll find a transcript of my current support history, starting from the time when I reported my “unable to backup” issue, and ending with my response to their meager attempt to remedy the situation. I’d wait days to get a response, had multiple support agents dealing with my case on multiple threads – the whole thing was a mess. And throughout all of these issues, Crashplan support sucked. Sure they give big warnings of this, but a small grace period would be nice. The UI was finicky – if the wrong settings were changed, my entire backup archive would be expunged by the system – with no time to go back and undo anything. The backup service would load slowly, and would frequently re-scan my computer. I would usually only see 100kbps or so upload speed, even when I knew I had much more bandwidth. Backup upload speed was nothing like I saw using Backblaze. However, over the last few months of using it, and leading up to this giant Crashplan data loss disaster, have seen a darker side. My initial impression of Crashplan was good – a flexible service with lots of configuration options. Note that nowadays, I believe that Backblaze retains data for 3-6 months, which is much much better.Īnyway, I decided that having longer than 1 month retention times for my data was important, and switched to Crashplan. Because of this little quirk of their service, I decided to switch backup providers to Crashplan. Backblaze would delete data from my archive if it didn’t see that data connected to my computer for a month – so if I went on vacation for 2 months and stored away my external hard drives, my data would be automatically expunged at the end of the first month. However, the one thing Backblaze didn’t do at the time was offer unlimited, or very long retention. Backblaze was great – a lightweight, easy to use front end, fast backup speed, low system resources, good support response times, and most importantly, a reliable service. Before I switched to Crashplan, I was using Backblaze for online backup. I’ve been using online backup for a number of years. ![]() And Crashplan doesn’t seem to have any remorse. It’s gone – my entire online backup archive of all of my data – my life’s work – 2.4 tb of everything – completely gone. That’s right, Crashplan lost all of my data, unrecoverably. Clearing the CrashPlan cache is the solution.After almost an entire week of not being able to backup to Crashplan because of “archive maintenance” on their part, I was informed today that instead of merely maintaining my backup archive, Crashplan LOST THE ENTIRE THING. In this case, there may have occurred acorruption in one of the CrashPlan cache files. Right click "CrashPlan Backup Service" and choose "Start"Īfter an unexpected stop of the computer and/or the CrashPlan PRO software, the message " Unable to connect to the - local backup engine - retry?" may appear after launching CrashPlan.$ sudo launchctl load /Library/LaunchDaemons/ Restart the Mac OS X service via Terminal.app with the command:.There are various ways to restart the CrashPlan engine: Restarting the CrashPlan engine is the solution This occurs only once, and only in a singular event (not on every new installation), and within about fifteen minutes after the end of the installation process. In a new installation, this engine can stop by itself. after an unexpected stop of the computer and/or the CrashPlan softwareĪfter an initial installation of the CrashPlan PRO software, after starting the CrashPlan application the message appears " Unable to connect to the - local backup engine - retry?" The CrashPlan software consists of two parts:.within approximately fifteen minutes after a first install of the CrashPlan software. ![]() There are two common situations where this occurs: Unable to connect to the - local backup engine
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |