![]() So, here are some pictures to fill in the space where I should be offering thoughts. Everything is pretty much there, barring a few new files from iPhoto and They contact me when seed data is uploaded at their end.I box up hard drive and send by pre-paid courier back to CrashPlan.I attach hard drive to computer and add it as a destination.Support contact me to confirm my details.Again, here’re the rough steps, but you can look it up for yourself: So, Adrian Johnson from Code42 offered me the use of a seeded backup drive, and I must say it’s been a really smooth experience. So gigabytes of home movies and other media were, beyond Time Machine backups, at risk. This was one of my complaints with Backblaze – I couldn’t get all of the data I wanted to up to the provider due to the extraordinarily shitty ADSL1 connection at my house. You can read more about how that works here. So, the killer feature that CrashPlan offers for me, and residents of the US, is seeded backup. Additionally, I hope you appreciate just how hard it is to take photos that look this bad. Just a reminder, every product is different, and every user’s circumstances are different, so don’t complain to me if you find that CrashPlan isn’t for you. So I thought I’d do a post to cover off on some initial thoughts and feelings and provide some public feedback on how it went. So, a short time after my post on Backblaze and Mozy and why I was going for the cheapest (but not necessarily nastiest) personal cloud backup solution, the Australian arm of CrashPlan got in touch and offered to help get me started with them. So I’d like to publicly thank Daniel R at Code42 Support for his promptness and courtesy when dealing with me, as well as his ability to actually, well, resolve the issue. It’s also not a feature you really think about until you actually need it. The ability to re-attach / adopt backups with new / replacement / freshly re-installed machines is a really cool feature that no doubt is saving people a fair bit of angst. And resolved in about 52 hours (including about 12 hours of them waiting for me to send logs through). And then all I had to do was synchronize the changes. Once I’d re-installed everything, I could log back in with my normal credentials, and “adopt” the backup sitting in the Code42 DC that was assigned to my iMac. Custom installation (as user): ~/Library/Application Support/CrashPlan.Remove the following directory from your system:.Follow the prompts to complete the uninstall process.Press Command-Shift-G and paste /Library/Application Support/CrashPlan/Uninstall.app into the dialog.For a complete uninstall, the following steps need to be done (on Mac OSX). The instructions for this process can be found here. Still no go, so he had me do a full uninstall (I think with prejudice) and re-install. I’m fascinated by what the “maintenance queue” might be and how my archive ended up there. He then got back to me to advise that my archive was in a “maintenance queue” and he’d removed it from that queue and advised me to restart everything and see how it went. I sent through the logs and Daniel got back in touch to have me modify my settings.xml file. I hadn’t realised I could clicky on the CrashPlan icon in the main window to open up a console. A very nice gentleman named Daniel R got in contact with me and got me to send through some logs. I’d had this problem before with MozyHome (link), but with a smaller set of data, so wasn’t too keen to re-upload over 900GB again. I had a weird problem the other day on my main iMac where it looked like I had to re-seed all of my data. The client itself is easy to use, and the pricing has been reasonable in my experience. ![]() I’m a big fan of the Aussie DC presence and ability to use a local seed drive. I’ve signed up for another 3 years or so, so I’m fairly committed at this point. I’ve been happily using CrashPlan for about a year now, after publicly breaking up with MozyHome, and sleeping around on Backblaze.
0 Comments
Leave a Reply. |