Well… I can no longer recommend CrashPlan, even using my fix below. I recently upgraded my file server, performed a computer adoption according to CrashPlan’s instructions…. and CrashPlan lost all of my backups from that machine. All 16TB or so or them. It also lost my backup set definitions after the adoption.
CrashPlan support was… not particularly helpful. They claim they see the 16TB of data attached to the right computer GUID, but I can’t see the data in my client, and when I look at my account in the CrashPlan web interface, I see nothing. Support said it “might work” if I forced a backup to run… and it didn’t.
My CrashPlan account expires soon, and I won’t be renewing.
If my fix doesn’t work for you, try changing the server that you’re connecting to, as described HERE. Thanks to reader Jorgen for his comment with this tip! This will, unfortunately, mean starting your backups over from scratch.
Reading some of the recent comments on one of my previous posts, I’ve noticed that some people seem to be having problems following the instructions there — looking at the wrong XML files, forgetting to restart the CrashPlan service, etc. In the interest of making this fix more “user friendly”, I’ve developed some scripts for Windows and Linux that does some “automagic” — one-click fixes, basically.
Unzip all files to a directory somewhere, then run CrashPlanFix.bat as Administrator (right-click, Run as Administrator). You’ll see a window pop up showing some progress messages. As long as you don’t see any errors, everything should have worked properly.
Decompress the file and then run CrashPlanFix-Linux.sh.
Nothing yet — I don’t have access to any Mac systems.
(Update: 13 Feb 2014) Thanks to reader Bill W, Mac users can now feel the automagic love. Download his script for Mac HERE. Note that this will need to be run with elevated privileges via the ‘sudo’ command. Thanks Bill!