CrashPlan packages for Synology NAS

UPDATE – The instructions and notes on this page apply to all three versions of the package hosted on my repo: CrashPlan, CrashPlan PRO, and CrashPlan PROe.

CrashPlan is a popular online backup solution which supports continuous syncing. With this your NAS can become even more resilient – it could even get stolen or destroyed and you would still have your data. Whilst you can pay a small monthly charge for a storage allocation in the Cloud, one neat feature CrashPlan offers is for individuals to collaboratively backup their important data to each other – for free! You could install CrashPlan on your laptop and have it continuously protecting your documents to your NAS, even whilst away from home.


CrashPlan is a Java application, and one that’s typically difficult to install on a NAS – therefore an obvious candidate for me to simplify into a package, given that I’ve made a few others. I tried and failed a few months ago, getting stuck at compiling the Jtux library for ARM CPUs (the Oracle Java for Embedded doesn’t come with any headers).

I noticed a few CrashPlan setup guides linking to my Java package, and decided to try again based on these: Kenneth Larsen’s blog post, the Vincesoft blog article for installing on ARM processor Iomega NAS units, and this handy PDF document which is a digest of all of them, complete with download links for the additional compiled ARM libraries. I used the PowerPC binaries Christophe had compiled on his blog, so thanks go to him. I wanted make sure the package didn’t require the NAS to be bootstrapped, so I picked out the few generic binaries that were needed (bash, nice and cpio) directly from the Optware repo.

UPDATE – For version 3.2 I also had to identify and then figure out how to compile Tim Macinta’s fast MD5 library, to fix the supplied on ARM systems (CrashPlan only distributes libraries for x86). I’m documenting that process here in case more libs are required in future versions. I identified it from the error message in log/engine_error.log and by running objdump -x I could see that the same Java_com_twmacinta_util_MD5_Transform_1native function mentioned in the error was present in the x86 lib but not in my compiled from W3C Libwww. I took the headers from an install of OpenJDK on a regular Ubuntu desktop. I then used the Linux x86 source from the download bundle on Tim’s website – the closest match – and compiled it directly on the syno using the command line from a comment in another version of that source:
gcc -O3 -shared -I/tmp/jdk_headers/include /tmp/fast-md5/src/lib/arch/linux_x86/MD5.c -o

Aside from the challenges of getting the library dependencies fixed for ARM and QorIQ PowerPC systems, there was also the matter of compliance – Code 42 Software’s EULA prohibits redistribution of their work. I had to make the syno package download CrashPlan for Linux (after the end user agrees their EULA), then I had to write my own script to extract this archive and mimic their installer, since their installer is interactive. It took a lot of slow testing, but I managed it!

CPPROe package info

My most recent package version introduces handling of the automatic updates which Code 42 sometimes publish to the clients. This has proved to be quite a challenge to get working as testing was very laborious. I can confirm that it worked with the update from CrashPlan PRO 3.2 to 3.2.1 , and from CrashPlan 3.2.1 to 3.4.1:




  • This package is for Marvell Kirkwood, Marvell Armada 370/XP, Intel and Freescale QorIQ/PowerQUICC PowerPC CPUs only, so please check which CPU your NAS has. It will work on an unmodified NAS, no hacking or bootstrapping required. It will only work on older PowerQUICC PowerPC models that are running DSM 5.0. It is technically possible to run CrashPlan on older DSM versions, but it requires chroot-ing to a Debian install. Christophe from has recently released packages to automate this.
  • In the User Control Panel in DSM, enable the User Homes service.
  • Install the package directly from Package Center in DSM. In Settings -> Package Sources add my package repository URL which is
  • You will need to install either one of my Java SE Embedded packages first (Java 6 or 7). Read the instructions on that page carefully too.
  • If you previously installed CrashPlan manually using the Synology Wiki, you can find uninstall instructions here.


  • The package downloads the CrashPlan installer directly from Code 42 Software, following acceptance of their EULA. I am complying with their wish that no one redistributes it.
  • CrashPlan is installed in headless mode – backup engine only. This is configured by a desktop client, but operates independently of it.
  • The engine daemon script checks the amount of system RAM and scales the Java heap size appropriately (up to the default maximum of 512MB). This can be overridden in a persistent way if you are backing up very large backup sets by editing /volume1/@appstore/CrashPlan/syno_package.vars. If you’re considering buying a NAS purely to use CrashPlan and intend to back up more than a few hundred GB then I strongly advise buying one of the Intel models which come with 1GB RAM and can be upgraded to 3GB very cheaply. RAM is very limited on the ARM ones. 128MB RAM on the J series means CrashPlan is running with only one fifth of the recommended heap size, so I doubt it’s viable for backing up very much at all. My DS111 has 256MB of RAM and currently backs up around 60GB with no issues. I have found that a 512MB heap was insufficient to back up more than 2TB of files on a Windows server. It kept restarting the backup engine every few minutes until I increased the heap to 1024MB.
  • As with my other syno packages, the daemon user account password is randomized when it is created using the openssl binary. DSM Package Center runs as the root user so my script starts the package using an su command. This means that you can change the password yourself and CrashPlan will still work.
  • The default location for saving friends’ backups is set to /volume1/crashplan/backupArchives (where /volume1 is you primary storage volume) to eliminate the chance of them being destroyed accidentally by uninstalling the package.
  • The first time you run the server you will need to stop it and restart it before you can connect the client. This is because a config file that’s only created on first run needs to be edited by one of my scripts. The engine is then configured to listen on all interfaces on the default port 4243.
  • Once the engine is running, you can manage it by installing CrashPlan on another computer, and editing the file conf/ on that computer so that this line:
    is uncommented (by removing the hash symbol) and set to the IP address of your NAS, e.g.:
    On Windows you can also disable the CrashPlan service if you will only use the client.
  • If you need to manage CrashPlan from a remote location, I suggest you do so using SSH tunnelling as per this support document.
  • The package supports upgrading to future versions while preserving the machine identity, logs, login details, and cache. Upgrades can now take place without requiring a login from the client afterwards.
  • If you remove the package completely and re-install it later, you can re-attach to previous backups. When you log in to the Desktop Client with your existing account after a re-install, you can select “adopt computer” to merge the records, and preserve your existing backups. I haven’t tested whether this also re-attaches links to friends’ CrashPlan computers and backup sets, though the latter does seem possible in the Friends section of the GUI. It’s probably a good idea to test that this survives a package reinstall before you start relying on it. Sometimes, particularly with CrashPlan PRO I think, the adopt option is not offered. In this case you can log into CrashPlan Central and retrieve your computer’s GUID. On the CrashPlan client, double-click on the logo in the top right and you’ll enter a command line mode. You can use the GUID command to change the system’s GUID to the one you just retrieved from your account.
  • The log which is displayed in the package’s Log tab is actually the activity history. If you’re trying to troubleshoot an issue you will need to use an SSH session to inspect the two engine log files which are:
  • When CrashPlan downloads and attempts to run an automatic update, the script will most likely fail and stop the package. This is typically caused by syntax differences with the Synology versions of certain Linux shell commands (like rm, mv, or ps). You will need to wait several minutes in the event of this happening before you take action, because the update script tries to restart CrashPlan 10 times at 10 second intervals. After this, you simply start the package again in Package Center and my scripts will fix the update, then run it. One final package restart is required before you can connect with the CrashPlan Desktop client (remember to update that too).
  • After their backup is seeded some users may wish to schedule the CrashPlan engine using cron so that it only runs at certain times. This is particularly useful on ARM systems because CrashPlan currently prevents hibernation while it is running (unresolved issue, reported to Code 42). To schedule, edit /etc/crontab and add the following entries for starting and stopping CrashPlan:
    55 2 * * * root /var/packages/CrashPlan/scripts/start-stop-status start
    0  4 * * * root /var/packages/CrashPlan/scripts/start-stop-status stop

    This example would configure CrashPlan to run daily between 02:55 and 04:00am. CrashPlan by default will scan the whole backup selection for changes at 3:00am so this is ideal. The simplest way to edit crontab if you’re not really confident with Linux is to install Merty’s Config File Editor package, which requires the official Synology Perl package to be installed too (since DSM 4.2). After editing crontab you will need to restart the cron daemon for the changes to take effect:
    /usr/syno/etc.defaults/rc.d/ stop
    /usr/syno/etc.defaults/rc.d/ start

    It is vitally important that you do not improvise your own startup commands or use a different account because this will most likely break the permissions on the config files, causing additional problems. The package scripts are designed to be run as root, and they will in turn invoke the CrashPlan engine using its own dedicated user account.
  • If you update DSM later, you will need to re-install the Java package or else UTF-8 and locale support will be broken by the update.
  • If you decide to sign up for one of CrashPlan’s paid backup services as a result of my work on this, I would really appreciate it if you could use this affiliate link, or consider donating using the PayPal button on the right.

Package scripts

For information, here are the package scripts so you can see what it’s going to do. You can get more information about how packages work by reading the Synology Package wiki.


#--------CRASHPLAN installer script
#--------package maintained at

[ "${SYNOPKG_PKGNAME}" == "CrashPlan" ] && DOWNLOAD_FILE="CrashPlan_3.7.0_Linux.tgz"
[ "${SYNOPKG_PKGNAME}" == "CrashPlanPRO" ] && DOWNLOAD_FILE="CrashPlanPRO_3.7.0_Linux.tgz"
if [ "${SYNOPKG_PKGNAME}" == "CrashPlanPROe" ]; then
  [ "${WIZARD_VER_370}" == "true" ] && CPPROE_VER="3.7.0"
  [ "${WIZARD_VER_364}" == "true" ] && CPPROE_VER="3.6.4"
  [ "${WIZARD_VER_363}" == "true" ] && CPPROE_VER="3.6.3"
  [ "${WIZARD_VER_3614}" == "true" ] && CPPROE_VER=""
  [ "${WIZARD_VER_353}" == "true" ] && CPPROE_VER="3.5.3"
  [ "${WIZARD_VER_341}" == "true" ] && CPPROE_VER="3.4.1"
  [ "${WIZARD_VER_33}" == "true" ] && CPPROE_VER="3.3"
SYNO_CPU_ARCH="`uname -m`"
[ "${SYNO_CPU_ARCH}" == "x86_64" ] && SYNO_CPU_ARCH="i686"
[ "${SYNO_CPU_ARCH}" == "armv5tel" ] && SYNO_CPU_ARCH="armle"
[ "${SYNO_CPU_ARCH}" == "armv7l" ] && SYNO_CPU_ARCH="armle"
[ "${SYNOPKG_DSM_ARCH}" == "armada375" ] && SYNO_CPU_ARCH="armhf"
[ "${SYNOPKG_DSM_ARCH}" == "comcerto2k" ] && SYNO_CPU_ARCH="armhf"
[ "${SYNOPKG_DSM_ARCH}" == "alpine" ] && SYNO_CPU_ARCH="armhf"
NATIVE_BINS_FILE="`echo ${NATIVE_BINS_URL} | sed -r "s%^.*/(.*)%\1%"`"
TEMP_FOLDER="`find / -maxdepth 2 -path '/volume?/@tmp' | head -n 1`"
#the Manifest folder is where friends' backup data is stored
#we set it outside the app folder so it persists after a package uninstall
MANIFEST_FOLDER="/`echo $TEMP_FOLDER | cut -f2 -d'/'`/crashplan"
UPGRADE_FILES="syno_package.vars conf/my.service.xml conf/service.login conf/service.model"
PUBLIC_FOLDER="`synoshare --get public | sed -r "/Path/!d;s/^.*\[(.*)\].*$/\1/"`"
source /etc/profile

preinst ()
  if [ -z ${JAVA_HOME} ]; then
    echo "Java is not installed or not properly configured. JAVA_HOME is not defined. "
    echo "Download and install the Java Synology package from"
    exit 1

  if [ ! -f ${JAVA_HOME}/bin/java ]; then
    echo "Java is not installed or not properly configured. The Java binary could not be located. "
    echo "Download and install the Java Synology package from"
    exit 1

    WGET_FILENAME="`echo ${WGET_URL} | sed -r "s%^.*/(.*)%\1%"`"
    wget ${WGET_URL}
    if [[ $? != 0 ]]; then
      if [ -d ${PUBLIC_FOLDER} ] && [ -f ${PUBLIC_FOLDER}/${WGET_FILENAME} ]; then
        echo "There was a problem downloading ${WGET_FILENAME} from the official download link, "
        echo "which was \"${WGET_URL}\" "
        echo "Alternatively, you may download this file manually and place it in the 'public' shared folder. "
        exit 1
  exit 0

postinst ()
  #extract CPU-specific additional binaries
  mkdir ${SYNOPKG_PKGDEST}/bin

  #extract main archive
  #extract cpio archive
  cat "${TEMP_FOLDER}/${EXTRACTED_FOLDER}"/${CPI_FILE} | gzip -d -c | ${SYNOPKG_PKGDEST}/bin/cpio -i --no-preserve-owner
  echo "#uncomment to expand Java max heap size beyond prescribed value (will survive upgrades)" > ${SYNOPKG_PKGDEST}/syno_package.vars
  echo "#you probably only want more than the recommended 1024M if you're backing up extremely large volumes of files" >> ${SYNOPKG_PKGDEST}/syno_package.vars
  echo "#USR_MAX_HEAP=1024M" >> ${SYNOPKG_PKGDEST}/syno_package.vars
  echo >> ${SYNOPKG_PKGDEST}/syno_package.vars

  cp ${TEMP_FOLDER}/${EXTRACTED_FOLDER}/scripts/CrashPlanEngine ${OPTDIR}/bin
  cp ${TEMP_FOLDER}/${EXTRACTED_FOLDER}/scripts/run.conf ${OPTDIR}/bin
  mkdir -p ${MANIFEST_FOLDER}/backupArchives    
  #save install variables which Crashplan expects its own installer script to create
  echo BINSDIR=/bin >> ${VARS_FILE}
  echo MANIFESTDIR=${MANIFEST_FOLDER}/backupArchives >> ${VARS_FILE}
  #leave these ones out which should help upgrades from Code42 to work (based on examining an upgrade script)
  #echo INITDIR=/etc/init.d >> ${VARS_FILE}
  #echo RUNLVLDIR=/usr/syno/etc/rc.d >> ${VARS_FILE}
  echo INSTALLDATE=`date +%Y%m%d` >> ${VARS_FILE}
  echo JAVACOMMON=\${JAVA_HOME}/bin/java >> ${VARS_FILE}
  cat ${TEMP_FOLDER}/${EXTRACTED_FOLDER}/install.defaults >> ${VARS_FILE}
  #remove temp files
  #add firewall config
  /usr/syno/bin/servicetool --install-configure-file --package /var/packages/${SYNOPKG_PKGNAME}/scripts/${SYNOPKG_PKGNAME}.sc > /dev/null
  #amend CrashPlanPROe client version
  [ "${SYNOPKG_PKGNAME}" == "CrashPlanPROe" ] && sed -i -r "s/^version=\".*(-.*$)/version=\"${CPPROE_VER}\1/" /var/packages/${SYNOPKG_PKGNAME}/INFO

  exit 0

preuninst ()
  #make sure engine is stopped
  /var/packages/${SYNOPKG_PKGNAME}/scripts/start-stop-status stop
  exit 0

postuninst ()
  if [ -f ${SYNOPKG_PKGDEST}/syno_package.vars ]; then
    source ${SYNOPKG_PKGDEST}/syno_package.vars

  if [ "${LIBFFI_SYMLINK}" == "YES" ]; then
    sed -i "/^LIBFFI_SYMLINK/d" ${SYNOPKG_PKGDEST}/syno_package.vars
  [ -e ${OPTDIR}/lib/* ] && rm ${OPTDIR}/lib/*
  #delete symlinks that no longer resolve
  if [ ! -e /lib/ ]; then
    [ -L /lib/ ] && rm /lib/
  if [ ! -e /lib/ ]; then
    [ -L /lib/ ] && rm /lib/
    #repair symlink on DSM 5.0 now that it's included by default
    ln -s /lib/
  #remove firewall config
  if [ "${SYNOPKG_PKG_STATUS}" == "UNINSTALL" ]; then
    /usr/syno/bin/servicetool --remove-configure-file --package ${SYNOPKG_PKGNAME}.sc > /dev/null

  #remove legacy daemon user and homedir
  DAEMON_USER="`echo ${SYNOPKG_PKGNAME} | awk {'print tolower($_)'}`"
  synouser --del ${DAEMON_USER}
  [ -e /var/services/homes/${DAEMON_USER} ] && rm -r /var/services/homes/${DAEMON_USER}
 exit 0

preupgrade ()
  #make sure engine is stopped
  /var/packages/${SYNOPKG_PKGNAME}/scripts/start-stop-status stop

  #if identity from legacy package version exists migrate it
  DAEMON_USER="`echo ${SYNOPKG_PKGNAME} | awk {'print tolower($_)'}`"
  if [ -d ${DAEMON_HOME}/.crashplan ]; then
    mkdir -p ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig/conf
    mkdir -p /var/lib/crashplan
    mv ${DAEMON_HOME}/.crashplan/.identity /var/lib/crashplan/
    chown -R root:root /var/lib/crashplan/

  #if identity exists back up config
  if [ -f /var/lib/crashplan/.identity ]; then
    mkdir -p ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig/conf

  #if config data exists back it up  
  if [ "${CONFIG_MIGRATION}" == "true" ]; then
      if [ -f ${OPTDIR}/${FILE_TO_MIGRATE} ]; then
      if [ -d ${OPTDIR}/${FOLDER_TO_MIGRATE} ]; then

  exit 0

postupgrade ()
  #use the migrated identity and config data from the previous version
  if [ -f ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig/conf/my.service.xml ]; then
      if [ -f ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig/${FILE_TO_MIGRATE} ]; then
    if [ -d ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig/${FOLDER_TO_MIGRATE} ]; then
    rmdir ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig/conf
    rmdir ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig
    #make CrashPlan log entry
    TIMESTAMP="`date "+%D %I:%M%p"`"
    echo "I ${TIMESTAMP} Synology Package Center updated ${SYNOPKG_PKGNAME} to version ${SYNOPKG_PKGVER}" >> ${LOG_FILE}

    #fix permissions on migrated settings and manifest from legacy package versions which used a daemon user account
    chown -R root:root ${SYNOPKG_PKGDEST}
    if [ -f ${SYNOPKG_PKGDEST}/conf/my.service.xml ]; then
      MANIFEST_FOLDER=`cat ${SYNOPKG_PKGDEST}/conf/my.service.xml | grep "<manifestPath>" | cut -f2 -d'>' | cut -f1 -d'<'`
      chown -R root:root ${MANIFEST_FOLDER}

    #tidy up some legacy settings
    sed -i "/^CRON_SYNOPKG_PKGNAME/d" ${SYNOPKG_PKGDEST}/syno_package.vars
    sed -i "/^CRON_SYNOPKG_PKGDEST/d" ${SYNOPKG_PKGDEST}/syno_package.vars
  exit 0


#--------CRASHPLAN start-stop-status script
#--------package maintained at

TEMP_FOLDER="`find / -maxdepth 2 -path '/volume?/@tmp' | head -n 1`"
MANIFEST_FOLDER="/`echo $TEMP_FOLDER | cut -f2 -d'/'`/crashplan" 
PKG_FOLDER="`dirname $0 | cut -f1-4 -d'/'`"
DNAME="`dirname $0 | cut -f4 -d'/'`"
JAVA_MIN_HEAP=`grep "^${CFG_PARAM}=" "${OPTDIR}/bin/${ENGINE_CFG}" | sed -r "s/^.*-Xms([0-9]+)[Mm] .*$/\1/"` 
SYNO_CPU_ARCH="`uname -m`"
TIMESTAMP="`date "+%D %I:%M%p"`"
source ${OPTDIR}/install.vars
source /etc/profile
source /root/.profile

start_daemon ()
  #check persistent variables from syno_package.vars
  if [ -f ${OPTDIR}/syno_package.vars ]; then
    source ${OPTDIR}/syno_package.vars
  USR_MAX_HEAP=`echo $USR_MAX_HEAP | sed -e "s/[mM]//"`

  #do we need to restore the identity file - has a DSM upgrade scrubbed /var/lib/crashplan?
  if [ ! -e /var/lib/crashplan ]; then
    mkdir /var/lib/crashplan
    [ -e ${OPTDIR}/conf/var-backup/.identity ] && cp ${OPTDIR}/conf/var-backup/.identity /var/lib/crashplan/

  #fix up some of the binary paths and fix some command syntax for busybox 
  #moved this to from because Code42 push updates and these
  #new scripts will need this treatment too
  find ${OPTDIR}/ -name "*.sh" | while IFS="" read -r FILE_TO_EDIT; do
    if [ -e ${FILE_TO_EDIT} ]; then
      #this list of substitutions will probably need expanding as new CrashPlan updates are released
      sed -i "s%^#!/bin/bash%#!$/bin/sh%" "${FILE_TO_EDIT}"
      sed -i -r "s%(^\s*)(/bin/ps|ps) [^w][^\|]*\|%\1/bin/ps w \|%" "${FILE_TO_EDIT}"
      sed -i -r "s%\`ps [^w][^\|]*\|%\`ps w \|%" "${FILE_TO_EDIT}"
      sed -i -r "s%^ps [^w][^\|]*\|%ps w \|%" "${FILE_TO_EDIT}"
      sed -i "s/rm -fv/rm -f/" "${FILE_TO_EDIT}"
      sed -i "s/mv -fv/mv -f/" "${FILE_TO_EDIT}"

  #use this daemon init script rather than the unreliable Code42 stock one which greps the ps output
  sed -i "s%^ENGINE_SCRIPT=.*$%ENGINE_SCRIPT=$0%" ${OPTDIR}/bin/

  #any downloaded upgrade script will usually have failed until the above changes are made so we need to
  #find it and start it, if it exists
  UPGRADE_SCRIPT=`find ${OPTDIR}/upgrade -name ""`
  if [ -n "${UPGRADE_SCRIPT}" ]; then
    rm ${OPTDIR}/*.pid
    #make CrashPlan log entry
    echo "I ${TIMESTAMP} Synology repairing upgrade in ${SCRIPT_HOME}" >> ${DLOG}

    mv ${SCRIPT_HOME}/upgrade.log ${SCRIPT_HOME}/upgrade.log.old
    cd ${SCRIPT_HOME}
    exit 0

  #updates may also overwrite our native binaries
  [ -e ${OPTDIR}/bin/ ] && cp -f ${SYNOPKG_PKGDEST}/bin/ ${OPTDIR}/lib
  [ -e ${OPTDIR}/bin/ ] && cp -f ${OPTDIR}/bin/ ${OPTDIR}/
  cp -f ${OPTDIR}/bin/jna-3.2.5.jar ${OPTDIR}/lib

  #create or repair symlink if a DSM upgrade has removed it - PowerPC only
  if [ -e ${OPTDIR}/lib/ ]; then
    if [ ! -e /lib/ ]; then
      #if it doesn't exist, but is still a link then it's a broken link and should be deleted first
      [ -L /lib/ ] && rm /lib/
      ln -s ${OPTDIR}/lib/ /lib/

  #set appropriate Java max heap size
  RAM=$((`free | grep Mem: | sed -e "s/^ *Mem: *\([0-9]*\).*$/\1/"`/1024))
  if [ $RAM -le 128 ]; then
  elif [ $RAM -le 256 ]; then
  elif [ $RAM -le 512 ]; then
  elif [ $RAM -le 1024 ]; then
  elif [ $RAM -gt 1024 ]; then
  if [ $USR_MAX_HEAP -gt $JAVA_MAX_HEAP ]; then
  if [ $JAVA_MAX_HEAP -lt $JAVA_MIN_HEAP ]; then
    #can't have a max heap lower than min heap (ARM low RAM systems)
  sed -i -r "s/(^${CFG_PARAM}=.*) -Xmx[0-9]+[mM] (.*$)/\1 -Xmx${JAVA_MAX_HEAP}m \2/" "${OPTDIR}/bin/${ENGINE_CFG}"
  #disable the use of the x86-optimized external Fast MD5 library if running on ARM and PPC CPUs
  #seems to be the default behaviour now but that may change again
  [ "${SYNO_CPU_ARCH}" == "x86_64" ] && SYNO_CPU_ARCH="i686"
  if [ "${SYNO_CPU_ARCH}" != "i686" ]; then
    grep "^${CFG_PARAM}=.*c42\.native\.md5\.enabled" "${OPTDIR}/bin/${ENGINE_CFG}" > /dev/null \
     || sed -i -r "s/(^${CFG_PARAM}=\".*)\"$/\1 -Dc42.native.md5.enabled=false\"/" "${OPTDIR}/bin/${ENGINE_CFG}"

  #move the Java temp directory from the default of /tmp
  grep "^${CFG_PARAM}=.*Djava\.io\.tmpdir" "${OPTDIR}/bin/${ENGINE_CFG}" > /dev/null \
   || sed -i -r "s%(^${CFG_PARAM}=\".*)\"$%\1${TEMP_FOLDER}\"%" "${OPTDIR}/bin/${ENGINE_CFG}"

  #now edit the XML config file, which only exists after first run
  if [ -f ${OPTDIR}/conf/my.service.xml ]; then

    #allow direct connections from CrashPlan Desktop client on remote systems
    #you must edit the value of serviceHost in conf/ on the client you connect with
    #users report that this value is sometimes reset so now it's set every service startup 
    sed -i "s/<serviceHost>127\.0\.0\.1<\/serviceHost>/<serviceHost>0\.0\.0\.0<\/serviceHost>/" "${OPTDIR}/conf/my.service.xml"
    #this change is made only once in case you want to customize the friends' backup location
    if [ "${MANIFEST_PATH_SET}" != "True" ]; then

      #keep friends' backup data outside the application folder to make accidental deletion less likely 
      sed -i "s%<manifestPath>.*</manifestPath>%<manifestPath>${MANIFEST_FOLDER}/backupArchives/</manifestPath>%" "${OPTDIR}/conf/my.service.xml"
      echo "MANIFEST_PATH_SET=True" >> ${OPTDIR}/syno_package.vars

    #since CrashPlan version 3.5.3 the value javaMemoryHeapMax also needs setting to match that used in bin/run.conf
    sed -i -r "s%(<javaMemoryHeapMax>)[0-9]+[mM](</javaMemoryHeapMax>)%\1${JAVA_MAX_HEAP}m\2%" "${OPTDIR}/conf/my.service.xml"
    echo "Check the package log to ensure the package has started successfully, then stop and restart the package to allow desktop client connections." > "${SYNOPKG_TEMP_LOGFILE}"

  #increase the system-wide maximum number of open files from Synology default of 24466
  echo "65536" > /proc/sys/fs/file-max

  #raise the maximum open file count from the Synology default of 1024 - thanks Casper K. for figuring this out
  ulimit -n 65536

  source ${OPTDIR}/bin/run.conf
  source ${OPTDIR}/install.vars
  cd ${OPTDIR}
  $JAVACOMMON $SRV_JAVA_OPTS -classpath $FULL_CP com.backup42.service.CPService > ${OPTDIR}/log/engine_output.log 2> ${OPTDIR}/log/engine_error.log &
  if [ $! -gt 0 ]; then
    echo $! > $PID_FILE
    renice 19 $!
    if [ -z "${SYNOPKG_PKGDEST}" ]; then
      #script was manually invoked, need this to show status change in Package Center      
      [ -e ${PKG_FOLDER}/enabled ] || touch ${PKG_FOLDER}/enabled
    echo "${DNAME} failed to start, check ${OPTDIR}/log/engine_error.log" > "${SYNOPKG_TEMP_LOGFILE}"
    echo "${DNAME} failed to start, check ${OPTDIR}/log/engine_error.log" >&2
    exit 1

stop_daemon ()
  echo "I ${TIMESTAMP} Stopping ${DNAME}" >> ${DLOG}
  kill `cat ${PID_FILE}`
  wait_for_status 1 20 || kill -9 `cat ${PID_FILE}`
  rm -f ${PID_FILE}
  if [ -z ${SYNOPKG_PKGDEST} ]; then
    #script was manually invoked, need this to show status change in Package Center
    [ -e ${PKG_FOLDER}/enabled ] && rm ${PKG_FOLDER}/enabled
  #backup identity file in case DSM upgrade removes it
  [ -e ${OPTDIR}/conf/var-backup ] || mkdir ${OPTDIR}/conf/var-backup 
  cp /var/lib/crashplan/.identity ${OPTDIR}/conf/var-backup/

daemon_status ()
  if [ -f ${PID_FILE} ] && kill -0 `cat ${PID_FILE}` > /dev/null 2>&1; then
  rm -f ${PID_FILE}
  return 1

wait_for_status ()
  while [ ${counter} -gt 0 ]; do
    [ $? -eq $1 ] && return
    let counter=counter-1
    sleep 1
  return 1

case $1 in
    if daemon_status; then
      echo ${DNAME} is already running with PID `cat ${PID_FILE}`
      exit 0
      echo Starting ${DNAME} ...
      exit $?

    if daemon_status; then
      echo Stopping ${DNAME} ...
      exit $?
      echo ${DNAME} is not running
      exit 0

    exit $?

    if daemon_status; then
      echo ${DNAME} is running with PID `cat ${PID_FILE}`
      exit 0
      echo ${DNAME} is not running
      exit 1

    echo "${DLOG}"
    exit 0

    echo "Usage: $0 {start|stop|status|restart}" >&2
    exit 1


install_uifile & upgrade_uifile

    "step_title": "Client Version Selection",
    "items": [
        "type": "singleselect",
        "desc": "Please select the CrashPlanPROe client version that is appropriate for your backup destination server:",
        "subitems": [
            "key": "WIZARD_VER_370",
            "desc": "3.7.0",
            "defaultValue": true
            "key": "WIZARD_VER_364",
            "desc": "3.6.4",
            "defaultValue": false
            "key": "WIZARD_VER_363",
            "desc": "3.6.3",
            "defaultValue": false
            "key": "WIZARD_VER_3614",
            "desc": "",
            "defaultValue": false
            "key": "WIZARD_VER_353",
            "desc": "3.5.3",
            "defaultValue": false
            "key": "WIZARD_VER_341",
            "desc": "3.4.1",
            "defaultValue": false
            "key": "WIZARD_VER_33",
            "desc": "3.3",
            "defaultValue": false


  • 0031 Added TCP 4242 to the firewall services (computer to computer connections)
  • 0030 Fixed show-stopping issue with version 0029 for systems with more than one volume
  • 0029 Updated to CrashPlan version 3.7.0, improved detection of temp folder (prevent use of /var/@tmp), added support for Annapurna Alpine AL514 CPU (armhf) in DS2015xs, added support for Marvell Armada 375 CPU (armhf) in DS215j, abandoned practical efforts to try to support Code42’s upgrade scripts, abandoned inotify support (realtime backup) on PowerPC after many failed attempts with self-built and pre-built jtux and jna libraries, back-merged older libffi support for old PowerPC binaries after it was removed in 0028 re-write
  • 0028 Substantial re-write:
    Updated to CrashPlan version 3.6.4
    DSM 5.0 or newer is now required taken from Debian JNA 3.2.7 package with dependency on newer (included in DSM 5.0)
    jna-3.2.5.jar emptied of irrelevant CPU architecture libs to reduce size
    Increased default max heap size from 512MB to 1GB on systems with more than 1GB RAM
    Intel CPUs no longer need the awkward glibc version-faking shim to enable inotify support (for real-time backup)
    Switched to using root account – no more adding account permissions for backup, package upgrades will no longer break this
    DSM Firewall application definition added
    Tested with DSM Task Scheduler to allow backups between certain times of day only, saving RAM when not in use
    Daemon init script now uses a proper PID file instead of Code42’s unreliable method of using grep on the output of ps
    Daemon init script can be run from the command line
    Removal of bash binary dependency now Code42’s CrashPlanEngine script is no longer used
    Removal of nice binary dependency, using BusyBox’s renice
    Unified ARMv5 and ARMv7 external binary package (armle)
    Added support for Mindspeed Comcerto 2000 CPU (comcerto2k – armhf) in DS414j
    Added support for Intel Atom C2538 (avoton) CPU in DS415+
    Added support to choose which version of CrashPlan PROe client to download, since some servers may still require legacy versions
    Switched to .tar.xz for native binaries to reduce hosting overhead
  • 0027 Fixed open file handle limit for very large backup sets (ulimit fix)
  • 0026 Updated all CrashPlan clients to version 3.6.3, improved handling of Java temp files
  • 0025 glibc version shim no longer used on Intel Synology models running DSM 5.0
  • 0024 Updated to CrashPlan PROe and added support for PowerPC 2010 Synology models running DSM 5.0
  • 0023 Added support for Intel Atom Evansport and Armada XP CPUs in new DSx14 products
  • 0022 Updated all CrashPlan client versions to 3.5.3, compiled native binary dependencies to add support for Armada 370 CPU (DS213j), now updates the new javaMemoryHeapMax value in my.service.xml to the value defined in syno_package.vars
  • 0021 Updated CrashPlan to version 3.5.2
  • 0020 Fixes for DSM 4.2
  • 018 Updated CrashPlan PRO to version 3.4.1
  • 017 Updated CrashPlan and CrashPlan PROe to version 3.4.1, and improved in-app update handling
  • 016 Added support for Freescale QorIQ CPUs in some x13 series Synology models, and installer script now downloads native binaries separately to reduce repo hosting bandwidth, PowerQUICC PowerPC processors in previous Synology generations with older glibc versions are not supported
  • 015 Added support for easy scheduling via cron – see updated Notes section
  • 014 DSM 4.1 user profile permissions fix
  • 013 implemented update handling for future automatic updates from Code 42, and incremented CrashPlanPRO client to release version 3.2.1
  • 012 incremented CrashPlanPROe client to release version 3.3
  • 011 minor fix to allow a wildcard on the cpio archive name inside the main installer package (to fix CP PROe client since Code 42 Software had amended the cpio file version to
  • 010 minor bug fix relating to daemon home directory path
  • 009 rewrote the scripts to be even easier to maintain and unified as much as possible with my imminent CrashPlan PROe server package, fixed a timezone bug (tightened regex matching), moved the script-amending logic from to with it now applying to all .sh scripts each startup so perhaps updates from Code42 might work in future, if wget fails to fetch the installer from Code42 the installer will look for the file in the public shared folder
  • 008 merged the 14 package scripts each (7 for ARM, 7 for Intel) for CP, CP PRO, & CP PROe – 42 scripts in total – down to just two! ARM & Intel are now supported by the same package, Intel synos now have working inotify support (Real-Time Backup) thanks to rwojo’s shim to pass the glibc version check, upgrade process now retains login, cache and log data (no more re-scanning), users can specify a persistent larger max heap size for very large backup sets
  • 007 fixed a bug that broke CrashPlan if the Java folder moved (if you changed version)
  • 006 installation now fails without User Home service enabled, fixed Daylight Saving Time support, automated replacing the ARM symlink which is destroyed by DSM upgrades, stopped assuming the primary storage volume is /volume1, reset ownership on /var/lib/crashplan and the Friends backup location after installs and upgrades
  • 005 added warning to restart daemon after 1st run, and improved upgrade process again
  • 004 updated to CrashPlan 3.2.1 and improved package upgrade process, forced binding to each startup
  • 003 fixed ownership of /volume1/crashplan folder
  • 002 updated to CrashPlan 3.2
  • 001 intial public release
About these ads

3,392 thoughts on “CrashPlan packages for Synology NAS

  1. Chris

    I did this:
    “I did some more digging and managed to actually resolve my issue and am once again successfully backing up to the cloud. I changed the file /volume1/@appstore/CrashPlan/syno_package.vars by editing in vi to remove the # in front of the command: #USR_MAX_HEAP=XXXX and making XXXX=1536 After editing, I re-started the package”

    and this:
    “Suggested values for devices with 1GB RAM and 2GB swap, not running any other memory intensive applications: modify the first line in /opt/crashplan/bin/run.conf
    SRV_JAVA_OPTS=”-Dfile.encoding=UTF-8 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Xms20m -Xmx512m …
    SRV_JAVA_OPTS=”-Dfile.encoding=UTF-8 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Xms128m -Xmx1536m …”

    And now I am back up and running again.

  2. stncttr908

    I’m running CrashPlan on my DS415Play. Everything was working fine with 3.7.0 for several days, I got about 220GB of my 400GB initial backup done. However, since then I am having a ton of issues with the CrashPlan process “freezing” for several minutes at a time where there is no upload activity (Synology shows upstream has stopped, and the CP client will lock up and show no activity). During this time the kswapd0 process on the NAS goes nuts and uses between 20-25% CPU, and I can see the physical RAM usage of the CP Java process fall considerably. Then, the RAM usage will spike back up and everything is fine for another few minutes, then it all happens over again. Has anyone seen this before and know how to fix it? I tried changing my USR_MAX_HEAP and SRV_JAVA_OPTS options as others have, but this has not fixed the issue. Is it simply a matter of my DS415Play hitting a RAM wall? This backup set is around 100k files (my MP3 and photo collections) but for some reason CP reports nearly twice as many files when it scans. I am not sure if that’s related to the problem, but I felt it was worth noting.

    I’m currently rebuilding my file list to see if that improves things. I’ve also stopped all other packages to give CP as much RAM as possible during this initial backup. If I can get it running reasonably well I’ll just strt and stop the process on a schedule going forward to “catch up” overnight.

  3. roelteeuwen

    Hi all, issue:

    – Crashplan stopped working
    – Synology gave a message that I needed to upgrade crashplan. When I tried to run the update (3.7.0-0030) is gives directly the error message: “Could not install crashplan”.
    – I tried to remove the crashplan package completely and then do a fresh install. Same problem/error. Tried also removal by using these commands:
    – Tried to reinstall Java SE embedded by using community packages (I tried 6, 7 and 8) I also get directly the error message: “Could not install Java Embedded SE xx”. I did a manual reinstall of Java using the Java Manager (version: jdk-7u75-linux-i586.gz). That worked.
    – When I try a manual package install `(crashplan3.7.0-merged-0030.spk) I directly get the error message “This package doesn’t contain a digital signature”.
    Could this be the issue?

    I hope anyone can help…

    Best regards,

  4. Matt Kopf

    When updating to the lastest release (0030) the Eula pops up, but when I have it install it simply says install failed.

    I updated Java to what I believe is the latest build: 1.7.0_76
    Installed the latest DSM and rebooted.

    Still fails to install
    I am running a 1812+ Synology.

    I’m not a linux guru so any help finding and fixing the problem would be great!


    1. Matt Kopf

      I don’t know why, but I tried again to install the package and today it worked just fine and appears to have backed up all my needed data. I just had to wait a month?

  5. Bjorn

    Just a FYI, I have 5.0.4528 running, and by just doing a update of the Crashplan app after it had stoped (which it did when it tried to auto-update), everything worked as it should, after I clicked start it started up as normal, and my windows client connected to it as it should straight away. Good job Patters!

  6. ptolemyiv

    Firstly patters, just wanted to thank you for the fantastic efforts on this… you single-handedly led me to spend a decent amount of money on a 3 year family subscription! Have you tried getting in contact directly with crash plan for them to more openly and proactively support your efforts?

    Anyhow I have now upgraded to 3.7.0 as well (after getting caught for a while by the trusted publisher settings issue – not the most helpful error message from the synology!) but am experiencing weird behaviour – basically the backup log shows crash plan frequently stopping, restarting and trying to backup the same set of files..

    It spent the best part of today doing this in repeat for 2 files of 1.5MB size and then eventually moved onto the below… have tried stopping and restarting the service and the mac client to no avail.. thanks for any advice!

    Example of log:

    I 01/26/15 01:27AM CrashPlan started, version 3.7.0, GUID 654070501410865558
    I 01/26/15 01:27AM Backup scheduled to always run
    I 01/26/15 01:27AM [Default] Scanning for files to back up
    I 01/26/15 01:28AM [Default] Starting backup to CrashPlan Central: 49 files (127.80MB) to back up
    I 01/26/15 01:30AM Stopping CrashPlan
    I 01/26/15 01:30AM [Default] Scanning for files stopped
    I 01/26/15 01:30AM CrashPlan started, version 3.7.0, GUID 654070501410865558
    I 01/26/15 01:30AM Backup scheduled to always run
    I 01/26/15 01:30AM [Default] Scanning for files to back up
    I 01/26/15 01:30AM [Default] Starting backup to CrashPlan Central: 49 files (127.80MB) to back up

    1. frankwes

      I’ve got the same problem… CP keeps starting and stopping over an d over again. I’ve read that is has something to do with use of memory, but how can I change the use of memory on my NAS? (Synology DS214+)

  7. Dave Simmons

    Thank you for releasing 0030. I was running 0028 just fine, but the auto upgrade to0029 stopped the service from running. Now with 0030, the service on the Synology DS415+ running DSM 5.1 seems to work fine, but my 3.7.0 crash plan GUI client that was formerly running fine on my iMac now crashes after about one minute or so. It appears to be taking to the sinology and moving a file when about one minute into this process it crashes.
    I tested by running another crash plan client on another iMac and got the same results.
    I think there may be an issue with 0030. Any suggestions on how to debug?
    Dave S

  8. belnas


    looks like crashplan is stopping after each upload:

    any suggestions?

    DSM 5 latest
    3.7.0 in both client and nas
    synology’s java manager with 7.55u

    1. patters Post author

      Can you try stopping CrashPlan, logging in via SSH and doing the following:
      cd /volume1/@appstore/CrashPlan/bin
      mv jna-3.2.5.jar jna-3.2.5.jar.bak

      Then start it back up. Any better?

      1. Scott

        I am experiencing the same thing as belnas, and followed your suggestion. Now it is scanning files, but won’t finish. It keeps restarting the scan. I am on a Mac, and the crash plan client keeps closing too.

      2. belnas

        @Scott, 512M is certainly a limitation,
        but my setup was working flawlessly before the 3.7.0 upgrade…
        …backing up >2Tb in 5 backup sets of <100k files each, and uploading at 5m/s

        so, I'm totally lost now.
        I don't know what else to try.

  9. jolimp

    hi, from 2 days my nas crash plan server cannot acces cloud crash plan.
    I have done the “ra, restart” thing, uninstall + re install it. No change
    Telnet to the crash plan cloud from the server answer Ok

    Anyone got this, or have an idea about the issue ?

  10. Chermette

    Ok, I got it back up&running. As stated several times, I increased the heap size and the allocated space in RAM. But, this wasn’t enough, and I also had to decrease the number of files to be backed up.
    Plus, from the look of the past few days’ comments, it looks like it happened for lots of different people. Which means that Tuesday’s update uses more RAM than before, for some reasons.
    Patters, can you please have a look at it? Do you want some log files?

    Best regards

      1. Chermette

        Thanks for your answer. I understand what you mean, and I really appreciate the work that you’ve done.
        But it looks to me like the issue that’s happening has started occurring with your latest update, not since Code42’s. Anyway, I understand your fair point.

        Best regards

      2. ptolemyiv

        As Chermette mentioned when I manually had modified the install to work 3.7.0 all was fine, it’s only since I did your official update? can someone point me to the heap size and ram modifications to make?

        I have the DS414 with 1gb ram so would have thought I would be okay…

        Extremely frustrating since I’ve gone and recently bought the 3 year family subscription to crash plan!

        Anyone else with the DS414 or a device with 1gb ram having it working fine on the latest version?

  11. Gio

    I cannot connect the Crashplan on synology using the Windows desktop application. Both are latest version. Worked very well before the update. Did the same (changing the ip adress in the But the desktop apllication cannot connect to the backup engine…

  12. Rob

    The new package works perfectly on my DS214+ (ARM based). However, I tried installing it on a DS412+ (Intel based) and it doesn’t upgrade nor install. Even after complete removal of the package, I still get a notification “failed to install Crashplan” in the Package Manager. Any ideas?

  13. Sandro

    I’ve tried installing CrashPlan PROe server version 3.5.5-0020 on my Synology 1512+, running DSM 5.1-5022

    The package fails to install with the following error “There was a problem downloading crashplan-native-i686.tgz from the official link, which was Alternatively, you may download this file manually and place it in the ‘public’ shared folder.

    When I look at the web address there is a file ending .tar.xy and no file ending .tgz.
    I tried downloading this file, extracting it and the compressing it back to crashplan-native-i686.tgz. Then placing it in the public folder.

    Crashplan then appears to install correctly, but I am unable to start the package.
    I have been trying for a couple of days to work out how to fix this problem, but with no success. Any help would be much appreciated.

  14. Michael


    thanks for your great instructions, but I still can’t get it to work.

    I try installing it on a DS215j and the installation works fine. But the status is “stopped” and when I click on “start” it falls back to “stopped”.

    When I open the log, it shows a blank log file with nothing in it – any ideas?


      1. Martin Ziel

        FYI, I checked via SSH and noticed the following problems:
        The CrashplanEngine script refers to /bin/bash which does not exist (though I don’t know if that script is even used)

        The other problem is that /var/lib/crashplan is completely empty.

        I hope this helps you boil down the problem.

      2. BenniB


        I’m also running a new Synology DS215j. Do you have any clue, why it is not working ? Maybe I could help troubleshooting. (I’m new to Synology DSM, but I know other embedded linux distros)

      3. Adam

        Hi all,

        I’ve managed to get CrashPlan working on a DS215J. The issue is with the script. It would seem the DS215J needs the armle binaries not the armhf ones.

        I downloaded the package and edited the script changing :

        [ “${SYNOPKG_DSM_ARCH}” == “armada375″ ] && SYNO_CPU_ARCH=”armhf”


        [ “${SYNOPKG_DSM_ARCH}” == “armada375″ ] && SYNO_CPU_ARCH=”armle”

        Re-TAR the package and the perform a manual install.

        Hopefully @patters can alter the package for all to use.

        Thanks for your great work.

      4. patters Post author

        I fixed this earlier tonight using this same method having been given access to a system to test. Only now am I finally going back over my blog comments to see that you had already provided the solution!

        Code 42’s installer is compacted with cpio which is needs a binary utility of the same name to unpack it. That was failing, because the version of cpio for ARM with hard float (armhf – which works on the DS414j) was expecting the system’s main GNU C library to be at least at version 2.17. However, the version of libc used to build the DS215j is only version 2.13.

        I tried to find various different armhf builds of cpio from inside Debian and Ubuntu packages, but none of them would work. They all crashed.

        In the end I got it working by making the DS215j use the armle (regular ARM) binaries. This works nicely, and I can confirm that realtime backup also works – so CrashPlan senses changes to the filesystem in realtime and schedules those changes to be synchronized in the next 15min backup.

      5. fss

        I’m still not able to get it to work on a new DS215j. It doesn’t give any errors during installation, but it stays in “Stopped” even when I click “Run”. Any ideas on this one? Would love to get it to work, otherwise will have to find another solution.

      6. Michael Vaahsen (@vaahsen)


        I know that there are tons of other important things to do and I don’t want to push on that, I just want to ask, if you will try to fix that issue or not. I need to decide if I change my backup strategy.

        Thanks a lot for your feedback and for your investment. You should present your donate button a bit larger, its hard to find ;o)

        If you need some log files from DS215j or if I can help somehow else, please let me know!


      7. kbn

        I am the proud owner of a new 215j and long time Crashplan user. If there is anything I can do to help get it working on the 215j’s please let me know. While not the strongest Linux admin around I do have a few years under my belt.

  15. joelgerlach

    Question: Does the CPU settings in the crashplan Pro client app have any effect on how it runs on the server? I currently have the settings to run at up to 80% of CPU on user idle or present, but Crashplan still only chugs along at 35-40%. I’m not complaining, as I’ve gotten about 8mbps upload pretty consistently; but since the server isn’t doing much else I thought I’d bump it up a bit. But I see it’s not really having an effect on anything. Is this feature supported? If not, no worries, I’ll just let it run. Thanks!

  16. ptolemyiv

    Can anyone point to the memory heap changes etc that I can try out on my ds414 in order to see if this can get crash plan working again? I really don’t understand why this 3.7.0 update (the patters one rather than the workaround which didn’t cause the problem) has completely stopped the package from working.. very frustrating having bought a 3 year license!

  17. martijnkrop

    Hmmmm…. I am running version 3.7.0-0030 on my DS713+ and I notice the same behavior as some other people here. The backup starts the scan and after a few minutes the Crashplan service stops on the NAS and restarts and the process starts all over again.

    1. Steven

      Same behavior as all the others up here. Running 3.7.0-0030 on my DS1511. The backup starts the scan and after a few minutes the Crashplan service stops scanning. I did notice that the number of files it reports while scanning doesn’t seem to add up to the real numbers. It is much larger than reality, like 3 or 4 times larger. I wonder if it’s related. Everything worked well for many months before the update, nothing else changed except the update.

      1. vanardenne

        Same behaviour here as stated above. Running 3.7.0-0030 on DS411 with DSM 5.1-5022 Update 1

      2. patters Post author

        Are you able to grant me SSH access to your NAS? One way to settle this would be to use the exact same binaries that were in my 3.6.4 package (for Jnotify in particular). If the problems persist then the change can only have been introduced by Code 42.

      3. patters Post author

        It was aimed at Steven, but you can help if you’re willing to grant me access and if you have that same issue. Which model of NAS?

      4. patters Post author

        I would rather focus on Intel for now, because I know that my own ARM system is ok. In fact my own Intel system is fine. But I want to remotely check out an Intel CrashPlan Syno with a large backup set.

        I would expect that there’s some kind of additional memory overhead introduced with 3.7.0, and while your backup selection fitted within the memory constraints of 3.6.4 on your NAS, now suddenly it doesn’t. But because your backup set and archive is already so large, I guess there is no way back. You could try doing what some people on here have done and increase the heap to larger than your RAM size which will be horrible and slow, but it may allow you to downsize your backup set and instead have several smaller ones.

        I guess a good way to test would be to create a new sample backup set. Disable backup on the original one, and try to see if the new backup set actually works without constantly disconnecting.

  18. belnas

    @Patters, have you identified the issue of the continuously stopping and starting of the 3.7.0?
    Do you think is it solvable?

    Crashplan was working nicely before the 3.7.0,
    and now it stops just before starting to backup.

    Shall I forget about Crahsplan on a DS213j at all?
    or is there any hope to have it up and running again?

    Thanks for your work,

    *I started a glacier backup, but that will cost me $30/month for 3TB only in storage :(

    1. patters Post author

      As far as I can tell these issues were introduced by CrashPlan itself after the move to 3.7.0 unfortunately. My package is mainly concerned with wrapping the service up in a way that the Synology expects and so on. I can’t really influence how the code behaves.

    1. patters Post author

      CrashPlan push updates from their end. So even if you install 3.6.4 it would get broken by their updater. Also once your backup archive on their servers has been updated you can’t go back.

  19. scpotter

    I’m also seeing the start/stop problem. DS415+ DSM 5.1-5022 Update 2 (just updated) and Crashplan 3.7.0-0030 Maybe some how be related to the crashplan client on my mac.

    When I started writing this the log pattern was start, stop, waits a little over 2 minutes, then self start, stop, etc. A few things which are different than before 3.7:
    – With crashplan stopped and the DS idle (0% CPU, 0 traffic), I’m still seeing 67% of my 2GB RAM in use.
    – Even when the service isn’t running my mac client appears to connect to the DS. I used to see a message that it couldn’t connect. Now it launches, and I can resume a backup. This will create a start/stop entry in the log, and the CPU revs up on the DS.
    – Log pattern is the same before DSM 5.1-5022 Update 2 (from Update 1) and after

    Did more investigation:
    – Paused large job, stopped Crashplan service, powered down DS, restarted. Crashplan defaulted to running.
    – Opened Mac client, unpaused the large backup job, everything seemed ok, then Mac client crashed.
    – DS log entries show a different pattern of start, process 1 file, stop, repeat. This is better than nothing, so will leave this for now.

    Will update again when I have time to look at this again.

    1. scpotter

      As others suggested ssh’d in and edited USR_MAX_HEAP=2048M (which was commented out before) in this file:

      It hasn’t been an hour yet, but this seems to have stabilized everything, including the crashing Mac client. I’ve seen the java process consuming up to 950MB of RAM.

  20. RHC

    My DS212j (DSM 5.1-5022 Update 2) running CrashPaln 3.7.0-0030 will not hibernate the HDDs anymore. Have any of you experienced similar problems?

    I have set all the log settings to OFF (in /volume1/@appstore/CrashPlan/conf/ this worked for me in the previous version, but it is not working anymore.
    Any ideas on how to get HDD hibernating to working again.

  21. Martinos

    Hi Patters, I am running Crashplan version 3.7.0-0030 on my DS213+. The backup continuously stopping after scanning a few hundreds of thousands files, and then starting again. The moment that scanning of files stopped is always on my folder wich contains my (large) video files.
    Can you solve this issue? Thanks in advance!

  22. Mark

    Hi. Also getting the stop/start issue on a DS214play since updating to 0030. I would be very grateful for a solution, temporary or permanent as I have not been able to back up my NAS for some time. Many thanks!

  23. Daniel

    Newest updates of Synology DSM/Crashplan APP/Crashplan Desktop are not working.

    The Desktop updated itself last week, which caused it to lose connection to the APP. I updated the APP, and it did allow me to connect, but they were not connecting to the CrashPlan Cloud. I was several months behind on DSM updates, so I went ahead and updated that. Now the APP will not launch. Please Help.

    current versions:

    DSM: DSM 5.1-5022 Update 2
    APP: 3.7.0-0030
    Desktop: 3.7.0

    I’ve set DSM to allow “untrusted publishers” as well.

    1. patters Post author

      You can trick the package to upgrade over the top of an existing installation if you edit the package INFO file to an older version number. So in an SSH session try:
      cp /var/packages/CrashPlan/INFO /volume1/@tmp
      vi /var/packages/CrashPlan/INFO

      Press I to enter insert mode.
      Move the cursor to the version line and drop the package version suffix from 0030 to 0029
      Hit Escape
      type :
      type wq!

      Now refresh Package Center and upgrade CrashPlan which will keep all your settings and synchronization state etc.

      1. dmcgee333

        I get the message as below:
        >cp /var/packages/CrashPlan/INFO /volume1/@tmp
        >cp: can’t stat ‘/var/packages/CrashPlan/INFO': No such file or directory

      2. dmcgee333

        I Get this message:

        >cp /var/packages/CrashPlan/INFO /volume1/@tmp
        >cp: can’t stat ‘/var/packages/CrashPlan/INFO': No such file or directory

      3. dmcgee333

        I uninstalled CrashplanPRO from the syno. I tried to reinstall and i get “Java is not installed or not properly configured. JAVA_HOME is not defined. Downlaod and install”

        Java is installed as it has been the whole time

      4. patters Post author

        DSM updates used to break Java, but the current package version fixes itself automatically. Are you up to date? A reboot should cure that particular issue if so.

      5. patters Post author

        At the beginning you mentioned CrashPlan only, not CrashPlanPRO which uses a different package name – which is why that command didn’t work.

      6. dmcgee333

        OK, so what do i do now. Now i cannot install CrashPlanPRO because Java is not working. I rebooted the Syno, and still get the same error.

  24. Dale

    I was having similar trouble on the DS214+ after updating Crashplan to 3.7.0 and updating the headless client package. A Java update didn’t help either, but after updating to the latest DSM everything is working again. Thanks patters!

  25. steven

    I think i just fixed it, looks like the new version is really RAM hungry, at least 50% more. I had to modify the USR_MAX_HEAP setting to 1600Megs. It was 1024 megs before. It might not even be enough since the java process already shows 1500megs usage and the backup is not finished yet.

  26. caro.sim

    I don’t understand, I have install java embeded and crashplan 3.7 0030 for the first time but it’s not working
    /var/packages/CrashPlan/scripts/ start
    Starting CrashPlan …
    sed: /var/packages/CrashPlan/target/bin/ No such file or directory
    find: /var/packages/CrashPlan/target/upgrade: No such file or directory
    /var/packages/CrashPlan/scripts/ line 5: can’t create : nonexistent directory
    /var/packages/CrashPlan/scripts/ line 10: can’t create /var/packages/CrashPlan/target/log/engine_output.log: nonexistent directory
    renice: setpriority: No such process
    Could you help me please,
    Thank you

  27. Caro

    I have installed java embeded and crashplan 3.7 0030 for the first time, it’s not workin.

    I have Synology 215j, and i have this error :
    /var/packages/CrashPlan/target/bin/ No such file or directory

    Could you help me please,
    Thank You

  28. phloopy

    I have a brand new DS1815+ with almost nothing on it, trying to get CrashPlan set up before I start loading it up with data. I’ve gone through the standard installation, but the service keeps stopping itself a couple seconds after starting. Here’s the engine_output.log:

    The engine_error.log is empty and the system log doesn’t contain anything related to CrashPlan.

    I increased heap to 1536M (of my 2GB, soon to be expanded to 16GB) using Chris’s instructions above (editing /volume1/@appstore/CrashPlan/syno_package.vars and /volume1/@appstore/CrashPlan/bin/run.conf). The pasted logs are from after that change, but aren’t any different than before the change, other than the mention of heap size in the log.

    Any ideas of what to try? I can set up remote access (for patters) to the box if that will help.

      1. phloopy

        Is this issue with the DS215j that was just fixed the same issue as the DS1815+? It seems to have the same symptom any way. What was done to fix the DS215j?

      2. patters Post author

        That was related to which ARM binaries to use hard float or regular. It should have used hard float really but the glibc version on the DS215j is too old. Not much to do with Intel.

      3. phloopy

        I installed Java with Java Manager, per these instructions:

        It says I’m using Java 7.

        I uninstalled and re-installed the CrashPlan package just now and the same problem is occurring. I’ve set up an account for you on my DS1815+ if you want to take a look at the problem. How can I securely deliver the credentials to you?

    1. phloopy

      Pro Tip: Don’t set your SSH port to 4242 or CrashPlan will silently fail because the port it wants to use is already taken.

      Changed my SSH port and everything’s working (:

  29. Martinos

    After a few weeks of failures, my backup is working again. Scanning of files is finished now. A few gigabytes of data is ready to backup to my destinations now. The reason why the backups works again is unknown to me. (no updates are installed in the past day’s) Only the crashplan service must I manually start, because the package was stopped today.

  30. Alex

    I’m also running 3.7.0-0030 on my DS213+.
    I fixed the restarting issue by increasing the USR_MAX_HEAP too to 1500meg ish.
    However, now I have an old problem return. If I set the uploading bandwidth limit to say 10meg, Crashplan uploads at that speed but somehow throttles the speed on the rest of my network, practically bringing everything else to a standstill while it uploads.

  31. ptolemyiv

    It does seem like the new version of crash plan is much more memory consumptive and that 512MB is too small a heap size – it would be interested to know from code42 why this is the case but in the interim it seems like the only fix is the following:

    Edit the file “syno_package.vars” located at (research ssh’ing into the synology as root and vi if a newbie):

    Change the line beginning “USR_MAX_HEAP” to:

    I have a synology ds414 which has 1GB ram – I would not recommend doing this change if your synology only has 512MB.

    Patters – massively appreciate all your work but you’ve been a bit quiet of late… could I ask what diskstation you are using, how much ram you have and what setting you yourself are using for this?

    Also have you ever gotten directly in touch with code42 re better supporting your efforts? They’ve likely made a lot of money out of it (including from myself) so should be a bit more open to making the synology package stable..

    1. ptolemyiv

      As a follow-on to this, the good/great news is that my crashplan has now been running for the past few hours without the constant stop/start.. looking at processes on the NAS I can see that Java is consuming ~710MB of memory – hence definitely is a memory issue and the crashplan update resulted in a significant increase in memory requirements…

    2. patters Post author

      Hi – I’ve been on a course, followed by some holiday so haven’t had much time for responding on here. I used to have a DS111 (256MB). I now have a DS214Play (1GB). I only backup around 70GB and have not had any issues. I used it to keep all the code for these Synology projects safe, and photos.

      I did try to contact Code42 several times back when I was first putting the package together, and later when I was trying to solve realtime backup on Intel systems (which another user fixed) but they weren’t any help. Unfortunately they don’t offer any support to edge-case systems like headless NAS units. They did once look at some logs for me once they kind of knew who I was, but it was a best effort kind of thing (maybe about the realtime backup not working on PowerPC), and we never got to the bottom of it.

      1. ptolemyiv

        Thanks for clarifying – mine has been working again for the last day and a half now with just one stop, restart and full system scan… total of ~575GB.

        A bit ridiculous regarding Code42 – I will send them an email myself also (and encourage others to) since you are the sole reason I paid for a 3-year family plan so they should do more to appreciate and support this business!

    3. Clarence

      Followed this, but still no dice for me (DS1513+). My backup set is over 2TB.
      Though, changing this setting did get me from immediate start/stop to starting, detecting the remaining data set to be backed up (around 700GB). And subsequently stopping after 2 minutes. No backup done.

      Still looking for a solution.

      1. AJ Willmer

        I am running a DS1513+ and patters install of Crashplan is working fine for me with several quite large backup sets. I have 4096 MB RAM. Running DSM 5.1-5022 Update 2. Synology Java install 1.7.0_51. patters CrashPlan install 3.7.0-0030. I did uncomment the config line at /volume1/@appstore/CrashPlan/syno_package.vars and edit so that “USR_MAX_HEAP=2048M”. I run Crashplan sets of 704,805 files / 1.6TB, 114,552 files / 437.1GB, 2,942 files 984.1GB, 102,368 files / 132.9 GB. I back up to a second CP machine inhouse, Crashplan Central, and a remote CP server hosted by a friend. My CP Advanced Backup Settings are Data de-duplication “Minimal”, Compression “Automatic”, Encryption “Enabled”, Back up open files, and one set has Watch file system in real time. I have two clients and two friends backing up a total to 2TB to me. Let me know if you need any other information about my setup / configuration.

      2. Clarence

        @AJ Willmer

        Went back to check my config files and realised that the cause was not uncommenting USR_MAX_HEAP even after changing to 1024M. Which I have changed to 2048M as I too upgraded the RAM to 4GB.
        So I have that sorted. Speed is still abysmal at 1.4Mbps but that’s better than not backing up at all.

        So thank you for mentioning uncommenting, minor blunders can cause major headaches.

      3. AJ Willmer

        @Clarence is your ‘dismal’ speed issue when backing up to CrashPlan Central? I am always stuck in 1.5-18 Mb/s backing up to CrashPlan Central. However I am able to back up to Crashplan Friends at almost my full WAN UP speed, just shy of 20Mb/s. (I want gigabit internet!)

    1. Brad J.

      I’m on a DS412+ with DSM 5.1-5022 Update 2 running version 3.7.0-0030 of Patters package and am having no problems.

      1. jkasal

        Hi Brad J.

        Out of curiosity, how big is your backup set?

        I have a DS412+ running DSM 5.1-5022 Update 2 and still running the 3.6.4-0028 version of Patters and not having any issues. My backup set is just over 500GB.



  32. Christopher S Peisher

    Hi there, i searched for a solution to this problem. I found where someone posted the exact same issue back in November of 2014 but the person, Stephen Cranfill, did not get a response. I just re-installed the desktop client and I am getting the message “Destination unavailable – you have an older version). I am running 3.7.0-0030 on DS412+ with 2GB ram, running DSM 5.4-4493 Update 7. How do i fix the problem causing this error message?

    1. Stephen Cranfill

      Hi Christopher. I was the one who originally posted that issue. I don’t recall exactly what fixed it, but I do recall completely removing Crashplan and removing any trace of it after SSHing into the box. After that, I reinstalled and it worked again. This was also a day or so later, so it could have been timing too. Perhaps something was wonky on CP’s end.

      1. Christopher S Peisher

        Hi Stephen! I was able to fix that issue by uninstalling the client through the win7 uninstall box, and then deleting the Crashplan folder under program Data. This is also a “complete uninstall” according to Code 42. That worked for me.

  33. Fabian

    Just wanted to share my idea: because of the issues with CP I now set up the Diskstation as an iSCSI target and selected the new drive in Windows as the target path for CrashPlan. Works like a charm :-)

  34. Chip

    I’m at a total loss – CrashPlan no successfully starts. I’ve been using this solution for more than a year so I’m pretty familiar with how to configure it. I worked through the previous update issue by manually unzipping the files. Now with version 30 CrashPlan fails to run on my 1513+. I’ve uninstalled both Java 7 and CrashPlan and reinstalled without success. All I find in the log file is that CrashPlan has started with a GUID. The engine_output log looks normal and the engine_error log is empty. So it’s as if the process hangs without doing any work. Not surprisingly, I can’t connect to from the desktop either. Can anyone please suggest what I can do?

  35. Richard

    You need to either allow it more RAM (increase Max_Heap_Size) or create more backup sets. I agree, the new version seems to require more RAM than previous to complete the same backup sets. I currently have my max_heap set at 3Gb.

    1. Chip

      I’m afraid I’ve already tried that without success. I have 3GB allocated to heap and had previously established multiple sets. I think the problem is more fundamental as I don’t believe CrashPlan is even starting. There’s nothing to indicate that it’s scanning files for example.

      1. maxx

        I am in a similar situation as Chip. I have CrashPlan installed however I am not able to connect to the CrashPlan engine. I cant logon using the client configured to point to the servers ip address, and the clients cant connect to preform the back up. The service reports that it is running and there are no errors in the logs. I have two Synology servers both the same, on one it works (it has only one volume), on the other i have the problem (its has two volumes). It was previously working on both.

        I have tried reinstalling both java and the crashplan package. I have increased the memory as discussed. When comparing the one that is working and the one that is not, I notice that in the /volume1/@appstore/CrashPlan/log/app.log Under the License section it says ServiceModel.authorized=false. Could that be the problem or perhaps just because I have not reconfigure the engine since restarting?

        I also while logged on as root over ssh I tried to run this command to see the status but was given a security error.
        /var/packages/CrashPlan/scripts/start-stop-status status.

        Any advice how I can diagnose the issue preventing CrashPlan from loading correctly?
        I am considering removing the second volume to see if this is the cause.
        Regards, and thanks for the package.

      2. Stefan

        This looks very much like the problems I am having (see my comments on Jan. 20 at 5:30). My Crashplan service also seems to run, but clients are unable to connect, and I also cannot logon using the client configured to point to the servers ip address. Any help would be appreciated.

  36. Richard

    Not sure what to tell you. Mine would start and then slowly ramp up the memory consumed until it hit ‘Max_Heap’ then it would crash, restart and start over. I previously had Max_Heap set to 1750Mb but now it is set to 3076Mb with the same backup sets. Even with Max_Heap set at 2536Mb it would still bomb. One other thing, even when Resource Monitor says that Java is using 2.2Gb for example, running the ‘Top’ command from an SSH session shows it is using 3.3Gb.

  37. Chip

    Yes, very similar maxx. I also have 2 x DS1513+ but on neither one does CrashPlan work. Both utilize just 1 volume and both were working until about 45 days ago (according to CrashPlan website data). I also notice there are some strange messages in the log/service.log.0 file regarding issues with a remote peer (I’m not sure if this is CrashPlan central, or the second Synology box), including this line: WE have an old version, localVersion=1388728800370 (2014-01-03T06:00:00:370+0000), remoteVersion=1413349200416 (2014-10-15T05:00:00:416+0000), remoteGuid=-5795313247234236037 after which connections are dropped.

  38. maxx

    I removed my second volume to see if it was causing the issue. I also removed (moved) my old archives and then reinstalled Crashplan. No change to the issue as described above. I also see the message WE have an old version, localVersion=1388728800370. However the working server is running the same version.
    I also see a some disconnections after this occurs.

  39. Stefan Grevelink

    I’m trying to install CrashPlan, it is working fine on my DS213J, but on my new DS1515+, after accepting the terms I get an alert saying ‘Cannot install “CrashPlan”‘. Is the DS1515+ not supported?


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s