Crashplan promo how to#
Crashplan promo install#
Crashplan promo update#

I went down the simpler route of rather than trying to be clever and reinstall crashplan each boot and copy configs over - simply install it once, configure it to login to my account and then tarball the entire /usr/local/crashplan directory up and untar it each boot.Īgain this works as long as theres no reboot.

I'm sure someone here knows how to accomplish this.

What would be really nice is to pair CrashPlan with a script that turns all the computers on for several hours during the middle of the night to update and verify backups, then turns them all off again once it is complete. I'm not giving my parents a choice about it, though, I'm just going to set it up for them and make them use it (well, it runs automatically so they don't really have to do anything). My only difficulty thus far is convincing my friends to start a backup ring with me - for some reason they are very hesitant (they don't want to feel obligated to leave their computers on one night per week to make sure the backups are up to date). So in short, CrashPlan works perfectly as far as I can tell. Perhaps I'll simulate a crash and make sure the restore function works. I haven't tried to restore any files yet, since I haven't needed to. The backup was originally going to take several hours over wireless, so I plugged in my laptop to my LAN and it dropped to about half an hour. I'm backing up just under 10 GBs from each (mainly pictures and documents), and after using the 'compact' feature, the used disk space dropped to about 7 GBs each. It works just fine between my Vista 圆4 Desktop and my Vista x86 Laptop, just not with my unRAID server. I am, in general, a bit alarmed that it' so fragile to a reboot.

So more investigation required! Not quite as easy as I'd hoped. I had thought I'd archived all the files necessary to contain this but it would appear I've missed something or it doesn't behave how I think. I'm not sure how it generates this id or where it stores it. Unfortunately this was a manual operation and it also meant any backups were removed as part of the process.

I had to completely remove it from my crashplan account and re add as a new machine before my clients would see and connect to it again. But as soon as I actually rebooted although crashplan reinstalled ok and came back up its internal id seemed to have changed. It worked in isolation - copying the configs and then uninstalling crashplan before reinstalling and copying the archived configs back and then starting the server made the whole thing seamless. Copying the config files generated across during the intial install as well to, in theory, avoid the step of having to login and setup the account again.īUt this didn't work. I also hacked their install script to remove all interactivity and hardcode the install paths to allow it to install from the go script at boot time. I then connected to the server from my windows desktop by changing the client config and configured the unraid crashplan install to login to my account.īackups to it then worked as you'd expect and files were only opened on the array when backups were in progress - so idle disk spindown and the ability to stop the arrary was not impeded. I've managed to install it and lnk the backup folder onto the array.

Crashplan promo