Crashplan for Dummies, aka Step by Step :)

Crashplan for home?

What do you see if you enter

ps auxww | grep -i CrashPlanService

It should be something like this:

root        63   0.1  6.1   873644 126976   ??  SNs  Tue03PM  43:01.37 /System/Library/Frameworks/JavaVM.framework/Commands/java -Dapp=CrashPlanService -Xmn10m -Xms15m -Xmx512m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.net.preferIPv4Stack=true -Dsun.net.inetaddr.ttl=300 -Dnetworkaddress.cache.ttl=300 -Dsun.net.inetaddr.negative.ttl=0 -Dnetworkaddress.cache.negative.ttl=0 -DCP_USER_NAME= -DCP_USER_HOME= -cp lib/com.backup42.common.jar:lib/com.backup42.service.jar:lib/com.code42.backup.jar:lib/com.code42.bplusj.jar:lib/com.code42.messaging.jar:lib/com.code42.os.jar:lib/com.code42.peer.jar:lib/com.code42.utils.jar:lib/com.jniwrapper.jniwrap.jar:lib/com.jniwrapper.macpack.jar:lib/com.jniwrapper.winpack.jar:lib/jtux.jar:lib/trove-2.0.1.jar:lang com.backup42.service.CrashPlanService

Thanks for your quick reply Stephen!

Enterprise:/usr/local/crashplan/bin# ps auxww | grep -i CrashPlanService
root      6439  0.0  0.0   3840   500 pts/0    S+   10:23   0:00 grep -i crashplanservice
Enterprise:/usr/local/crashplan/bin#

I downloaded this file directly on the RN http://download2.us.code42.com/installs ... _Linux.tgz

You are right, it is not running.

Maybe try

cd /usr/local/crashplan/bin
./CrashPlanEngine start

and see if anything interesting is displayed (or if the service starts).

Enterprise:/usr/local/crashplan/bin# ./CrashPlanEngine start
Starting CrashPlan Engine ... Using standard startup
OK
Enterprise:/usr/local/crashplan/bin#

and if I check afterwards:

Enterprise:/usr/local/crashplan/bin# ps auxww | grep -i CrashPlanService
root      7136  0.0  0.0   3840   500 pts/0    S+   10:29   0:00 grep -i crashplanservice
Enterprise:/usr/local/crashplan/bin#

I have uninstalled and reinstalled it but no luck.

Edit: I seem to have found a solution by following this advice

Thanks to this post I found some comments that had the answer - the java path was wrong, and there was a file with one variable to fix it (http://blog.andrewkoebbe.com/posts/2014 ... dynas-102/). If you use the default installation location, crashplan installs under /usr/local/crashplan. Within that directory is a file named install.vars; where there is a variable JAVACOMMON, with a path to tell Crashplan which Java to use. The default value was the JRE inside the Crashplan installation folder - that was not working for some reason. I changed the variable to /usr/bin/java7 - pointing to the JRE installed for the entire readyNAS. Then, I simply ran /etc/init.d/crashplan start ...and crashplan fired up and is now running fine.

Crashplan downloads its own Java during the installation. How can I prevent that from happening?
Also, my Java folder seems to be: ./etc/frontview/addons/bin/EJRE/ejdk1.8.0_33/linux_i586/jre/bin/java

Is that supposed to be?

Hi,

As discussed elsewhere, I am now trying to put together an updated step by step guide for installing CP on an OS4 Intel x86 NAS. I hope this could be useful for someone. Please understand that I am not a Linux guru so I may say some nonsense, do not hesitate to point out what is wrong.

Below the tentative. I hope I can come back and amend it while we work on it. Otherwise I'll need the admin's help! :)

I have a question regarding the global Java location for the system. I do not think that using the link I mentioned is correct. It works, but not sure it's the right thing to do.
Also, is there an easier way to install Java by using apt-get?

Thanks everybody.

===========================

CrashPlan Headless install - For dummies . Updated for CrashPlan 4.3.0 - 07/07/2015

What is a 'headless' install?
CrashPlan can be installed directly on a NAS. It will run as a service in background. However, we cannot connect a monitor to operate CrashPlan's GUI directly on the NAS. This makes the NAS "Headless". To operate and configure CrashPlan on our NAS we will use CrashPlan for Windows/Mac/Linux and redirect the GUI so it controls the NAS instead.

INTEL x86 based NAS

Step 1: INSTALL SSH

SSH allows the user to open a Linux terminal screen on a Windows/MAC/Linux computer so the NAS can be operated at Linux level.

Install the following add-on http://www.readynas.com/download/addons ... .0-x86.bin by following the below steps:

- open FrontView
- Navigate to Add-Ons
- Click on ADD NEW
- Browse to the file and click UPLOAD AND VERIFY IMAGE
- The NAS will install the add on for you

To SSH into the NAS by putty (open source app)
- Download putty at http://the.earth.li/~sgtatham/putty/lat ... /putty.exe
- putty does not require installation. Double click on the file, type the IP address of your NAS on "HOST NAME (or IP address)". Make sure that CONNECTION TYPE is set to SSH and click OPEN
- Putty may warn you about some security issues, click on OK to continue
- login using root as user name and the password used for the admin user on frontview.
- nothing to do at this stage, just leave the window open.

Step 2: INSTALL JAVA (this is apparently not needed anymore from version 4.2.0 onwards)
- Browse to the Oracle website and download the latest x86 Linux Small Footprint – Headless The download page is: http://www.oracle.com/technetwork/java/ ... index.html
- Save the file on your NAS on the BACKUP share
- Download and install the following add-on: http://minimserver.com/downloads/EJREIn ... as-x86.bin
- The above add-on will install the Java package we have just saved on the BACKUP share. When Java has been installed, switch back to the SSH window (open a new one if you had to reboot the system) and type the following command:

java -version

If Java was correctly installed the system will reply with something like

java version "1.8.0_33"
Java(TM) SE Embedded Runtime Environment (build 1.8.0_33-b05, headless)
Java HotSpot(TM) Embedded Server VM (build 25.33-b05, mixed mode)

Step 3: INSTALL CrashPlan
Navigate to CrashPlan's website and download the Linux version. Save it on the BACKUP share of your NAS. using wget is easy but getting the URL is not. I believe this is an easier alternative.
Back on the SSH terminal window, type the following commands (assuming that CrashPlan_4.3.0_Linux.tgz is the file you've just downloaded)

cd /backup

ls

(this will list the files currently in your share. Identify the latest CrashPlan file you've just saved)

cp CrashPlan_4.3.0_Linux.tgz /root]

(replace CrashPlan_4.3.0_Linux.tgz with whatever is the file you've just downloaded)

- Now the file is being copied to the root folder. Navigate to the root folder and extract the archive

cd /root
tar -xvf CrashPlan_4.3.0_Linux.tgz 

(again, replace CrashPlan_4.3.0_Linux.tgz with whatever you've just copied)

Type ls and you will see a folder called CrashPlan-install. Navigate into it by typying

cd CrashPlan-install

- Run CrashPlan install by typing

./install.sh

You will be asked to accept the EULA conditions. Scroll down (by hitting space to browse an entire page at a time).

- Confirm all the default options but point 4

Do you accept and agree to be bound by the EULA? (yes/no) yes
What directory do you wish to install CrashPlan to? [/usr/local/crashplan]
What directory do you wish to link the CrashPlan executable to? [/usr/local/bin]
What directory do you wish to store backups in? [/usr/local/var/crashplan] /crash-backup
What directory contains your SYSV init scripts? [/etc/init.d]
What directory contains your runlevel init links? [/etc/rc2.d] 

- CrashPlan will ask a final confirmation

Your selections:
CrashPlan will install to: /usr/local/crashplan
And put links to binaries in: /usr/local/bin
And store datas in: /crash-backup
Your init.d dir is: /etc/init.d
Your current runlevel directory is: /etc/rc2.d

Is this correct? (y/n) [y] y

- CrashPlan will now install.

STEP 4: Change the default JAVA location being used by CrashPlan (This is apparently not needed from version 4.2.0 if you just let CrashPlan install its own version of Java)

You will need an FTP client such as FileZilla or WinSCP (both freeware).
On FileZilla create a new profile using the following setup

HOST: your NAS IP
PORT: Leave blank
PROTOCOL: SFTP - SSH File Transfer Protocol
LOGON TYPE: Normal
USER: root
PASSWORD: (your SSH/admin password)



- navigate to CrashPlan configuration file

/usr/local/crashplan

- Edit install.vars file using your favorite editor (Notepad++ recommended)

locate the following line:

JAVACOMMON=/usr/local/ (cannot remember the original path!)

replace the path it with the following: /etc/frontview/addons/bin/EJRE/ejdk1.8.0_33/linux_i586/jre/bin/java

the final string will be

JAVACOMMON=/etc/frontview/addons/bin/EJRE/ejdk1.8.0_33/linux_i586/jre/bin/java

Not sure about that, isn't there a less version-dependent link under Linux? If Java is updated the whole thing has to be amended

Save the file and upload it back (FileZilla will detect the changes and will suggest to upload the file)

STEP 5: amend configuration file on the NAS

You will need an FTP client such as FileZilla or WinSCP (both freeware).
On FileZilla create a new profile using the following setup

HOST: your NAS IP
PORT: Leave blank
PROTOCOL: SFTP - SSH File Transfer Protocol
LOGON TYPE: Normal
USER: root
PASSWORD: (your SSH/admin password)



FileZilla will land in the /root folder. Just browse back to navigate to the actual root (/) folder. Now you can browse/edit files without using Linux and its user-friendly interface :)

I recommend that you make a copy of the file my.service.xml.

Navigate to the following folder:

/usr/local/crashplan/conf

Make a backup of the file - or rename it

my.service.xml

Edit my.service.xml located in /usr/local/crashplan/conf. Use your favorite editor (Notepad++ recommended)

Find the below line

<serviceHost>127.0.0.1</serviceHost>

and change it to

<serviceHost>Your.NAS.IP.ADDRESS</serviceHost>.

(thanks to sdouek for the hint!)

Save the file, FileZilla will detect the changes and will ask you if you want to upload the file.

- Now restart CrashPlan (if it had ever started) by typing on the Terminal window

./usr/local/crashplan/bin/CrashPlanEngine restart

- Confirm that CrashPlan is running by typing

ps auxww |grep -i CrashPlanService

The system must reply with something like the below

root      4714 16.3 19.5 1262344 402020 ?      SNl  May30 213:54 /etc/frontview/addons/bin/EJRE/ejdk1.8.0_33/linux_i586/jre/bin/java -Dfile.encoding=UTF-8 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Xms20m -Xmx1024m -Djava.net.preferIPv4Stack=true -Dsun.net.inetaddr.ttl=300 -Dnetworkaddress.cache.ttl=300 -Dsun.net.inetaddr.negative.ttl=0 -Dnetworkaddress.cache.negative.ttl=0 -Dc42.native.md5.enabled=false -classpath /usr/local/crashplan/lib/com.backup42.desktop.jar:/usr/local/crashplan/lang com.backup42.service.CPService
root     16791  0.0  0.0   3840   504 pts/0    S+   08:54   0:00 grep -i crashplanservice

otherwise you will receive a much less interesting answer as the below

root      7136  0.0  0.0   3840   500 pts/0    S+   10:29   0:00 grep -i crashplanservice

In the latter, CrashPlan has not started.

STEP 6: Connect your Windows GUI to your NAS

As mentioned, now we need to configure and manage the 'headless' CrashPlan service on your NAS. It is running but it's not doing anything because it does not know what to do. To do so we will need to fool our Windows system so the CrashPlan GUI connects to the NAS without realising so.

First, download and run the latest Windows CrashPlan client on your Windows PC. Do not run it straight away.

Next, amend the windows client's configuration. This is your Windows computer, not the NAS!
Navigate to the client's installation folder and look for a file called ui.properties.
It should be on C:\Program Files\CrashPlan\conf\ui.properties

Edit the file by using a decent editor, the default Notepad won't work well. If you do not have Notepad++ or similar, you can open it by using WordPad which is installed by default under windows.

Find the following line:

#servicePort=4242

Replace it with:

servicePort=4200

Next find the following line

#serviceHost=127.0.0.1

replace it with

serviceHost=Your.NAS.IP.ADDRESS

Save and close the file.

Next, confirm that the relevant ports are being used on the NAS. Switch to the SSH terminal window (or open a new one). Type:

netstat -na | grep LISTEN | grep 42

the output should show that port 4243 is listening on the local address

username$ netstat -na | grep LISTEN | grep 42
tcp4       0      0  *.4242                 *.*                    LISTEN
tcp4       0      0  127.0.0.1.4243         *.*                    LISTEN

if you get no output, then we have a problem. Make sure that CrashPlan is running as described above.

From version 4.3.0 there is an additional step to be performed.

1 . Confirm your Windows GUI is version 4.3 and it is NOT running (you may have to kill the process "CrashPlanDesktop.exe" running in the background)
2. Connect to the NAS by FTP using ROOT credentials.
3.Copy the file .ui_info from your NAS to your computer:
.....On the NAS: .ui_info on NAS is probably located /var/lib/crashplan (unless you changed it from the default when installing)
.....On the PC: .uni_info on your desktop is located on C:\ProgramData\CrashPlan. (Rename your old .uni_info to .uni_info.orig)

Open the CrashPlan GUI on your Windows PC. It should now automatically connect to the NAS.
Click on SETTINGS/GENERAL. The NAS' name should be displayed under "Name for this computer".

Now you are configuring the CrashPlan service on the NAS. Remember: every time you need to do so, you will need to open a tunnel by opening putty as described above. If you saved the configuration (recommended), just click on ReadyNAS CrashPlan click LOAD and then OPEN. This will save you typing the same information every time.


Useful Documents/Tweaks

Instructions for the cache are here: http://support.code42.com/CrashPlan/Lat ... _Directory
You do need to preserve the linux EOL convention (either edit on the NAS, or use something like notepad++). The cache can become quite large.

Instructions for the archive directory are here: http://support.code42.com/CrashPlan/Lat ... _Is_Stored
Note this only matters of you are saving backups for other machines on the NAS (e.g., using the crashplan "friend backup" feature).

How to open a tunnel by using putty - useful to control CrashPlan remotely without having to port-forward anything more than port 22 (SSH port)

- Close all the open putty windows
- Open putty again. On the main "PUTTY CONFIGURATION" windows click on SSH and then TUNNELS on the left hand side.
- Type 4200 on the SOURCE PORT field
- Type localhost:4243 on the DESTINATION field.
- Click on ADD



Navigate to SESSION again and type the IP address of your NAS. Make sure the CONNECTION TYPE is set to SSH and port number is 22.

Because this will need to be done before running the CrashPlan GUI, I suggest you save the configuration before you connect to the NAS.

Type "ReadyNAS CrashPlan" on the SAVED SESSIONS field. Click on SAVE.

Now you can connect and establish the tunnel by clicking OPEN. Log in as usual.

From version 4.3.0 onwards there is an extra step:

edit C:\ProgramData\CrashPlan\conf\ui_username.properties (username will be your actual username)

Change

servicePort=4243

With

servicePort=4200

Various hints and tools

#As of CrashPlan 4.2, CrashPlan will install their Java to run with their software on you NAS. There is no need to install a new Java on your whole NAS.
#JAVACOMMON=/usr/local/crashplan/jre/bin/java
#CrashPlan tests their software with that specific Java. (Unless you want to do their Quality Assurance for them on a new Java :) )

#Seeing What Port NAS is Listening to.
netstat -na | grep LISTEN | grep 42

#Return code should look something like this:
tcp6 0 0 :::4242 :::* LISTEN
tcp6 0 0 ::ffff:YOUR.NAS.IP.ADDRESS:4243 :::* LISTEN

#Starting,Stopping CrashPlan.
#/usr/local/crashplan/bin/
./CrashPlanEngine stop
./CrashPlanEngine status
./CrashPlanEngine start
./CrashPlanEngine restart

OR

/etc/init.d/crashplan [same options as above]

#Unpacking CrashPlan to install.
#/root/
tar -xvf CrashPlan_4.3.0_Linux.tgz
#(4.3.0 change to package number you are installing)

#Installing and Uninstalling CrashPlan (This will not uninstall your .ui_info or .identity file).
#/root/CrashPlan-install/
./CrashPlan-install/install.sh
./CrashPlan-install/uninstall.sh -i /usr/local/crashplan/

#/usr/local/crashplan/conf/my.service.xml
<serviceHost>YOUR.NAS.IP.ADDRESS</serviceHost>

OR

#To have CrashPlan listen on all network interfaces and thus accepting GUI connections from any computer on your home network.
<serviceHost>0.0.0.0</serviceHost>

#If Watch file system in real time" is not working CrashPlan suggested changes so that it works on a NAS.
#/etc/sysctl.conf
fs.inotify.max_user_watches=1048576

#Increasing Memory Value to CrashPlan Engine.
#Go to CrashPlan on PC and Double Click Home Icon in Upper Right Hand Corner
#Value should be in memory increments of 64, increasing value too high will stop CrashPlan from running. The upper limit on my NAS PRO Business is 3072 and I have 8 GB of Ram installed.
java mx "value"
OR
#Stop CrashPlan
#Edit /usr/local/crashplan/bin/run.conf in SRV_JAVA_OPTS change "-Xmx3072m" to desired value.
#Start CrashPlan

#Configuring CrashPlan Backup set to Exclude all Directories Named "Recycle Bin".
#Located in Settings-Backup-File exclusions:-Configure (Make sure "Regular Expressions" is checked).
./*Recycle Bin.*

#Another way to check if the CrashPlan service is running in your PC.
ps auxww |grep -i CrashPlanService

#Return code should be something like this:
root 19952 80.3 7.4 3623440 611904 ? SNl 08:17 400:32 /usr/local/crashplan/jre/bin/java -Dfile.encoding=UTF-8 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Xms20m -Xmx3072m -Dsun.net.inetaddr.ttl=300 -Dnetworkaddress.cache.ttl=300 -Dsun.net.inetaddr.negative.ttl=0 -Dnetworkaddress.cache.negative.ttl=0 -Dc42.native.md5.enabled=false -classpath /usr/local/crashplan/lib/com.backup42.desktop.jar:/usr/local/crashplan/lang com.backup42.service.CPService
root 23519 0.0 0.0 4104 504 pts/0 S+ 16:35 0:00 grep -i CrashPlanService

I noticed that if you don't want to keep opening putty every time you want to connect to your NAS you can do the following.
I make no guarantee that this will work but it has worked for me on my NAS PRO 6 and if you don't know what you are doing don't do it.

Step 1:
I recommend you make a copy ui.properties of the file before editing them. It should be in C:\Program Files\CrashPlan\conf\
On the PC you are using the crashplan GUI Edit the ui.properties file: Change serviceHost=NAS.IP.ADDRESS and rem out everything else

Step 2:
Stop crashplan by SSH into your NAS and type in

cd /usr/local/crashplan/bin

then type in

./CrashPlanEngine stop

Step 3:
I recommend that you make a copy of the file my.service.xml. SSH into your nas and change to the directory

cd /usr/local/crashplan/conf

and type

cp my.service.xml my.service.xml.bak

On the Nas unit you can either use Win CP (it has a built in editor and a windows gui) or Putty to ssh into your machine and use vi.
Edit my.service.xml located in /usr/local/crashplan/conf. Change <serviceHost>127.0.0.1</serviceHost> to <serviceHost>Your.NAS.IP.ADDRESS</serviceHost>.

Step 4:
Start crashplan by either rebooting or by SSH into your NAS and type in

cd /usr/local/crashplan/bin

then type in

./CrashPlanEngine start

There now if everything was done right when you click on Crashplan on your PC you will no longer need to open putty and establish a tunnel.

it sounds cool, I'll test it when I'm back home and I'll add it to the list if it works, thanks

Hi Sdouek

It works like a charm! Much easier than creating the tunnel - even though that is handy when you want to check the status remotely and only port 22 is being forwarded!

Thanks, I'm amending my guide now.

Edit: do I still need to change the service port to 4200? Will that be useful in case someone needed to open an SSH tunnel from the outside world? Is it still needed for the average user? I could move it to the 'tweaks' section.

Come on, I want feedbacks!

ok.

But if you do not amend the port number then you cannot dial in remotely by SSH, correct? I found it pretty useful when travelling if I need to check the upload status.