CrashPlan packages for Synology NAS

UPDATE – CrashPlan For Home (green branding) was retired by Code 42 Software on 22/08/2017. See migration notes below to find out how to transfer to CrashPlan for Small Business on Synology at the special discounted rate.

CrashPlan is a popular online backup solution which supports continuous syncing. With this your NAS can become even more resilient, particularly against the threat of ransomware.

There are now only two product versions:

  • Small Business: CrashPlan PRO (blue branding). Unlimited cloud backup subscription, $10 per device per month. Reporting via Admin Console. No peer-to-peer backups
  • Enterprise: CrashPlan PROe (black branding). Cloud backup subscription typically billed by storage usage, also available from third parties.

The instructions and notes on this page apply to both versions of the Synology package.


CrashPlan is a Java application which can be difficult to install on a NAS. Way back in January 2012 I decided to simplify it into a Synology package, since I had already created several others. It has been through many versions since that time, as the changelog below shows. Although it used to work on Synology products with ARM and PowerPC CPUs, it unfortunately became Intel-only in October 2016 due to Code 42 Software adding a reliance on some proprietary libraries.

Licence compliance is another challenge – Code 42’s EULA prohibits redistribution. I had to make the Synology package use the regular CrashPlan for Linux download (after the end user agrees to the Code 42 EULA). I then had to write my own script to extract this archive and mimic the Code 42 installer behaviour, but without the interactive prompts of the original.


Synology Package Installation

  • In Synology DSM’s Package Center, click Settings and add my package repository:
    Add Package Repository
  • The repository will push its certificate automatically to the NAS, which is used to validate package integrity. Set the Trust Level to Synology Inc. and trusted publishers:
    Trust Level
  • Now browse the Community section in Package Center to install CrashPlan:
    The repository only displays packages which are compatible with your specific model of NAS. If you don’t see CrashPlan in the list, then either your NAS model or your DSM version are not supported at this time. DSM 5.0 is the minimum supported version for this package, and an Intel CPU is required.
  • Since CrashPlan is a Java application, it needs a Java Runtime Environment (JRE) to function. It is recommended that you select to have the package install a dedicated Java 8 runtime. For licensing reasons I cannot include Java with this package, so you will need to agree to the licence terms and download it yourself from Oracle’s website. The package expects to find this .tar.gz file in a shared folder called ‘public’. If you go ahead and try to install the package without it, the error message will indicate precisely which Java file you need for your system type, and it will provide a TinyURL link to the appropriate Oracle download page.
  • To install CrashPlan PRO you will first need to log into the Admin Console and download the Linux App from the App Download section and also place this in the ‘public’ shared folder on your NAS.
  • If you have a multi-bay NAS, use the Shared Folder control panel to create the shared folder called public (it must be all lower case). On single bay models this is created by default. Assign it with Read/Write privileges for everyone.
  • If you have trouble getting the Java or CrashPlan PRO app files recognised by this package, try downloading them with Firefox. It seems to be the only web browser that doesn’t try to uncompress the files, or rename them without warning. I also suggest that you leave the Java file and the public folder present once you have installed the package, so that you won’t need to fetch this again to install future updates to the CrashPlan package.
  • CrashPlan is installed in headless mode – backup engine only. This will configured by a desktop client, but operates independently of it.
  • The first time you start the CrashPlan package you will need to stop it and restart it before you can connect the client. This is because a config file that is 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.

CrashPlan Client Installation

  • Once the CrashPlan engine is running on the NAS, you can manage it by installing CrashPlan on another computer, and by configuring it to connect to the NAS instance of the CrashPlan Engine.
  • Make sure that you install the version of the CrashPlan client that matches the version running on the NAS. If the NAS version gets upgraded later, you will need to update your client computer too.
  • The Linux CrashPlan PRO client must be downloaded from the Admin Console and placed in the ‘public’ folder on your NAS in order to successfully install the Synology package.
  • By default the client is configured to connect to the CrashPlan engine running on the local computer. Run this command on your NAS from an SSH session:
    echo `cat /var/lib/crashplan/.ui_info`
    Note those are backticks not quotes. This will give you a port number (4243), followed by an authentication token, followed by the IP binding ( means the server is listening for connections on all interfaces) e.g.:

    Copy this token value and use this value to replace the token in the equivalent config file on the computer that you would like to run the CrashPlan client on – located here:
    C:\ProgramData\CrashPlan\.ui_info (Windows)
    “/Library/Application Support/CrashPlan/.ui_info” (Mac OS X installed for all users)
    “~/Library/Application Support/CrashPlan/.ui_info” (Mac OS X installed for single user)
    /var/lib/crashplan/.ui_info (Linux)
    You will not be able to connect the client unless the client token matches on the NAS token. On the client you also need to amend the IP address value after the token to match the Synology NAS IP address.
    so using the example above, your computer’s CrashPlan client config file would be edited to:
    assuming that the Synology NAS has the IP
    If it still won’t connect, check that the ServicePort value is set to 4243 in the following files:
    C:\ProgramData\CrashPlan\conf\ui_(username).properties (Windows)
    “/Library/Application Support/CrashPlan/” (Mac OS X installed for all users)
    “~/Library/Application Support/CrashPlan/” (Mac OS X installed for single user)
    /usr/local/crashplan/conf (Linux)
    /var/lib/crashplan/.ui_info (Synology) – this value does change spontaneously if there’s a port conflict e.g. you started two versions of the package concurrently (CrashPlan and CrashPlan PRO)
  • As a result of the nightmarish complexity of recent product changes Code42 has now published a support article with more detail on running headless systems including config file locations on all supported operating systems, and for ‘all users’ versus single user installs etc.
  • You should disable the CrashPlan service on your computer if you intend only to use the client. In Windows, open the Services section in Computer Management and stop the CrashPlan Backup Service. In the service Properties set the Startup Type to Manual. You can also disable the CrashPlan System Tray notification application by removing it from Task Manager > More Details > Start-up Tab (Windows 8/Windows 10) or the All Users Startup Start Menu folder (Windows 7).
    To accomplish the same on Mac OS X, run the following commands one by one:

    sudo launchctl unload /Library/LaunchDaemons/com.crashplan.engine.plist
    sudo mv /Library/LaunchDaemons/com.crashplan.engine.plist /Library/LaunchDaemons/com.crashplan.engine.plist.bak

    The CrashPlan menu bar application can be disabled in System Preferences > Users & Groups > Current User > Login Items


Migration from CrashPlan For Home to CrashPlan For Small Business (CrashPlan PRO)

  • Leave the regular green branded CrashPlan 4.8.3 Synology package installed.
  • Go through the online migration using the link in the email notification you received from Code 42 on 22/08/2017. This seems to trigger the CrashPlan client to begin an update to 4.9 which will fail. It will also migrate your account onto a CrashPlan PRO server. The web page is likely to stall on the Migrating step, but no matter. The process is meant to take you to the store but it seems to be quite flakey. If you see the store page with a $0.00 amount in the basket, this has correctly referred you for the introductory offer. Apparently the $9.99 price thereafter shown on that screen is a mistake and the correct price of $2.50 is shown on a later screen in the process I think. Enter your credit card details and check out if you can. If not, continue.
  • Log into the CrashPlan PRO Admin Console as per these instructions, and download the CrashPlan PRO 4.9 client for Linux, and the 4.9 client for your remote console computer. Ignore the red message in the bottom left of the Admin Console about registering, and do not sign up for the free trial. Preferably use Firefox for the Linux version download – most of the other web browsers will try to unpack the .tgz archive, which you do not want to happen.
  • Configure the CrashPlan PRO 4.9 client on your computer to connect to your Syno as per the usual instructions on this blog post.
  • Put the downloaded Linux CrashPlan PRO 4.9 client .tgz file in the ‘public’ shared folder on your NAS. The package will no longer download this automatically as it did in previous versions.
  • From the Community section of DSM Package Center, install the CrashPlan PRO 4.9 package concurrently with your existing CrashPlan 4.8.3 Syno package.
  • This will stop the CrashPlan package and automatically import its configuration. Notice that it will also backup your old CrashPlan .identity file and leave it in the ‘public’ shared folder, just in case something goes wrong.
  • Start the CrashPlan PRO Synology package, and connect your CrashPlan PRO console from your computer.
  • You should see your protected folders as usual. At first mine reported something like “insufficient device licences”, but the next time I started up it changed to “subscription expired”.
  • Uninstall the CrashPlan 4.8.3 Synology package, this is no longer required.
  • At this point if the store referral didn’t work in the second step, you need to sign into the Admin Console. While signed in, navigate to this link which I was given by Code 42 support. If it works, you should see a store page with some blue font text and a $0.00 basket value. If it didn’t work you will get bounced to the Consumer Next Steps webpage: “Important Changes to CrashPlan for Home” – the one with the video of the CEO explaining the situation. I had to do this a few times before it worked. Once the store referral link worked and I had confirmed my payment details my CrashPlan PRO client immediately started working. Enjoy!


  • The package uses the intact CrashPlan installer directly from Code 42 Software, following acceptance of its EULA. I am complying with the directive that no one redistributes 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 large backup sets by editing /var/packages/CrashPlan/target/syno_package.vars. If you are 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 models with upgradeable RAM. Memory is very limited on the cheaper models. I have found that a 512MB heap was insufficient to back up more than 2TB of files on a Windows server and that was the situation many years ago. It kept restarting the backup engine every few minutes until I increased the heap to 1024MB. Many users of the package have found that they have to increase the heap size or CrashPlan will halt its activity. This can be mitigated by dividing your backup into several smaller backup sets which are scheduled to be protected at different times. Note that from package version 0041, using the dedicated JRE on a 64bit Intel NAS will allow a heap size greater than 4GB since the JRE is 64bit (requires DSM 6.0 in most cases).
  • 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 are trying to troubleshoot an issue you will need to use an SSH session to inspect these log files:
  • 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). The startup script will attempt to apply the published upgrade the next time the package is started.
  • Although CrashPlan’s activity can be scheduled within the application, in order to save RAM some users may wish to restrict running the CrashPlan engine to specific times of day using the Task Scheduler in DSM Control Panel:
    Schedule service start
    Note that regardless of real-time backup, by default CrashPlan will scan the whole backup selection for changes at 3:00am. Include this time within your Task Scheduler time window or else CrashPlan will not capture file changes which occurred while it was inactive:
    Schedule Service Start

  • If you decide to sign up for one of CrashPlan’s paid backup services as a result of my work on this, please consider donating using the PayPal button on the right of this page.

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 3rd Party Developer Guide.


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

[ "${SYNOPKG_PKGNAME}" == "CrashPlan" ] && DOWNLOAD_FILE="CrashPlan_4.8.3_Linux.tgz"
[ "${SYNOPKG_PKGNAME}" == "CrashPlanPRO" ] && DOWNLOAD_FILE="CrashPlanPRO_4.*_Linux.tgz"
if [ "${SYNOPKG_PKGNAME}" == "CrashPlanPROe" ]; then
  [ "${WIZARD_VER_483}" == "true" ] && { CPPROE_VER="4.8.3"; CP_EXTRACTED_FOLDER="crashplan-install"; OLD_JNA_NEEDED="false"; }
  [ "${WIZARD_VER_480}" == "true" ] && { CPPROE_VER="4.8.0"; CP_EXTRACTED_FOLDER="crashplan-install"; OLD_JNA_NEEDED="false"; }
  [ "${WIZARD_VER_470}" == "true" ] && { CPPROE_VER="4.7.0"; CP_EXTRACTED_FOLDER="crashplan-install"; OLD_JNA_NEEDED="false"; }
  [ "${WIZARD_VER_460}" == "true" ] && { CPPROE_VER="4.6.0"; CP_EXTRACTED_FOLDER="crashplan-install"; OLD_JNA_NEEDED="false"; }
  [ "${WIZARD_VER_452}" == "true" ] && { CPPROE_VER="4.5.2"; CP_EXTRACTED_FOLDER="crashplan-install"; OLD_JNA_NEEDED="false"; }
  [ "${WIZARD_VER_450}" == "true" ] && { CPPROE_VER="4.5.0"; CP_EXTRACTED_FOLDER="crashplan-install"; OLD_JNA_NEEDED="false"; }
  [ "${WIZARD_VER_441}" == "true" ] && { CPPROE_VER="4.4.1"; CP_EXTRACTED_FOLDER="crashplan-install"; OLD_JNA_NEEDED="false"; }
  [ "${WIZARD_VER_430}" == "true" ] && CPPROE_VER="4.3.0"
  [ "${WIZARD_VER_420}" == "true" ] && CPPROE_VER="4.2.0"
  [ "${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="armel"
[ "${SYNOPKG_DSM_ARCH}" == "armada375" ] && SYNO_CPU_ARCH="armv7l"
[ "${SYNOPKG_DSM_ARCH}" == "armada38x" ] && SYNO_CPU_ARCH="armhf"
[ "${SYNOPKG_DSM_ARCH}" == "comcerto2k" ] && SYNO_CPU_ARCH="armhf"
[ "${SYNOPKG_DSM_ARCH}" == "alpine" ] && SYNO_CPU_ARCH="armhf"
[ "${SYNOPKG_DSM_ARCH}" == "alpine4k" ] && SYNO_CPU_ARCH="armhf"
[ "${SYNOPKG_DSM_ARCH}" == "monaco" ] && SYNO_CPU_ARCH="armhf"
[ "${SYNOPKG_DSM_ARCH}" == "rtd1296" ] && SYNO_CPU_ARCH="armhf"
NATIVE_BINS_FILE="`echo ${NATIVE_BINS_URL} | sed -r "s%^.*/(.*)%\1%"`"
OLD_JNA_FILE="`echo ${OLD_JNA_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/"`"
#dedicated JRE section
if [ "${WIZARD_JRE_CP}" == "true" ]; then
  #detect systems capable of running 64bit JRE which can address more than 4GB of RAM
  [ "${SYNOPKG_DSM_ARCH}" == "x64" ] && SYNO_CPU_ARCH="x64"
  [ "`uname -m`" == "x86_64" ] && [ ${SYNOPKG_DSM_VERSION_MAJOR} -ge 6 ] && SYNO_CPU_ARCH="x64"
  if [ "${SYNO_CPU_ARCH}" == "armel" ]; then
    JAVA_BUILD="ARMv5/ARMv6/ARMv7 Linux - SoftFP ABI, Little Endian 2"
  elif [ "${SYNO_CPU_ARCH}" == "armv7l" ]; then
    JAVA_BUILD="ARMv5/ARMv6/ARMv7 Linux - SoftFP ABI, Little Endian 2"
  elif [ "${SYNO_CPU_ARCH}" == "armhf" ]; then
    JAVA_BUILD="ARMv6/ARMv7 Linux - VFP, HardFP ABI, Little Endian 1"
  elif [ "${SYNO_CPU_ARCH}" == "ppc" ]; then
    #Oracle have discontinued Java 8 for PowerPC after update 6
    JAVA_BUILD="Power Architecture Linux - Headless - e500v2 with double-precision SPE Floating Point Unit"
  elif [ "${SYNO_CPU_ARCH}" == "i686" ]; then
    JAVA_BUILD="x86 Linux Small Footprint - Headless"
  elif [ "${SYNO_CPU_ARCH}" == "x64" ]; then
    JAVA_BUILD="Linux x64"
JAVA_BINARY=`echo ${JAVA_BINARY} | cut -f1 -d'.'`
source /etc/profile

pre_checks ()
  #These checks are called from preinst and from preupgrade functions to prevent failures resulting in a partially upgraded package
  if [ "${WIZARD_JRE_CP}" == "true" ]; then
    synoshare -get public > /dev/null || (
      echo "A shared folder called 'public' could not be found - note this name is case-sensitive. " >> $SYNOPKG_TEMP_LOGFILE
      echo "Please create this using the Shared Folder DSM Control Panel and try again." >> $SYNOPKG_TEMP_LOGFILE
      exit 1

    [ -f ${PUBLIC_FOLDER}/${JAVA_BINARY}.tar.gz ] && JAVA_BINARY_FOUND=true
    [ -f ${PUBLIC_FOLDER}/${JAVA_BINARY}.tar.tar ] && JAVA_BINARY_FOUND=true
    if [ -z ${JAVA_BINARY_FOUND} ]; then
      echo "Java binary bundle not found. " >> $SYNOPKG_TEMP_LOGFILE
      echo "I was expecting the file ${PUBLIC_FOLDER}/${JAVA_BINARY}.tar.gz. " >> $SYNOPKG_TEMP_LOGFILE
      echo "Please agree to the Oracle licence at ${DOWNLOAD_URL}, then download the '${JAVA_BUILD}' package" >> $SYNOPKG_TEMP_LOGFILE
      echo "and place it in the 'public' shared folder on your NAS. This download cannot be automated even if " >> $SYNOPKG_TEMP_LOGFILE
      echo "displaying a package EULA could potentially cover the legal aspect, because files hosted on Oracle's " >> $SYNOPKG_TEMP_LOGFILE
      echo "server are protected by a session cookie requiring a JavaScript enabled browser." >> $SYNOPKG_TEMP_LOGFILE
      exit 1
    if [ -z ${JAVA_HOME} ]; then
      echo "Java is not installed or not properly configured. JAVA_HOME is not defined. " >> $SYNOPKG_TEMP_LOGFILE
      echo "Download and install the Java Synology package from" >> $SYNOPKG_TEMP_LOGFILE
      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. " >> $SYNOPKG_TEMP_LOGFILE
      echo "Download and install the Java Synology package from" >> $SYNOPKG_TEMP_LOGFILE
      exit 1

    if [ "${WIZARD_JRE_SYS}" == "true" ]; then
      JAVA_VER=`java -version 2>&1 | sed -r "/^.* version/!d;s/^.* version \"[0-9]\.([0-9]).*$/\1/"`
      if [ ${JAVA_VER} -lt 8 ]; then
        echo "This version of CrashPlan requires Java 8 or newer. Please update your Java package. "
        exit 1

preinst ()
    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, " >> $SYNOPKG_TEMP_LOGFILE
        echo "which was \"${WGET_URL}\" " >> $SYNOPKG_TEMP_LOGFILE
        echo "Alternatively, you may download this file manually and place it in the 'public' shared folder. " >> $SYNOPKG_TEMP_LOGFILE
        exit 1
  exit 0

postinst ()
  if [ "${WIZARD_JRE_CP}" == "true" ]; then
    #extract Java (Web browsers love to interfere with .tar.gz files)
    if [ -f ${JAVA_BINARY}.tar.gz ]; then
      #Firefox seems to be the only browser that leaves it alone
      tar xzf ${JAVA_BINARY}.tar.gz
    elif [ -f ${JAVA_BINARY}.gz ]; then
      tar xzf ${JAVA_BINARY}.gz
    elif [ -f ${JAVA_BINARY}.tar ]; then
      tar xf ${JAVA_BINARY}.tar
    elif [ -f ${JAVA_BINARY}.tar.tar ]; then
      #Internet Explorer
      tar xzf ${JAVA_BINARY}.tar.tar
    JRE_PATH="`find ${OPTDIR}/jre-syno/ -name jre`"
    [ -z ${JRE_PATH} ] && JRE_PATH=${OPTDIR}/jre-syno
    #change owner of folder tree
    chown -R root:root ${SYNOPKG_PKGDEST}
  #extract CPU-specific additional binaries
  mkdir ${SYNOPKG_PKGDEST}/bin
  [ "${OLD_JNA_NEEDED}" == "true" ] && tar xJf ${TEMP_FOLDER}/${OLD_JNA_FILE} && rm ${TEMP_FOLDER}/${OLD_JNA_FILE}

  #extract main archive
  #extract cpio archive
  cat "${TEMP_FOLDER}/${CP_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}/${CP_EXTRACTED_FOLDER}/scripts/CrashPlanEngine ${OPTDIR}/bin
  cp ${TEMP_FOLDER}/${CP_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}
  [ "${WIZARD_JRE_CP}" == "true" ] && echo JAVACOMMON=${JRE_PATH}/bin/java >> ${VARS_FILE}
  [ "${WIZARD_JRE_SYS}" == "true" ] && echo JAVACOMMON=\${JAVA_HOME}/bin/java >> ${VARS_FILE}
  cat ${TEMP_FOLDER}/${CP_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

  #are we transitioning an existing CrashPlan account to CrashPlan For Small Business?
  if [ "${SYNOPKG_PKGNAME}" == "CrashPlanPRO" ]; then
    if [ -e /var/packages/CrashPlan/scripts/start-stop-status ]; then
      /var/packages/CrashPlan/scripts/start-stop-status stop
      cp /var/lib/crashplan/.identity ${PUBLIC_FOLDER}/crashplan-identity.bak
      cp -R /var/packages/CrashPlan/target/conf/ ${OPTDIR}/

  exit 0

preuninst ()
  `dirname $0`/stop-start-status stop

  exit 0

postuninst ()
  if [ -f ${SYNOPKG_PKGDEST}/syno_package.vars ]; then
    source ${SYNOPKG_PKGDEST}/syno_package.vars
  [ -e ${OPTDIR}/lib/ ] && rm ${OPTDIR}/lib/

  #delete symlink if it no longer resolves - PowerPC only
  if [ ! -e /lib/ ]; then
    [ -L /lib/ ] && rm /lib/

  #remove firewall config
  if [ "${SYNOPKG_PKG_STATUS}" == "UNINSTALL" ]; then
    /usr/syno/bin/servicetool --remove-configure-file --package ${SYNOPKG_PKGNAME}.sc > /dev/null

 exit 0

preupgrade ()
  `dirname $0`/stop-start-status stop
  #if identity exists back up config
  if [ -f /var/lib/crashplan/.identity ]; then
    mkdir -p ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig/conf
      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}
  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/cpio |cpio ) %\1/${OPTDIR}/bin/cpio %" "${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 despite the above changes
  #so ignore the script and explicitly extract the new java code using the method 
  #thanks to Jeff Bingham for tweaks 
  UPGRADE_JAR=`find ${OPTDIR}/upgrade -maxdepth 1 -name "*.jar" | tail -1`
  if [ -n "${UPGRADE_JAR}" ]; then
    rm ${OPTDIR}/*.pid > /dev/null
    #make CrashPlan log entry
    echo "I ${TIMESTAMP} Synology extracting upgrade from ${UPGRADE_JAR}" >> ${DLOG}

    UPGRADE_VER=`echo ${SCRIPT_HOME} | sed -r "s/^.*\/([0-9_]+)\.[0-9]+/\1/"`
    #DSM 6.0 no longer includes unzip, use 7z instead
    unzip -o ${OPTDIR}/upgrade/${UPGRADE_VER}.jar "*.jar" -d ${OPTDIR}/lib/ || 7z e -y ${OPTDIR}/upgrade/${UPGRADE_VER}.jar "*.jar" -o${OPTDIR}/lib/ > /dev/null
    unzip -o ${OPTDIR}/upgrade/${UPGRADE_VER}.jar "lang/*" -d ${OPTDIR} || 7z e -y ${OPTDIR}/upgrade/${UPGRADE_VER}.jar "lang/*" -o${OPTDIR} > /dev/null
    mv ${UPGRADE_JAR} ${TEMP_FOLDER}/ > /dev/null
    exec $0

  #updates may also overwrite our native binaries
  [ -e ${OPTDIR}/bin/ ] && cp -f ${OPTDIR}/bin/ ${OPTDIR}/lib/
  [ -e ${OPTDIR}/bin/ ] && cp -f ${OPTDIR}/bin/ ${OPTDIR}/
  [ -e ${OPTDIR}/bin/jna-3.2.5.jar ] && cp -f ${OPTDIR}/bin/jna-3.2.5.jar ${OPTDIR}/lib/
  if [ -e ${OPTDIR}/bin/jna.jar ] && [ -e ${OPTDIR}/lib/jna.jar ]; then
    cp -f ${OPTDIR}/bin/jna.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"
    #default changed in CrashPlan 4.3
    sed -i "s/<serviceHost>localhost<\/serviceHost>/<serviceHost>0\.0\.0\.0<\/serviceHost>/" "${OPTDIR}/conf/my.service.xml"
    #since CrashPlan 4.4 another config file to allow remote console connections
    sed -i "s/127\.0\.0\.1/0\.0\.0\.0/" /var/lib/crashplan/.ui_info
    #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"

    #make sure CrashPlan is not binding to the IPv6 stack
    grep "\-Djava\.net\.preferIPv4Stack=true" "${OPTDIR}/bin/${ENGINE_CFG}" > /dev/null \
     || sed -i -r "s/(^${CFG_PARAM}=\".*)\"$/\1\"/" "${OPTDIR}/bin/${ENGINE_CFG}"
    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
  [ `cat /proc/sys/fs/file-max` -lt 65536 ] && 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

  #ensure that Code 42 have not amended install.vars to force the use of their own (Intel) JRE
  if [ -e ${OPTDIR}/jre-syno ]; then
    JRE_PATH="`find ${OPTDIR}/jre-syno/ -name jre`"
    [ -z ${JRE_PATH} ] && JRE_PATH=${OPTDIR}/jre-syno
    sed -i -r "s|^(JAVACOMMON=).*$|\1\${JRE_PATH}/bin/java|" ${OPTDIR}/install.vars
    #if missing, set timezone and locale for dedicated JRE   
    if [ -z ${TZ} ]; then
      SYNO_TZ=`cat /etc/synoinfo.conf | grep timezone | cut -f2 -d'"'`
      #fix for DST time in DSM 5.2 thanks to MinimServer Syno package author
      [ -e /usr/share/zoneinfo/Timezone/synotztable.json ] \
       && SYNO_TZ=`jq ".${SYNO_TZ} | .nameInTZDB" /usr/share/zoneinfo/Timezone/synotztable.json | sed -e "s/\"//g"` \
       || SYNO_TZ=`grep "^${SYNO_TZ}" /usr/share/zoneinfo/Timezone/tzname | sed -e "s/^.*= //"`
      export TZ=${SYNO_TZ}
    [ -z ${LANG} ] && export LANG=en_US.utf8
    export CLASSPATH=.:${OPTDIR}/jre-syno/lib

    sed -i -r "s|^(JAVACOMMON=).*$|\1\${JAVA_HOME}/bin/java|" ${OPTDIR}/install.vars

  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 $! > /dev/null
    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_483",
            "desc": "4.8.3",
            "defaultValue": true
          },          {
            "key": "WIZARD_VER_480",
            "desc": "4.8.0",
            "defaultValue": false
            "key": "WIZARD_VER_470",
            "desc": "4.7.0",
            "defaultValue": false
            "key": "WIZARD_VER_460",
            "desc": "4.6.0",
            "defaultValue": false
            "key": "WIZARD_VER_452",
            "desc": "4.5.2",
            "defaultValue": false
            "key": "WIZARD_VER_450",
            "desc": "4.5.0",
            "defaultValue": false
            "key": "WIZARD_VER_441",
            "desc": "4.4.1",
            "defaultValue": false
            "key": "WIZARD_VER_430",
            "desc": "4.3.0",
            "defaultValue": false
            "key": "WIZARD_VER_420",
            "desc": "4.2.0",
            "defaultValue": false
            "key": "WIZARD_VER_370",
            "desc": "3.7.0",
            "defaultValue": false
            "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
    "step_title": "Java Runtime Environment Selection",
    "items": [
        "type": "singleselect",
        "desc": "Please select the Java version which you would like CrashPlan to use:",
        "subitems": [
            "key": "WIZARD_JRE_SYS",
            "desc": "Default system Java version",
            "defaultValue": false
            "key": "WIZARD_JRE_CP",
            "desc": "Dedicated installation of Java 8",
            "defaultValue": true


  • 0031 Added TCP 4242 to the firewall services (computer to computer connections)
  • 0047 30/Oct/17 – Updated dedicated Java version to 8 update 151, added support for additional Intel CPUs in x18 Synology products.
  • 0046 26/Aug/17 – Updated to CrashPlan PRO 4.9, added support for migration from CrashPlan For Home to CrashPlan For Small Business (CrashPlan PRO). Please read the Migration section on this page for instructions.
  • 0045 02/Aug/17 – Updated to CrashPlan 4.8.3, updated dedicated Java version to 8 update 144
  • 0044 21/Jan/17 – Updated dedicated Java version to 8 update 121
  • 0043 07/Jan/17 – Updated dedicated Java version to 8 update 111, added support for Intel Broadwell and Grantley CPUs
  • 0042 03/Oct/16 – Updated to CrashPlan 4.8.0, Java 8 is now required, added optional dedicated Java 8 Runtime instead of the default system one including 64bit Java support on 64 bit Intel CPUs to permit memory allocation larger than 4GB. Support for non-Intel platforms withdrawn owing to Code42’s reliance on proprietary native code library
  • 0041 20/Jul/16 – Improved auto-upgrade compatibility (hopefully), added option to have CrashPlan use a dedicated Java 7 Runtime instead of the default system one, including 64bit Java support on 64 bit Intel CPUs to permit memory allocation larger than 4GB
  • 0040 25/May/16 – Added cpio to the path in the running context of
  • 0039 25/May/16 – Updated to CrashPlan 4.7.0, at each launch forced the use of the system JRE over the CrashPlan bundled Intel one, added Maven build of JNA 4.1.0 for ARMv7 systems consistent with the version bundled with CrashPlan
  • 0038 27/Apr/16 – Updated to CrashPlan 4.6.0, and improved support for Code 42 pushed updates
  • 0037 21/Jan/16 – Updated to CrashPlan 4.5.2
  • 0036 14/Dec/15 – Updated to CrashPlan 4.5.0, separate firewall definitions for management client and for friends backup, added support for DS716+ and DS216play
  • 0035 06/Nov/15 – Fixed the update to 4.4.1_59, new installs now listen for remote connections after second startup (was broken from 4.4), updated client install documentation with more file locations and added a link to a new Code42 support doc
    EITHER completely remove and reinstall the package (which will require a rescan of the entire backup set) OR alternatively please delete all except for one of the failed upgrade numbered subfolders in /var/packages/CrashPlan/target/upgrade before upgrading. There will be one folder for each time CrashPlan tried and failed to start since Code42 pushed the update
  • 0034 04/Oct/15 – Updated to CrashPlan 4.4.1, bundled newer JNA native libraries to match those from Code42, PLEASE READ UPDATED BLOG POST INSTRUCTIONS FOR CLIENT INSTALL this version introduced yet another requirement for the client
  • 0033 12/Aug/15 – Fixed version 0032 client connection issue for fresh installs
  • 0032 12/Jul/15 – Updated to CrashPlan 4.3, PLEASE READ UPDATED BLOG POST INSTRUCTIONS FOR CLIENT INSTALL this version introduced an extra requirement, changed update repair to use the method, forced CrashPlan to prefer IPv4 over IPv6 bindings, removed some legacy version migration scripting, updated main blog post documentation
  • 0031 20/May/15 – Updated to CrashPlan 4.2, cross compiled a newer cpio binary for some architectures which were segfaulting while unpacking main CrashPlan archive, added port 4242 to the firewall definition (friend backups), package is now signed with repository private key
  • 0030 16/Feb/15 – Fixed show-stopping issue with version 0029 for systems with more than one volume
  • 0029 21/Jan/15 – 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 22/Oct/14 – 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 equivalent 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 compression for native binaries to reduce web hosting footprint
  • 0027 20/Mar/14 – Fixed open file handle limit for very large backup sets (ulimit fix)
  • 0026 16/Feb/14 – Updated all CrashPlan clients to version 3.6.3, improved handling of Java temp files
  • 0025 30/Jan/14 – glibc version shim no longer used on Intel Synology models running DSM 5.0
  • 0024 30/Jan/14 – Updated to CrashPlan PROe and added support for PowerPC 2010 Synology models running DSM 5.0
  • 0023 30/Jan/14 – Added support for Intel Atom Evansport and Armada XP CPUs in new DSx14 products
  • 0022 10/Jun/13 – 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 01/Mar/13 – Updated CrashPlan to version 3.5.2
  • 0020 21/Jan/13 – 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 30/Jan/12 – intial public release

6,664 thoughts on “CrashPlan packages for Synology NAS

  1. Mike

    Anyone else having issues with the client randomly disconnecting? I’m running 3.64-0028 on a DS415+ with the Patters embedded Java 7 (7u71). I have 2GB allocated in syno_package.vars (I’ve upgraded my DS415+ to 8GB memory). I can remote connect the client and it runs for a random period of time and then just quits. There are zero entries in the engine_error log. I have multiple backup sets due to the size of my backup.

    1. Eric Henson

      I’m having this issue as well. The service restarts regularly, and the client closes itself whenever the service restart occurs.

    2. Marcus

      Mike, I’d like to know what memory module you bought. If possible a link to the item in the online store where you bought it. I’m going to buy a DS1815+ and would like to upgrade the memory to at least 8GB. Thanks!

    3. Mike

      Looks like this is a memory issue. I’ve upped the memory allocation in sync_package to 3072M and the client has been running successfully for over 1hr with no disconnects.

      1. Eric Henson

        Mike, I’d love to try this on our unit. Could you please direct me to where you changed that setting? I was unable to find any file with that name on the Synology device after poking around on the file system, but perhaps my Linux-fu is weak today.

    4. Mike

      Hi Eric

      You need to ssh or telnet into your box, and the file is /volume1/@appstore/Crashplan/syno_package.vars

      You’ll see an entry for USR_MAX_HEAP which you can modify. (Just make sure the line isn’t commented out, i.e. has a # at the beginning).

      You’ll need to restart the CrashPlan package on your box for it to read the new config.


      1. Eric Henson

        Mike, thanks so much! I’ve found the file (I guess my Linux-fu was indeed weak), and I’ll experiment with this. Might have to make a trip to get another RAM module, too.

      2. Eric Henson

        Mike, thanks very much for the tip. I wish I could report success, but uncommenting and bumping it from 512 to 1024 (our device presently only has 2GB RAM) produced no change in the resetting behavior.

    5. Mike

      If you’ve not already, I’d also try breaking your back up into sets. One strategy I also used when I was tight on memory was to bump up the memory allocation in increments until the disconnections happened. Then I’d set the backup sets to run at specific times overnight when the box wasn’t in use, and use the scheduling options in DSM to stop & start the CrashPlan package. That way I could allocate most of the boxes memory without affecting daily activities.

      1. Chris (@g0afr3ak)

        Having the same issue here. My DS 412+ has 2 GB of RAM. Before updating to DSM 5.1 everything was working perfectly, heap size for 1024MB was enough for almost 1.000.000 files. Now it’s crashing constantly. I tried to set the heap size to 2048MB, then the backup is running fine again, but the RAM usage on my DS is 80-90% all the time affecting the overall performance, so this is not a choice. I’m removing some directories from the backup now, hopefully reaching a stable state with 1024MB heap size again.
        I’m really wondering, why this happened after the update to DSM 5.1, as before that everything was smooth and easy…

  2. Jeff Mason

    I’ve read the thread pretty closely, but couldn’t find any updates on the “High iSCSI Utilization” with in my case DS412+, CrashPlan (headless on DS412+). I definitely have high, 100% iSCSI utilization when CrashPlan is running. As soon as I shit it down utilization goes back to 1-2%.

    Any updates that I missed?

  3. jeffmmason

    I have read and am following this thread concerning the “High Volume / iSCSI Utilization” with CrashPlan and Synology NASs, specifically DS 412+.

    I haven’t come across a solution and was wondering if I’ve missed anything concerning a solution, fix, update, ect?

    Configuration for future use:
    DSM 412+
    I haven’t come across a solution and was wondering if I’ve missed anything concerning a solution, fix, update, ect?

    Configuration for future use:
    DSM 5.1-5004
    CrashPlan 3.6.4 (headless on synology DS412+ according to PC LOAD)

  4. goslow2gofast

    Well, I followed the process and was able to get CrashPlan installed and running on my Synology DS413 on 11/08/2014, nd configured it from my Windows client fine, and had it backing up a modest test folder of some pictures. It ran for several days, but the last log entry is from 11/11/2014 saying “scanning for files completed”. I noticed today that it’s status was “stopped” so I tried starting it. It flips to running for a second or two, then goes back to stopped. No entries in its log file. Any thoughts, I didn’t make any changes to the NAS during that time.


  5. Chris (@g0afr3ak)

    Update to my previous post: The problem with the restarting client has to some kind of generic problem. I drastically reduced my backup directories to 5 with about 400.000 files, and still with 1024MB heap size the client is crashing all the time. Again, before the DSM 5.1 update I was backing up almost 1.000.000 files with 1024MB heap size!
    Another test: Heap size 1500MB. Now it’s working again, but my RAM usage is at 84% constantly. I don’t think this is an acceptable condition on the long term…

    Anyone has any suggestions why this is happening and how I can reduce the RAM usage of the client? Does the Java version (6-7-8) affect the RAM usage? I’m currently using version 1.8.0_06.

  6. Michael

    Hi: I have used CrashPlan on my PC and Macbook for a couple of years. I wanted to use it for my Synology as well. It is successfully installed and running on the NAS – but when I change the on my PC client to add the Synology IP address, it seems that I can no longer back up my PC? Isn’t it possible to have both? Any assistance appreciated.

  7. Alexandre

    I got a problem with crashplan. All is working on 4 NAS. But on a DS413, crahplan never worked. I never found the package in repo and i needed to install it manually.

    Then i can access crash, configure it, all is running well but when it finish to scan the files to save the backup never start. it s waiting for connection ( i test on crashplan server or another computer).

    Do i need to check a port is open or something like that ?

  8. John

    I would like to know how to re-install the previous version also, when i try the old install package was not available online. The crashplan packages are great and have come to rely on them, great work and thanks Patters.

  9. Hal Sandick


    First, Thanks all your work on this.

    I installed crashplan using your instructions about 17 months ago. the version on my server is 3.6.3. Now the java packages are showing up but not the crashplans ones. I tried deleting the link to your packages, rebooting and re entering it. Still only your java packages. i’m running the most recent version of dsm, DSM 5.1-5004,and have a ds213+

    any suggestions?


    1. Brad Sieve

      I could be wrong but last I heard (and have no success myself) getting the 213+ (powerpc) to work with the newest crashplan. There are comments about it before in the line and no updates I have seen,

  10. Tiestor

    I was running Crashplan on a DS414, and it worked perfectly and I loved it. After upgrading to DSM 5.1 and Crashplan 3.6.4 it stopped working properly, it’s starting and stopping after a few minutes. When I try to go back to Crashplan 3.6.3 by installing crashplan3.6.3-merged-0027.spk I get the error: “There was a problem downloading crashplan-native-armv7l.tgz from the official download link, which was “” Alternatively, you may download this file manually and place it in the ‘public’ shared folder.”

    Unfortunately, that file is removed so I am not able to restore the old working version of Crashplan, is there a way to resolve one of these issues to get back to a working version of Crashplan? Thanks in advance and I love your work.

  11. Enjoy


    I uninstalled version 3.6.3-0028 because did not work (I’ve written about this before).
    I downloaded version 3.6.3-0027 (crashplan3.6.3-merged-0027.spk) and I can not install.
    Also, at the moment I do not have CrashPlan on Synology :( Any idea?

    Could not update “CrashPlan”.
    There was a problem downloading crashplan-native-armv7l.tgz from the official download link, which was “”
    Alternatively, you may download this file manually and place it in the ‘public’ shared folder.

  12. Enjoy

    wOw :) uninstalled the latest version (after updating 3.6.3-> 3.6.4) and installed again 3.6.4 and now it works :)

    1. Eric Henson

      Congrats! Hopeful after hearing of your success, I tried reinstalling as well. It didn’t seem to solve the problem, but I then also doubled the NAS’s installed RAM from 2GB to 4GB and increased Java’s heapsize from 512MB to 2GB, which has allowed us to resume our backup with no more crashing!

      I don’t know about the long-term viability of this fix, but I’m just happy to be backing up again.

  13. ed

    Upgrading tonight to Synology DSM 5.1, Intel architecture DS1512+

    Using either the package center, or trying to use the spk from your package area, I get a ‘This package does not contain a digital signature’ error, and the update fails.

    1. ed

      That was quick resolution.

      There’s a new, or new to me anyway, Trust Level option in package center, General tab. Setting that to allow anyone allows the update to take. However, the update didn’t run. Not sure why. After 3 failed attempts I tried the combined package from your package center and manually installed. That ran, and backup complete. Go figure. Will Synology ever quit playing games on this package and just finally support it already. Without it, I’d just as soon toss this NAS in the trash.

      1. ed

        Interesting, come to notice it won’t run any longer, hasn’t since 4 days back when it ran successful the first time, backed files up, and now no longer runs. Trying to downgrade to prior version.

  14. Sid Mautte

    Anyone have any experience getting this to work with a pair of DS412+ configured in an HA cluster? Will the install via the primary interface cover both? Does the Crashplan need to be for 1 system or multiple to cover this scenario?

  15. Richard

    I installed your package on a 1812+ with 2Gb of RAM and it has been running great for about a week but since I just rebooted my NAS, the package won’t stay running, it says it started but then stops again almost immediately. I’ve tried reinstalling Java and rebooted again but it still won’t run – any ideas for what else to check next?


  16. Richard

    Here is the message in the log file

    Moss-Nas> cat engine_output.log
    [11.19.14 17:24:37.780 INFO main root ] JVM temp directory /var/@tmp does not exist!

    I simply went to that directory and did ‘Mkdir @tmp’ and now it stays running.

    1. John B.

      You could Instead just update the bin/run.conf file to point to a real existing @tmp folder,
      e.g. change “” to “”

      The real temporary folders are emptied on restart.

      1. bushwhackers

        A heads-up if anyone uses Richard’s solution.

        Looks like on re-boot, the @tmp directory you add at /var gets nuked at re-boot.(John B.’s comment now makes alot more sense)

        Have not tried updating the bin/run.conf file per John B.

  17. Stephen Cranfill

    Apologies if this has been discussed elsewhere, but I can’t find it if it has been.

    In troubleshooting an issue I was having, I uninstalled/reinstalled the Crashplan Pro package and am now getting the message:

    destination unavailable — you have an older version

    This is a freshly installed 3.6.4 package and the GUI install on my machine is also running 3.6.4. DSM is 5.1-5004. Anyone else seeing this?


  18. Stephen Cranfill

    As an addendum to this…. I attempted to revert to 3.6.3 without success, so I uninstalled 3.6.3 (I couldn’t get it to run). I then reinstalled 3.6.4 and it prompted me for a username and password as if the configuration has been removed (which I had tried to do manually earlier by renaming CrashPlan in /volume1/@appstore/). After re-entering that, all seemed to be well in the world again–no more “older version” message. Fab!


  19. Nicolas


    I have looked a bit a this topic because since the latest updates i have a constant crashplan restarting, making it unable to complete a backup.

    It’s running on a DS1010+ with 1gb ram. Crashplan was running fine but one day we noticed it had crashed. i couldn’t see the crasplan package on the package center ( old dsm version ) so i made all the DSM updates and reinstalled the latest crashplan package.

    I have a large set of files ( > 1.000.000 and more than 1Tb of data ). If i disallow the backup, it succeed the scanning and wait. But when it try to backup, the service restart after ~3 minutes…

    Any idea on how to fix this ?

    1. John B.

      Break your backup into small backup sets.
      Start with a single small set and keep reducing it until it works. Only then add a single extra set and repeat as before.
      I’m not sure what a sweet-spot is for you, but I have 6 sets. One of them contains 25k files at 81GB (i.e. large number of files) and another one with only 363 files but at 1.2TB (i.e. few but large files).

      1. Eric Henson

        I pushed off my similar issue by adding more RAM to the NAS, but I’m sure I’ll be dealing with this again one day as the backup size grows.

        John, I’d like to try out your backup sets solution, but I have a question about it. I presently have one very large set (~700,000 files at 1.8TB), and it’s backed up 70%. If I enable sets and then break this one up into multiple sets, am I going to have to restart the upload, or is CrashPlanPro smart enough to recognize it as duplicate data?

      2. John B.

        @Eric – there is a “Data de-duplication” setting in the Advanced backup settings.
        Personally, I’m using all types in my backup sets (Minimal, Full or Automatic), depending on what my needs are and what I am willing to wait for.
        I’m not sure what happens when you move a folder from one set to another, but you could test it with a smaller number of files.

      3. Eric Henson

        @John – Thanks for the encouragement to try! I broke my massive backup set into several smaller ones, and after a quick resync, it picked up right where it left off, with no progress lost! Disabling de-duplication (this is lots of archival data that doesn’t change) sped the process up from 2.5 Mbps to 15.0 Mbps. Hooray!

      1. Nicolas


        Thanks for the advice, i will test that right now.
        About dataset. If i remove a folder from one dataset and add it in an other data set, will i loose the versionning files infos of old backups ? the popup when un-selecting a folder is kinda scary about that.

  20. Johnny B


    I have a DS213j which was working sweetly with crashplan on 5.0. I have tried lots of the suggestions above to no avail (tried to install an older package, uninstalling, installing, upgrading the crashplan PC client). I am now running the latest version of the headless client, JAVA 7 package and PC client. The engine basically stops a few minutes after starting and the log file is empty of any information. The front end client cannot connect I have only 512 mb of RAM and its not easy I believe to increase that. Is this the end of the road. 16 months left on a 2 year subscription. Ah well. if there any updates on this situation I would love to hear it.


  21. Lonny

    I’m Testing this out on a rackststion with the latest dsm and 16Gb ram. When I assign more than 3.5gm ram to the java heap setting then Crashplan will not start. I’m thinking there might be a 64bit java needed. Anyone have any experience with this? I have about 12TB to backup.

  22. Pondo

    I see only the ProE version on the Repo, am I doing something wrong? Thanks for taking the time to make these work!

  23. Marcel

    Hi there … are there any news regarding the PPC-problem? … I own a DS213+ and Crashplan is still not running … :-(

    Thanks for your work!

    Best regards

  24. marc

    I own also a DS213+ which runs on a PowerPC with DSM 5.1. So the newest version of your package (3.6.4 0028) does not run. It always stays in the mode “waiting for backup”.

    So I tried to downgrade to 3.6.3 0027 which installs without any errors. But after starting – stopping – restarting it does not download and install the upgrade to 3.6.4 from the crashplan server. Any idea why this does not happen? Last time I tried this (some weeks ago) it worked perfectly … :-(


  25. Eric Henson

    Okay, I’m past my wit’s end, and lapsing into despair. Adding RAM, increasing the heapsize, and breaking up the data sets worked for a while, but we threw some more data onto the NAS, and it’s back to crash loops.

    I further divided the backup sets such that no set is over 1TB (problems seemed to previously begin around 1.9TB or so), but now there’s no change. The client crashes out and restarts during the initial scan, and never makes it to backing up files.

    I’m out of ideas, and I’m ready to throw this box out a window. Does anybody have any ideas for a desperate man?

    1. Eric Henson

      Further research suggests that CrashPlan requires about 1GB of available memory for every 1TB to be backed up, regardless of backup set breakdown. The amount of archival data we have to backup therefore makes a Synology/CrashPlanPro solution unsuitable. Heck, the whole CrashPlan system is pretty unscalable if that’s the case. “Unlimited storage” indeed.

      Thanks to everyone for their help, but I give up. Time to explore other backup solutions.

      1. Marcus

        This is not correct. I have 11 TB. And this worked perfectly well with my DS412+ which used 2 GB for Crashplan. It is only the number of files per backup set which matters.

      2. Eloi

        14tb with 300k files over 6 backup sets on 2gb of ram so I believe this solution does work. Although it did crash sometime but oh well no cheaper option than crash plan to date that work with nas or should I say nothing work with nas except for crashplan unless you count Amazon glacier.


      3. OecherWolke

        Hi Eric, this “rule” isn’t true. It depends on the amount of files, the settings (deduplication/compression) and the file size. Really huge files need more RAM for compression and deduplication. A big number of files in one job needs more RAM for the selection/analyzing process. I save about 11TB on a DS1513+ with only 4GB of RAM. The jobs are quite different. A “office”-job (office documents) and some “graphics-jobs” (JPEG, TIFF, PSD, PSB files) with sizes up to 3GB per file.

  26. goslow2gofast

    So, I have a DS413, and have had reasonable success with CrashPlan installed for the last month or so. But this weekend an update to DSM 5.1 was installed, and the machine rebooted, and now when I try to start the CrashPlan package it won’t stay running for more than a few seconds. No entries in it’s log file. Is this common, is there a fix?


  27. Daniel

    I have a Synology 214se and had everything working on DSM 5.1 until the 5004 update. Since DSM has updated, the crashplan app won’t run. Is there any simple way of getting it back to life? I tried re-installing Java SE 7, but it didn’t help. Installation according to PCload. Thank you!

  28. Aaron

    I just updated Crashplan on my Snynology 214+ running 5.1-5004 update 2. I also updated Java 7. Java 7 is running but Crashplan won’t start. When I try to run it manually I get the following message. “Failed to run the package service. Check package log……” Any ideas on getting Crashplan running again?

  29. B. Goodman

    On my stock DS412+, I’m currently running:
    DSM 5.1 Update 1
    Patters Java 1.7.0_71-0029
    CrashPlan 3.6.3-0027

    I’m being prompted to upgrade to:
    DSM 5.1 Update 2
    CrashPlan 3.6.4

    I’m thinking about staying where I am rather than risking breaking the whole thing. Constructive advice would be greatly appreciated!

  30. Maxime

    Hello i bought the new 215j and added the repo, but only 3 packets show ( open remote, minecraft, craftbukkit ). Does this mean the packages aren’t available for my processor (Marvell Armada 370 Dual Core)?
    Thanks for your work.

    1. patters Post author

      I will need to add in support for that CPU type, which is new (Marvell Armada 375). Please can you connect to your NAS with SSH and reply back here with the result of running this command:
      uname -a

      1. Maxime

        Thank you, here’s the message :
        Linux xxxx 3.2.40 #5004 SMP Sat Nov 29 01:35:02 CST 2014 armv7l GNU/Linux synology_armada375_ds215j

      2. Maxime

        Processor : ARMv7 Processor rev 1 (v7l)
        processor : 0
        BogoMIPS : 1594.16

        processor : 1
        BogoMIPS : 1594.16

        Features : swp half thumb fastmult vfp edsp neon vfpv3 tls
        CPU implementer : 0x41
        CPU architecture: 7
        CPU variant : 0x4
        CPU part : 0xc09
        CPU revision : 1

        Hardware : Marvell Armada-375 Board
        Revision : 0000
        Serial : 0000000000000000

      3. patters Post author

        I’ve just published an amended Java package for Armada 375. Can you check it works by ensuring you get the JVM and Hotspot versions displayed in the log section of the package? Once that’s confirmed working ok I can get support added to the other packages.

      4. patters Post author

        I’ve just published an amended Java package for Armada 375. Can you check it works by ensuring you get the JVM and Hotspot versions displayed in the log section of the package? Once that’s confirmed working ok I can get support added to the other packages.

    2. Maxime

      Ok i tried installing Java 7 but it failed. I created the public folder and put ejre-7u71-fcs-b14-linux-arm-vfp-hflt-server_headless-26_sep_2014 in it before, compressed or decompressed same result.

  31. belnas

    hi, all good,
    but after a reboot, the backup folders appear as “missing” on the crashplan desktop.
    but when I click them, it opens the NAS filesystem and the folders appear as selected.

    any advise?


  32. John

    I tried the CrashPlanPRO package and it seemed to be working, but upon rebooting the synology server the application does not restart. I tried restarting it manually using the start-stop-status script, but it reported directory errors. I uninstalled PRO then installed basic CrashPlan and it does restart when the server reboot.

    I think the PRO startup script has a bug.

  33. Jens

    Hi All!

    I successfully added the repository and was able to install Java (I took Version 7) and checked it is running. When I navigate to Community I see “Bliss, CraftBukkit, Java 6/7/8, Minecraft, Openremote and Servilo”, but Crashplan is missing! :-(
    I updated the package list, restarted my DS (it’s a DS413 with DSM 5.0-4528 Update 2) with no luck – the Crashplan Client is still not visible! :-(

    Can anyone PLEASE help??!?


  34. naPS

    Trying to download the package now, and it’s telling me it doesn’t have a digital signature. This is after the latest Syno update.

  35. WiFied

    Has anyone updated to DSM 5.1-5021? Any problems with Crashplan following the update? Crashplan been very stable for me on 5.1-5004, so just trying to avoid problems on DS1512+.

  36. Frazze

    I updated my DS214play to DSM 5.1-5021 and after that CrashPlan did not start, it also switched to stopped state as soon as I tried to start it manually. So I tried to re-install it but I only got an error message that said something like “Failed to install CrashPlan” following very soon after having accepted the CrashPlan Disclaimer.

    What I found out was that I needed to set the Trust Level to Any Publisher while doing the install. (I must have switched it back to “Synology Inc.” after I did the original install.).

    It now works perfectly again.

    Thanks for providing this excellent package!

  37. Wes Gurney

    I have DS413 with DSM 5.1-5021 and I am getting a Java exception when starting Crashplan service:
    [12.19.14 02:11:30.629 ERROR main backup42.service.backup.BackupController] Exception setting up BackupController! java.lang.UnsatisfiedLinkError: /volume1/@tmp/jna8085791042687730128.tmp: /lib/ version `GLIBC_2.11′ not found (required by /volume1/@tmp/jna8085791042687730128.tmp), java.lang.UnsatisfiedLinkError: /volume1/@tmp/jna8085791042687730128.tmp: /lib/ version `GLIBC_2.11′ not found (required by /volume1/@tmp/jna8085791042687730128.tmp)
    java.lang.UnsatisfiedLinkError: /volume1/@tmp/jna8085791042687730128.tmp: /lib/ version `GLIBC_2.11′ not found (required by /volume1/@tmp/jna8085791042687730128.tmp)
    at java.lang.ClassLoader$NativeLibrary.load(Native Method)
    at java.lang.ClassLoader.loadLibrary1(
    at java.lang.ClassLoader.loadLibrary0(
    at java.lang.ClassLoader.loadLibrary(
    at java.lang.Runtime.load0(
    at java.lang.System.load(
    at com.sun.jna.Native.loadNativeLibraryFromJar(
    at com.sun.jna.Native.loadNativeLibrary(
    at com.sun.jna.Native.(
    at com.code42.jna.LinuxPlatform.(
    at com.code42.jna.PlatformFactory.getLinuxPlatform(
    at com.code42.jna.inotify.InotifyManager.(
    at com.code42.jna.inotify.JNAInotifyFileWatcherDriver.(
    at com.code42.backup.path.BackupSetsManager.initFileWatcherDriver(
    at com.code42.backup.path.BackupSetsManager.setUp(
    at com.code42.backup.BackupManager.setUp(
    at com.backup42.service.backup.BackupController.setUp(
    at com.backup42.service.CPService.start(
    at com.backup42.service.CPService.main(

    [12.19.14 02:11:30.630 INFO main backup42.service.backup.BackupController] BackupController.setup(): EXIT

    Any ideas on how to fix? I am using Java 7 SE Embedded.


  38. B. Goodman

    OK, looking for more information on whether I should update CrashPlan to 3.6.4 on my DS412+ or leave well enough alone at 3.6.3. What does the update give me that I’m not getting now?

    1. WiFied

      3.4.6 working great on DSM 5.1 for me. There are release notes on the Crashplan website that outline the changes in 3.4.6 – security updates alone are reason enough to update.

  39. Jeff


    I’ve always had problems with crashplan not starting after rebooting. I’ve got a DS415+, and it looks like /tmp/@tmp is missing after a reboot.

    I edited /var/packages/CrashPlan/scripts/ and added a line near the top before the definition of TEMP_FOLDER that reads:

    test ! -d “/tmp/@tmp” && mkdir /tmp/@tmp

    which seems to be much better.

    FYI, in case others are having the same problem.


  40. Eluc

    I’ve just updated my DS1513+ (intel) to DSM5.1-5021 and then I’ve uninstalled/installed Java 6 package (I didn’t download the java file from Oracle again, I assume it hasn’t changed and I get no error to install Java 6). But now CrashPlan is stopped and choosing run has no effect. I’ve seen other people with the same problem in previous comments that are on different architectures and Java version. Any clue where to look for ?

    1. patters Post author

      I’ve just published an amended Java package for Armada 375. Can you check it works by ensuring you get the JVM and Hotspot versions displayed in the log section of the package? Once that’s confirmed working ok I can get support added to the other packages.

  41. Yacko

    I have updated from DSM 5.1-5004 Update 2 to DSM 5.1-5021, and i can’t start crashplan anymore …

    Un-installing and re-installing JAVA + Crashplan was needed to get it works again.

    Synology DS214+
    DMS 5.1-5021
    CrashPlan : 3.6.4-0028
    Java SE Embedded 7 : 1.7.0_71-0029

    1. captn

      Same here… DS212J, Same versions of everything else. Updated from DSM 5.1-5021 build 2 today and it was still broken so I had to do a reinstall

  42. Stig

    The package breaks on the Crashplan Proe 3.7.0 update from Code42. The update is downloaded, then the logs says “Synology repairing upgrade in /var/packages/CrashPlanPROe/target/upgrade/1388728800370.1419325211508” – and it never restarts


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 )

Google+ photo

You are commenting using your Google+ 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 )


Connecting to %s