Forum Discussion

Star

Aug 21, 2016

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 can make an install script from it?

This was adapted from:http://ptarmiganlabs.wordpress.com/2013/06/23/netgear-readynas-rn312-hello/

Step 1: Installation
Add some tools to READYNAS:

apt-get install apt-utils
apt-get install dialog

dpkg-reconfigure debconf

Set the debconf level to "dialog" and "medium"

It turns out the pre-installed version of cpio doesn't quite cut it. Replace it:

apt-get remove busybox-cpio
apt-get install cpio

Make a temp directory

mkdir /tmpcd
cd /tmpcd

Download last version of linux CrashPlan (Check on website)
wget https://download1.code42.com/installs/linux/install/CrashPlan/CrashPlan_4.7.0_Linux.tgz

Unzip the file:
tar -xvzf CrashPlan_4.7.0_Linux.tgz

cd crashplan-install
./install.sh

if upgrading, you need to remove a previous version: ./uninstall.sh -i /usr/local/crashplan

CrashPlan will install to: /usr/local/crashplan or install in /apps/crashplan
And put links to binaries in: /usr/local/bin
And store datas in a share (I prefer to put it on a USB media to not waste space on NAS): /media/USB_HDD_2/crashplan-backup (or /data/crashplan)
Your init.d dir is: /etc/init.d
Your current runlevel directory is: /etc/rc5.d
Is this correct? (y/n) [y]

Now we are going to do few customizations:

stop CrashPlan:
service crashplan stop
or run: /usr/local/crashplan/bin/CrashPlanEngine stop

Backup my.service.xml:

cp /usr/local/crashplan/conf/my.service.xml /usr/local/crashplan/conf/my.service.xml.orig

With your favorite editor, edit /usr/local/crashplan/conf/my.service.xml
example: nano /usr/local/crashplan/conf/my.service.xml

On the line that says ServiceHost. Replace 127.0.0.1 with IP of the NAS (the one from your LAN like 192.168.0.120) and then save the file and exit nano
Move CrashPlan cache and log directories to new locations or it will full your system partition

mkdir /media/USB_HDD_2/crashplan

ls -lah /usr/local/crashplan/cache/
mkdir /media/USB_HDD_2/crashplan/cache
mv /usr/local/crashplan/cache/* /media/USB_HDD_2/crashplan/cache/

ls -lah /usr/local/crashplan/log/
mkdir /media/USB_HDD_2/crashplan/log

vi /usr/local/crashplan/conf/my.service.xml
Change the paths as neeed for your choice of new directories:
look up for cachePath and FilesLog.

For example:

<cachePath>/usr/local/crashplan/cache</cachePath>
to
<cachePath>/media/USB_HDD_2/crashplan/cache</cachePath

And finally check free disk space on /:
/usr/local/crashplan/log# df -h

Restart crashplan:
service crashplan start
or run: /usr/local/crashplan/bin/CrashPlanEngine start

Reset debconf to non-interactive (using "noninteractive" and "medium" as settings):
dpkg-reconfigure debconf

Step 2. Configuration
These instructions are based on those available on CrashPlanís support site.

1. Install the client on your laptop or desktop from CrashPlan site. Note this is the consumer version - Enterprise version can be obtained from here.

2. Before doing anything else, exit the CrashPlan client if it is running, then edit the ui.properties file located in one of these folders:

Linux (if installed as root): /usr/local/crashplan/conf/ui.properties
Mac: /Applications/CrashPlan.app/Contents/Resources/Java/conf/ui.properties
Solaris (if installed as root): /opt/sfw/crashplan/conf/ui.properties
Windows: C:\Program Files\CrashPlan\conf\ui.properties?

and ensure the following line:?
#serviceHost=127.0.0.1
#servicePort=4243

is modified to look like this (if not there at all, add it), then save the file:?
serviceHost=your_NAS_IP
servicePort=4200

Step 3. Newer releases of Crashplan require you to copy a UI key form the backend service on the headless system (the ReadyNAS in our case) to the client system (the computer we are using the desktop app on).

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).
For example...

ReadyNas .ui_info
4243,87a4cc89-09ac-495e-946e-ed1c3642a909,192.168.0.120

should be copied to the client and changed to

IMPORTANT Do not change port 4243 to 4200 !

4243,87a4cc89-09ac-495e-946e-ed1c3642a909,192.168.0.120

The correct client file will be in the location below depending on your client OS.

Locations Of .ui_.properties (source)

Windows Vista, 7, 8, 10, Server 2008, and Server 2012
Installed for everyone: C:\ProgramData\CrashPlan\conf
To view this hidden folder, open Windows Explorer and paste the path in the address bar.
Installed per user: C:\Users\\AppData\<Local|Roaming>\Programs\CrashPlan\conf
To view this hidden folder, open Windows Explorer and paste the path in the address bar.
Windows XP
Installed for everyone: C:\Documents and Settings\All Users\Application Data\CrashPlan\conf
To view this hidden folder, open Windows Explorer and paste the path in the address bar.
Installed per user: C:\Documents and Settings\\Application Data\Programs\CrashPlan\conf
To view this hidden folder, open Windows Explorer and paste the path in the address bar.
OS X
Installed for everyone: /Library/Application Support/CrashPlan/conf/.ui_.properties
Installed per user: ~/Library/Application Support/CrashPlan/conf/
Linux: /usr/local/crashplan/conf
Solaris: /opt/sfw/crashplan/conf
Now fire up your desktop app and you should be greeted with the setup process.

4. Open the CrashPlan app on your client and setup CrashPlan as per their instructions on their site.

5. Once setup, close the CrashPlan client app, close your terminal window and edit the ui.properties file again to remove the line you added or modified, saving when done.

6. You can then load up your client and set it up, and as with any other clients you also install the CrashPlan app on to (and either login with same account, or using your CrashPlan ìFriend Codeî) you will then be able to see your ReadyNAS as a backup destination (under ìComputersî)?. If you have more than one ReadyNAS that you install this on to, you can also setup backups to run between

CONGRATULATIONS YOU ARE DONE!

ReadyNAS Backup

38 Replies

Bogus
Tutor
Aug 31, 2016
Could you please check step 3, because it's not really clear. Should I or shouldn't I change the port number from 4243 to 4200?
- StephenB
  Guru
  Aug 31, 2016
  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
    Tutor
    Aug 31, 2016
    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 :)
jclaracq
Star
Oct 03, 2016
I noticed as well that my crashplan stopped to work about a week ago. I will check that as soon as I can and update the tuto if necessary. As StephenB said Crashplan installs its own java package. But I can only speak for x86 version
- jplee3
  Apprentice
  Oct 03, 2016
  Thanks! I don't think this is really going to be an issue for x86/Intel-based NASes, as I would expect the JRE that CP precompiles to run just fine. It really looks like it's an issue with ARM-based NASes. And before, this was only really an issue of pointing CP to use the Java/JRE compiled for ARM on the NAS (rather than CP's precompiled version). Now the issue appears to be that CP added another precompiled library dependency (which only works in x86), so even if users of ARM-based NASes point CP to use the system JRE, the CP service will still fail because that other CP-specific library can't load in the ARM environment.
  - john_h1
    Tutor
    Oct 04, 2016
    Yup, Crashplan has stopped working for me too on my RN316 ReadyNAS. I'm thinking about dumping Crashplan altogther and just use sync with Dropbox for my important files.
oshae
Tutor
Oct 05, 2016
I'm running 4.2.28 on a Pro 6.

I've been using the Java 7 addon from RNSXtras for quite some time now. My CrashPlan 4.7 install tried to upgrade to 4.8 I believe on Sept 29. It tried to download the new JVM and was unable to because of the wget cert check issue. It filled the /usr/local/crashplan/upgrade folder with multiple attempts and filled my root volume. Luckily I was still able to boot up and SSH in. I modified .wgetrc according to a post I found and this page (I can't find the forum post anymore).

http://www.elftronix.com/how-to-automatically-skip-wget-ssl-certificate-check/

I managed to delete everything in the upgrade folder to reclaim the root volume space. After making that change to wget, CrashPlan tried to upgrade again. This time it was able to download the Java 1.8 and it successfully upgraded to 4.8. JAVACOMMON in my install.vars is now pointing to /usr/local/crashplan/jre/bin/java.

Everything seems to be working fine. I'm guessing parts of this have already been posted somewhere on the forums but I thought I would just post my experience in case anyone runs into the same problem.

Can I assume there is no need for the Java 1.7 addon from RNSXtras anymore?
- jplee3
  Apprentice
  Oct 05, 2016
  I may just ditch Crashplan and move over to Amazon Cloud Drive. Pricing seems reasonable at $60 for unlimited storage... my CP plan expires in December anyway.
  - oshae
    Tutor
    Oct 05, 2016
    I still really like CrashPlan and recommend it all the time. Even a free setup where you cross backup between 2 clients is very handy. I have the CP family plan, so I can put my parents machines on it as well. The day they have a hard drive failure I know it will be simple for me to restore their stuff for them. Puts my mind at ease.
    
    How would you use ACD with the ReadyNAS? There is no addon that I am aware of. Then again I'm not on OS6.