NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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...
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
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 :)
Bogus,
I just checked again. I can connect to the CrashPlan of the NAS from the GUI of the client only if the ui.info port is set to 4243 !! Thus for me it works like that:
My ReadyNAS /var/lib/crashplan/ui.info:
4243,xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,192.168.0.120
My Windows Client: c:\ProgramData\CrashPlan/.ui_info:
4243,xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,192.168.0.120
A second thing to know: backup your new ui.info of the client (as it can be overwritten if Crashplan is started on the client in "server" mode).
Now from tutorial your client connects directly to the NAS.
To connect the client as a "Crashplan client" of the NAS, what you need to do is to :
- Stop/kill the Crashplan service on your client PC
- reverse the ui.properties to serviceHost=127.0.0.1 and servicePort=4243
- restart CrashPlan
Now that way the GUI login in to the PC (not to the NAS) then you have to tell the PC to backup to the NAS using the code from the Crashplan server of the NAS.
If you want to go back to controlling the NAS Crashplan from the PC. You have to redo the ui.properties (actually I just uncomment the IP of the NAS and ServicePort=4200)
Also do not forget to overwrite you ui.info with the backup ui.info (every time you will switch from NAS to PC it will be overwritten.
jclaracq wrote:
Bogus,
I just checked again. I can connect to the CrashPlan of the NAS from the GUI of the client only if the ui.info port is set to 4243 !! Thus for me it works like that:
My ReadyNAS /var/lib/crashplan/ui.info:
4243,xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,192.168.0.120
My Windows Client: c:\ProgramData\CrashPlan/.ui_info:
4243,xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,192.168.0.120
You need to leave the ports at 4243 because you aren't tunneling through putty. I always start with putty myself, so I can access the crashplan logs, etc directly from linux - and then launch the client if there's something there I want to see or change. So 4200 works for me,
Also, I don't think you need to change the IP address on the NAS - 127.0.0.1 (localhost) should work too, and is easier to manage overall (fewer things to touch later if the IP address changes). Your method does require setting the NAS IP address on the client (and mine requires leaving it alone).
jclaracq - if you want edits to the main post, then let me know what they are - I can apply them for you.
Also, you might consider listing both the putty and direct configuration options in the main post, so both are documented.
StephenB wrote:
jclaracq wrote:Bogus,
I just checked again. I can connect to the CrashPlan of the NAS from the GUI of the client only if the ui.info port is set to 4243 !! Thus for me it works like that:
My ReadyNAS /var/lib/crashplan/ui.info:
4243,xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,192.168.0.120
My Windows Client: c:\ProgramData\CrashPlan/.ui_info:
4243,xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,192.168.0.120
You need to leave the ports at 4243 because you aren't tunneling through putty. I always start with putty myself, so I can access the crashplan logs, etc directly from linux - and then launch the client if there's something there I want to see or change. So 4200 works for me,
Also, I don't think you need to change the IP address on the NAS - 127.0.0.1 (localhost) should work too, and is easier to manage overall (fewer things to touch later if the IP address changes). Your method does require setting the NAS IP address on the client (and mine requires leaving it alone).
jclaracq - if you want edits to the main post, then let me know what they are - I can apply them for you.
Also, you might consider listing both the putty and direct configuration options in the main post, so both are documented.
Sorry my bad.
My Windows Client: c:\ProgramData\CrashPlan/.ui_info:
4243,xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,192.168.0.123
That is what I have too.
Regarding "the IP address on the NAS - 127.0.0.1 (localhost) should work too"
I doubt it (but don't know for sure), because it might only listen to itself (hence localhost). Chaning it to 0.0.0.0 makes more sense, in particular when using DHCP as the IP address of the ReadyNAS might change.
Stephen can you also attach files to my or the 1st post? These .so files are required for ARM.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
