NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

sdouek's avatar
sdouek
Guide
Jul 08, 2015

CrashPlan Cheat Sheet and Tweaks

lBelow are Command Codes, Tweaks and info on CrashPlan.

If you need me to add any more or if something changes feel free to let me know and I will adjust it.

#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. (In other words EJREInstaller-0.20-readynas-x86.bin by MinimServer is not needed for this install anymore).
#In /usr/local/crashplan/install.vars the 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 :) )
#If the EJRE addon is already installed on your system DO NOT UNINSTALL IT, it is still needed globally and as per MinimServer.

Uninstalling the Java runtime

To remove the EJRE installation from your ReadyNAS, remove the EJRE Installer add-on. This removes the installed EJRE files, but doesn't remove the original EJRE .tar.gz file from the backup share.



#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.*

#CrashPlan updated to 4.3.0 and now my Windows 7 GUI will not connect.
1) Make sure Windows 7 GUI is 4.3 and make sure it is not running when you are doing the steps below:
2) Copy your .ui_info from your NAS to your desktop:
a) .ui_info on NAS is probably located /var/lib/crashplan (unless you changed it from the default when installing i.e.
What directory do you wish to store backups in? [/usr/local/var/crashplan])
b) .ui_info on your desktop is located C:\ProgramData\CrashPlan. (Rename your old .ui_info to .ui_info.orig)
3) Configure your ui.properies file on you PC appropriately. i.e. service port should be 4200 if you are using ssh to tunnel or service host should be changed to your NAS ip address if you made the proper changes in the my.service.xml file on you NAS.
4) Start up CrashPlan 4.3 on your desktop.

#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

#Installing the CrashPlan app instructions from CrashPlan's Website.
CrashPlan Headless Client Install

ReadyNas Forum - Crashplan for Dummies, aka Step by Step (this is the latest guide so far out of the 18 or so pages in the post).
Crashplan for Dummies, aka Step by Step :)

34 Replies

Replies have been turned off for this discussion
  • Thanks for the cheat sheet, good summary and helped me solve why 4.3.0 wasn't connecting from Windows

    Cheers
  • This forum and it's users has helped me so much I am Glad to give back to the Community.
  • Great cheat sheet. Thanks.

    Perhaps someone more experienced than I can help me troubleshoot this though... Crashplan v3.6.4 was working fine on my ReadyNAS Ultra4+ until recently... I'm not sure if something changed such that we require the latest versions of the clients to work with the CrashPlan service. So, updating to 4.3.0 seemed to work fine after uninstalling 3.6.4, but upon trying to launch 4.3.0 on my ReadyNAS the following is in the engine_error.log:

    /usr/local/crashplan/jre/bin/java: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory


    Any guidance on what to do about that?

    I verified that "jre-7u45-linux-x64.tgz" properly downloaded and unpacked in the java path set on "JAVACOMMON=/usr/local/crashplan/jre/bin/java"

    I am at a loss right now. Thanks.
    • kahunamike's avatar
      kahunamike
      Aspirant

      Did you ever solve the jre issue? I'm getting the same error message after upgrading to 4.3.0

       

      /usr/local/crashplan/jre/bin/java: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory

      • scootle's avatar
        scootle
        Aspirant

        Nope, haven't yet solved this issue.  My post was made right before the ReadyNAS.com forums were migrated, so everything was locked during the transition, so I presume nobody was able to read or reply to my inquiry.

         

        For the time being, I am without a means to run CrashPlan.

         

        Any suggestions are welcome.  Thanks.

    • chriscena's avatar
      chriscena
      Aspirant

      I managed to get Crashplan 4.4.1 up and running on my NAS (ReadyNAS Ultra 4). All I had to do was to swap out the x64 JRE package with the 586 version instead, after completing the usual install. The install.defaults file contains the URL for the correct file, so just download that one:

       

      (I'm doing all of this in ~/crashplan-install/)

       

      wget http://download.code42.com/installs/proserver/jre/jre-7-linux-i586.tgz

       

      then unpack and swap the x64 version with the 586 version:

       

      tar -zxf jre-7-linux-i586.tgz

      mv /usr/local/crashplan/jre/ /usr/local/crashplan/jre-x64

      mv ~/crashplan-install/jre /usr/local/crashplan/jre

       

      then start the Crashplan service. Voila!

       

      Obviously, the installer picks the wrong architecture for the NAS. Hope this helps.

       

      • scootle's avatar
        scootle
        Aspirant

        Yeah, that appears to be the issue... the Crashplan installer script does not pick the correct architecture for the ReadyNAS Ultra4+ it seems.  I guess we should report that to them, but that said, we are shoe-horning the vanilla "Linux" install onto a NAS, which they show as unsupported.

         

        Thanks all.  Hope this helps others in the same boat.

  • TYPO Error:

     

    b) .uni_info on your desktop is located C:\ProgramData\CrashPlan. (Rename your old .uni_info to .uni_info.orig)

     

    .uni_info should read .ui_info

     

    Thank you StepheB for finding it and pointing it out !

    • StephenB's avatar
      StephenB
      Guru - Experienced User

      sdouek wrote:

       

       

      .uni_info should read .ui_info

       

       


      I edited the original.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More