NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
jclaracq
Aug 21, 2016Star
Tutorial to install CrashPlan (updated August 2016)
Hello everyone, As I have reinstall CrashPlan on my ReadyNas today. I thought I will share with everyone my updated notes. Feel free to comment to improve this step-by-step. Maybe a clever person...
StephenB
Aug 31, 2016Guru - Experienced User
There's more than one way to set this up, but here is what I do:
My ReadyNAS /var/lib/crashplan/ui.info:
4243,xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,127.0.0.1
My Windows Client: c:\ProgramData\CrashPlan/.ui_info:
4200,xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,127.0.0.1
And putty (Windows) SSH->tunnels configuration:
L4200 localhost:4243
Bogus
Aug 31, 2016Tutor
Sorry for the confusion but what I mean is that there's a contradiction in setp 3 of the tutorial:
First you write to change the number: "Copy the contents of /var/lib/crashplan/.ui_info on the ReadyNAS to the appropriate file on your client computer (see below) making sure to change the the first number (4243) in the file to the forwarded local port (4200)."
And then you write NOT to change the number: "IMPORTANT Do not change port 4243 to 4200 !"
Anyway, here's how I got it working without the need of Putty and opening SSH tunnels:
In the client's ui.properties, I changed
#serviceHost=127.0.0.1 #servicePort=4243
to
serviceHost=192.168.0.123 servicePort=4200
My ReadyNAS /var/lib/crashplan/ui.info:
4243,xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,192.168.0.123
My Windows Client: c:\ProgramData\CrashPlan/.ui_info:
4200,xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,192.168.0.123
(192.168.0.123 is the IP address of the ReadyNAS.)
On my ReadyNAS 204 (with ARM processor), I needed to change the JAVACOMMON variable to the correct java executable in the install.vars file in the root of your crashplan install directory.
JAVACOMMON=/usr/bin/java
Also I needed to change the files libjtux.so and libmd5.so (located in /usr/local/crashplan).
(How can I attach those files here?)
Another change is that ReadyNAS devices boot at runlevel 2 but the installer creates the “init.d” startup script in “rc5.d“. If you were to reboot, your service would never start so we fix it like so:
cd /etc/rc2.d/ ln -s ../init.d/crashplan S99crashplan rm /etc/rc5.d/S99crashplan
After some research I also found that: CrashPlan just stays on 'waiting for backup' forever. I did an 'apt-get install libjna-java' and created a symbolic link from '/usr/lib/jni/libjnidispatch.so' to '/usr/local/crashplan'. You can also copy the file."
Two other files that I replaced are: jna.jar and jna-platform.jar -- I used symbolic links from /usr/share/java/jna.jar and /usr/share/java/jna-platform.jar to replace the /usr/local/crashplan/lib/jna.jar and /usr/local/crashplan/lib/jna-platform.jar (the files are installed after apt-get install libjna-java)
Somehow changing the log an cache paths in my.service.xml doesn't seem to do anything. log and cache are still in the same space. Perhaps that's an ARM thing, I dont know...
Other than that Crashplan is backing up :)
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!