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,692 thoughts on “CrashPlan packages for Synology NAS

  1. toojee

    Do you think I can use crashplan on windows to sync my windows pc with my synolgy NAS ?
    I have to install multiple crashplan ? How software do you use to sync all your PC with the NAS? thx

  2. cereyanli

    CP package is reporting as running and Backup report says %100 backed up but it does not backup latest files from last couple of months.. How can I track the issue ?

    1. Hauke

      I had the same problem, but discovered that I had set the Check for Changes in the Settings to 99 Days. Pressing Now started the upload of changes and checking for changes again. I have now set it to 2 days. I have a rather large backup set and I remember setting it to 99 days as at the time the backup never stopped scanning (reason was of cause that I had not increased the memory). Hope this helps.

  3. Martijn Damen

    I also have an interesting issue – the service starts and says it is running, but it seems it is not doing anything>

    admin@Soho-NAS:/volume1/@appstore/CrashPlan/log$ tail -f history.log.0
    I 09/10/16 03:35PM Stopping CrashPlan
    I 09/10/16 03:36PM Stopping CrashPlan

    Also there is no .ui_info created.

    I already tried to remove and reinstall everything, but the same.
    Anyone with thoughts on this?

    Thanks, Martijn

  4. Marten

    First off thank you for your continued support.

    My problem is the crashplan client (OSX, 4.7.0) refuses to even try to connect to the server (Synology 1811, 6.0.2-8451-1, CP 4.7.0 0041).

    I conclude this from the fact that a telnet 4243 shows up in the server service.log.0 as UISession Created, while starting crashplan client doesn’t give a peep in the server logs.

    On OSX Client:
    ~/Library/Application Support/CrashPlan/

    /Library/Application Support/CrashPlan/

    /Users/username/Library/Application Support/CrashPlan/.ui_info:

    Any ideas?

  5. Stuart (@escapologybb)

    can anyone tell me why CrashPlan keeps stopping and during the debugging process every time I run echo `cat /var/lib/crashplan/.ui_info` on the Synology I get a different port number from the first time?

    For instance, in the instructions above the following example is given, where the first four numbers are the port number used for communication between the client and server:


    This is all fine and dandy the first time I set up CrashPlan on the server, obviously the token is different on my setup, but as of 30 seconds ago the first four numbers are 4261 and my Synology is not being backed up to CrashPlan and hasn’t for the past three days, when this happened last time the first phone numbers were 4251. The only way I’ve been able to rectify the problem has been to completely uninstall and reinstall both client and server packages, which seems a crazy waste of time. Can anybody help me with this?

    I love that you’ve gone to the time of making this package, but it’s driving me crazy and I would really appreciate some help, there may be a small prize for the winner of this question! :-)

    1. Monte Moore

      Hello all, Patters, thanks for all the help you and others provide. I recently ran into an issue with my crashplan “analyzing data” forever it seems. I have named my synology DS151+ volume, “volume 1”. On the crashplan backup window it reads the following. “Analyzing: volume1 > @EP>EP_TBL It stays in this mode forever and then when I check my computer to see how the “analyzing” process is going then it says that crashplan has “disconnected from the server”. It seems to disconnect all the time. It did back up well at one point, but this is crazy. I’ve read several posts talking about how to change the Java Heap Size but I can’t seem to locate the actual file to do so. I changed the crashplan memory size to 3072 and restarted but I’m not sure if I need to change the synology crashplan java heap size.. This is most likely due to my ignorance as to how this stuff works. You guys really amaze me at how you can figure all this stuff out. I’m using an Imac and have the latest updates for the crashplan and java etc. I was thinking maybe it was a memory mismatch for lack of a better word.

      I’ve looked at your posting and tried to go down the file paths to find the file to change the java heap size number but can’t seem to locate it. If someone could point me to how to go about the SSH directions to get to the file in the synology or maybe just education me as to how to find it, I would be forever grateful.

      I wish synology and crashplan would just get together and get this stuff working together so it isn’t so difficult. I saw where Backblaze works with synology now. Anyway, thanks in advance for any help you might be able to provide. Monrte Monte Moore


      1. Jeff

        I am seeing the same thing. Lot os disconnects from clients trying to backup to the server running on synology.

  6. Andy Fitter

    I’ve looked back through all the old replies here but can’t find an answer. Is there a way to install a 64bit JRE on DSM 5.X? If so, can somebody point me to where the instructions are? I’m kind of stuck on DSM 5.X due to compatibility issues.

    My Crashplan seems to have reached the heap limit on 32 bit Java.



  7. Lumiere

    hi all,
    the following java 64 bit and steps has been tested on DS1815+(16GB ram) DSM5.x

    use the java manager provided by synology/oracle
    download jdk-7u80-linux-x64.tar.gz from oracle site.
    rename to jdk-7u80-linux-i586.tar.gz
    stop crashplan
    update using the java manager
    change your heap size to a larger value.
    start crashplan.

    monitor your Resource Monitor , Process and see memory usage grow beyond 3.7gb without crashing. ^_^

    ds1815> uname -a
    Linux ds1815 3.10.35 #5967 SMP Tue Apr 26 16:28:16 CST 2016 x86_64 GNU/Linux synology_avoton_1815+
    ds1815> which java
    ds1815> java -version
    java version “1.7.0_80”
    Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
    Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)

    ds1815> grep MAX syno_package.vars

  8. mgittelman

    Looks like version 1435813200480 was released today. Failed on extracting upgrade from 1435813200480_286.jar. Anyone else having issues yet?

  9. stevens420

    It keeps closing the GUI and attempting to install the upgrade, but failing, every 30 minutes. Otherwise everything continues to work normally.

  10. stevens420

    There has to be a way to cancel these forced “updates” that seem to make Crashplan less memory efficient each time.

  11. Eric Jolley

    Hi I have Auto Update turned off but the CrashPlan Pro app insists on stopping, downloading a new version then won’t run again.

  12. Rogier

    Hi all, Patters,

    Same issue here, the automatic upgrade to version 1435813200480 won’t work.
    Already removed everything and tried a clean installation, but no luck…
    Any help would very much appreaciated to keep Crashplan running again!


    1. ajwillmer

      I am having the same issue of upgrade not working. In engine_error.log I have “Error: Could not find or load main class com.backup42.service.CPService”

      1. aadhoc78

        I just had same problem. I uninstalled/reinstalled the service, fixed the Crashplan token in client’s .ui_info, reran the crashplan client (gave it the encryption key again), and its scanning again. I think I’m back to normal.

    2. Robert

      I tried to run the upgrade again:
      cat ./upgrade.cpi | gzip -d -c — | cpio -iv

      But now engine_error.log shows:
      Exception in thread “main” java.lang.UnsupportedClassVersionError: com/backup42/service/CPService : Unsupported major.minor version 52.0
      at java.lang.ClassLoader.defineClass1(Native Method)
      at java.lang.ClassLoader.defineClass(
      at Method)
      at java.lang.ClassLoader.loadClass(
      at sun.misc.Launcher$AppClassLoader.loadClass(
      at java.lang.ClassLoader.loadClass(
      at sun.launcher.LauncherHelper.checkAndLoadMain(

      1. Robert

        Turns out the crashplan doesn’t like java 1.7, which is why the installer initially tried to install its own 1.8. I uninstalled patters’ 1.7 and installed his 1.8 and crashplan run now. So all I did was:

        1. copy cpio to /bin (I thought I previously made a symlink to cpio)
        1. sudo cat ./upgrade.cpi | gzip -d -c — | cpio -iv
        2. added back USR_MAX_HELP to syno_package.vars
        3. uninstall patters’ java 1.7 and install patters’ java 1.8 from package center
        4. start crashplan from package center

      2. Martin

        Bravo Robert. This got me working. I’m a little unsure of the actual resolution but I did something similar to this:

        1. Uninstall Crashplan
        2. Reinstall Crashplan (system java as I’ve installed Synology Java 8 x64 101)
        3. Wait for stop
        4. Start
        5. Wait for stop
        6. SSH to synology
        7. cd /volume1/@appstore/CrashPlan
        8. sudo cat ./upgrade.cpi | gzip -d -c — | cpio -iv
        9. Start Crashplan
        10. Successfully running 4.8


        No connection to crashplan central (Destination unavailable – you have an older version)

        Obviously my desktop client is still 4.7, but I don’t believe this should cause the problem.

      3. Martin

        Just got off chat with Crashplan support who tell that they are seeing Destination Unavailable issue with supported clients, so it appears to be on their end.

        I’ve a ticket raised and updates should come.

      4. shashachu


        When you reinstalled did you have to re log in to CrashPlan or did it save your credentials? I can get everything running, just can’t log in. Thanks!

      5. Sean Nicoara

        I’ve tried using the steps you outlined Martin, but at step 8 I’m getting an error..

        When running this:
        sudo cat ./upgrade.cpi | gzip -d -c — | cpio -iv

        I get this:
        -sh: cpio: command not found
        gzip: —.gz: No such file or directory

        Any idea’s? Linux really isn’t one of my strengths..

      6. klauspeter

        Fist, if it can’t find cpio, cpio isn’t in /bin – did you copy it from /var/packages/CrashPlan/target/bin to /bin?
        Second, the long dash — ist actually two short dashes – – one right after the other without a space.
        Third, you should run the command as super user – you can do that by enter “sudo sh” before entering the command. Just typing “sudo” in front of it doesn’t work, as there are actually three commands in that line and if you type “sudo” in front of it just the first one gets run as super usr. Just remember to exit after doing that.

  13. Scott Egan

    I have a DS716+ that installs Patters Crashplan app (version 4.7 on latest version of DSM)just fine but when I go to stop and restart the service to allow for connections I get the error “Failed to Stop the package service” I click OK and the service reports that it is stopped and can be restarted but it does not allow for connections from the client. I have installed this package many times for friends and family but am coming across the error now.

    Any suggestions?


    1. Michael

      Hi guys, I basically did what Martin did above (also used system Java v8 which I installed prior to re-install of CP) and installed the client again. I also checked and grabbed the content of the .ui_info file below and re-added to the equivalent file on the client end:

      cat /var/lib/crashplan/.ui_info

      I also noted the port had changed from 4243 to 4253.

      All now working again until the next time it breaks :-(

  14. Danoz

    Hi folks,

    I have an idea I’d like to float with everyone.

    What are the thoughts about moving the source code for this package up to GitHub?

    That way, the community members could contribute to the codebase and share the load of producing fixes if/when necessary. My thoughts are to help lighten the load for Patters in maintaining this fine piece of technology he has created.

    What do you think Patters? If you wanted to retain control, you could remain owner of the repository and thus have final say over any pull requests submitted by collaborators.


  15. shashachu

    I got the service running again with the 1435813200480_286.1475207180183 upgrade, but I can’t log in. I had to manually unzip the upgrade .jar file and move the lib directory and all the .so files into /crashplan. I also had to install Java 8 embedded and update the JAVACOMMON directory in install.vars. That all said, when I try to log in, I get a server error. The service logs say it’s because the AuthorizedStorageService isn’t running. I checked the engine_error log, and it says the AuthorizedStorageService failed to run because it can’t find That file exists, so I have to assume it’s just not compiled for ARM. It seems to be a CrashPlan-created file, so now I’m stuck.

  16. Yves Soers

    I have received the update on 1 of my 2 devices.

    Packages was stopped, but worked again after I started the package again. Now version 4.8 is running.

    I have Java8 from Synology installed.

    1. Jay

      It looks like the CP update now needs jre 1.8.0_72. The jre that Synology has is 1.8.0_101-b13. The installer logs say the current Java version is not compatible and is embedding 1.8.0_72.

      The installer log also show the script is once again unable to find the path for cpio: line 232: cpio: command not found

      I think that’s what Patter’s last update was hoping to have fixed according to his post from July 20th.

      The only script I can find is in /etc, and there’s no reference to cpio in that script. The only cpio I find is at /volume1/@appstore/CrashPlan/bin/cpio.

  17. dbork2014

    Thank you very much! Your solution worked for me, I just had to use a slighly changed command in step 8 since I did not link cpio.

    8. sudo cat ./upgrade.cpi | gzip -d -c – | sudo bin/cpio -iv

    It seems that CrashPlan has fixed their connectivity problem, I am showing a connection using version 4.8

    1. jamesdeanreeves

      It looks like the CP update now needs jre 1.8.0_72. The jre that Synology has is 1.8.0_101-b13. The installer logs say the current Java version is not compatible and is embedding 1.8.0_72.

      The installer log also show the script is once again unable to find the path for cpio: line 232: cpio: command not found

      I think that’s what Patter’s last update was hoping to have fixed according to his post from July 20th.

      The only script I can find is in /etc, and there’s no reference to cpio in that script. The only cpio I find is at /volume1/@appstore/CrashPlan/bin/cpio.

      1. jamesdeanreeves

        I managed to get mine running.

        I copied cpio to /usr/bin and softlinked it to /bin

        uninstalled then reinstalled CP on the Synology, and it upgraded itself fine – even though Patter’s package says 4.7blah, the logs says it’s 4.8.

        Patters has done an outstanding service to us all with what he’s done and continues to do – we all owe him a LOT!

        But we can’t expect that forever.

        With that said, I’m jumping ship and telling Crash Plan to go e’f themselves – Crash Plan should be the ones supporting headless operations and making our life easier. I shouldn’t have to be spending 2-3 hours of my time every other month fixing something I am paying for.

        I’ll be checking out an earlier posters comment about using Backblaze with Synology Cloud Sync as well as others.

  18. Ernst von Harringa

    Can also mount the Synology shares on a Mac and back it up that way without all the constant fixing every time the app auto updates. Been doing this for 6+ months now…

  19. Per


    Back to this again…

    Mine fell over too. I managed to get 4.8 running on the NAS (linked cpio to /bin etc). However as I uninstalled/re-installed I need to get the key inserted again.

    I’ve upgraded my PC to CP 4.8 and when I try to re-connect the NAS to the cloud I find this in the engine_error.log:
    Unable to load library ‘c42archive’: Native library (linux-arm/

    Looks like something’s needs patching again.

    Anyone else getting this far?


    1. shashachu

      I’m in the exact same position. I don’t have a solution. It’s probably not compiled for ARM so I don’t know how we can fix it.

    2. Marcel

      Hi all,

      My DS413 is now also running 4.8.0 after upgrading, but on the Crashplan site I’m only able to find version 4.7.0. When I try to connect from Windows client (still 4.7.0) to the NAS, I get a system error. Has anyone been able to connect to 4.8.0 using a 4.7.0 client?


      1. Kevin

        I’m having the same issue. I can’t connect with the 4.7 client. I get the system error message. Not sure why we Crashplan is not offering the 4.8 client.

      2. wittgenfrog

        Strangely on mine (DS916+) fell-over (4.8 on Synology-reported as 4.7 , 4.7 client on PC ) at first, but strangely it now all works. I didn’t do anything to upgrade (apart from tearing my hair), it simply started working for no obvious reason.

  20. Dmitriy

    It appears that the old list of commands to upgrade the client running on a Synology DS is no longer working. I get a solid reply from the Synology
    -sh: unzip: command not found

  21. Singularity

    Running 5.2 with a 412+ and it now refuses to upgrade to 4.8! I WAS running 4.7 with Java Manager and Java 7 (System) with pretty much no issues. Then this 4.8 came out and really screwed it up! I’ve gone through all the different techniques I’ve found but no dice. I’ve upgraded Java 8 and I know it’s good cause from command line I can just type ‘java’ and I’ll get the correct output. Of course I reinstalled CP a bunch of times each time selecting System Java.

    For the heck of it I removed Java Manager, then went ahead and installed Patters Java 8 which seemed to go okay. When I installed CP again I selected dedicated but it complained about wanting Java 7 so it bombed it. I told it to use System Java which then worked okay. I fire it up and it’ll run, download the update, then bomb out like usual. The interesting thing is that when I again go to command line and type ‘java’ it doesn’t find it so the path isn’t there. When I look in install.vars I see that it’s looking for System Java which it can’t find obviously. If I edit it to the correct path then restart CP it’ll overwrite it so of course it bombs!

    What the heck??

  22. Brian Olbivion

    (0) Stay calm.
    (1) Uninstall CrashPlan package
    (2) Reinstall CrashPlan package
    (3) ssh to your DS; cd /volume1/@appstore/CrashPlan/
    (4) mv upgrade upgrade.tmp
    (5) touch upgrade

    CrashPlan will remain as 4.70, repeatedly fail to upgrade, but function as before. Be patient. When Patters has time, he will fix the package.
    (6) Be grateful.

  23. Sean Nicoara

    I’ve followed the steps listed by Martin above, and at step 8, im getting an error. The command im using is: sudo cat ./upgrade.cpi | gzip -d -c — | cpio -iv
    im getting: -sh: cpio: command not found
    I know it’s something to do with cpio not being included in synology’s os, but.. how do i get around this? its been days without a backup =\

  24. Babachan

    I tried a couple of times to restart package but that didn’t work. I had Synology Java7, I also installed Java8 and now it is working again.

  25. jamesdeanreeves

    I give up – I’ve been trying to post a comment and it appears I’m being blocked – maybe the content which has a link to the 4.8 client?

  26. jamesdeanreeves

    I chatted with a CP Support person yesterday, and he said “they’re still rolling out 4.8” – not sure what the hell that means and why it’s taking CP so long to get it out there – the Release notes have been out there since Thursday. The support person gave me a link for the 4.8 download:

    (link removed by me to test this)

    I didn’t update my client to 4.8 – it’s still at 4.7. And oddly enough it’s connecting to the CP server just fine which is at 4.8. I didn’t think it was supposed to be able to do that!

    Be sure the ports match in the .ui_info file on your client and to what is on the server. Mine seems to have changed to 4253.

    Just an FYI, I removed all java versions on the NAS, installed Synology’s Java 8, then when I installed CP, I selected the option for the install to use the one bundled with CP – that’s what worked for my Java issue.

  27. jamesdeanreeves

    That’s what it was – it didn’t like the link and I have tried several different ways to get it thru – anyone have any ideas how to post links here?


  28. m rombout

    In my case I copied CPIO to /usr/bin and then executed cat ./upgrade.cpi | gzip -d -c | cpio -iv from /volume1/@appstore/CrashPlan

    Archive extracted and the service was startable again from the Synology Package center

  29. Martin

    DS213j; stopped at
    I 09/30/16 01:00AM Synology extracting upgrade from /var/packages/CrashPlan/target/upgrade/1435813200480_286.jar
    a few days ago.

    I installed Java8 package from Synology (it’s the only Java package I have installed) and started the CrashPlan package and after a few minutes everything is running again…!
    I 10/02/16 08:17PM CrashPlan started, version 4.8.0, GUID 551757018175111170

  30. OJ

    This is what I did to get the service running again:

    * ssh to the NAS (I su to root so that I don’t have to sudo all the things!)
    * run: 7z e -o./ /var/packages/CrashPlan/target/upgrade.cpi
    * run: rm /var/packages/CrashPlan/target/upgrade.cpi
    * run: 7z e -o/var/packages/CrashPlan/target/lib ./upgrade
    * run: rm upgrade
    * Restart the Crashplan application.

    The service should now run.

  31. Sean Nicoara

    OK, I got it working. So hopefully the below helps someone, because I’m pretty hopeless with Linux and just fumbled my way through this.

    1. Uninstalled CP
    2. Uninstalled all versions of Java
    3. *Important – make sure DSM is up to date. as of writing i have DSM 6.0.2-8451 installed.
    4. Install Patters Java 8 package
    5. Install CP and allow it to start. It’ll stop eventually with a failed upgrade.
    6. SSH into synology.
    7. Ensure that you have cpio at /bin by running “sudo cp /var/packages/CrashPlan/target/bin/cpio /bin/cpio”
    8. Edit “/var/packages/CrashPlan/target/install.vars” by typing “sudo vi /var/packages/CrashPlan/target/install.vars”
    9. Modify your JAVACOMMON line to be /volume1/@appstore/java8/ejdk1.8.0_101/linux_i586/jre/bin
    10. Save the file (google vi commands if you don’t know how to use it)
    11. Start up crashplan package. it should run properly now.

    You’ll need to complete the usual guid steps in order to connect a client to the server.

    Hope this helps someone.

    1. Min


      I followed your instruction and got Crashplan synology packaging running (it’s identified as 4.8.0). However when I tried to run the desktop client, it asked me to log in again and gave “System Error, if persist reinstall Crashplan”, I reinstalled and it gave the same error. The client is only 4.7.0 (latest version from Crashplan website). Anything I can do?

      1. Sean Nicoara

        Did you do the last step? Replace the GUID in the config file? You’ll find the instructions on the Chris Nelson page, but to repeat them, they are:

        1. SSH into Synology
        2. run “cat /var/lib/crashplan/.ui_info ; echo”
        3. Copy and paste results from step 2 into “C:\ProgramData\CrashPlan\.ui_info” on your client computer
        4. Ensure that you change the last part of the string to the IP of your nas, don’t leave it as
        5. Save the file and try start the client again. Should work this time.

  32. DJ Uittenbogaard (@DJ_F3)

    After running into this situation over and over again I would love to switch over to a different backup provider. (even though this forum and our host do a fantastic job).
    > What is a good alternative to Crashplan on Synology? (pricing/features)

      1. Rich

        Also looking at BackBlaze B2. Be careful if you use encryption, had an issue where they had to update the package. Also, I’m happening issues with multiple backups from the same volume to the same bucket, with the same application key.

        Is there a better place to discuss this you could point me towards?

        I’m hoping to upgrade my NAS, and move the DS413 (ARM) to just a backup of something larger, with crashplan on the newer one; but I’m still considering.

        Also, patters — Thanks for all the support and work over the years.

  33. patters Post author

    New package released for 4.8.0.

    Java 7 no longer works, so the dedicated JRE option has now been updated to Java 8 also. Remember to update your CrashPlan management client to 4.8.0. The official website doesn’t yet advertise the 4.8.0 downloads but they can be found here:

    1. Gert Serneels

      Hi Patters,

      Everything worked fine with my 4.7.0, didn’t received an update yet.
      But after your package update, I can’t connect anymore!
      On my PC I now always get a system error, in the service.log this error occurs (see below).
      The authorized services don’t work anymore…



      [10.03.16 15:46:35.238 INFO 10866_AUTH-2 p42.service.ClientServiceManager] CSM:: Starting authorized services.
      [10.03.16 15:46:35.258 ERROR 10866_AUTH-2 backup42.service.peer.Authorizer] AUTH:: Failed to authorize, authorized services failed to start., java.lang.IllegalStateException: Failed to start authorized services.
      STACKTRACE:: java.lang.IllegalStateException: Failed to start authorized services.
      at com.backup42.service.ClientServiceManager.authorize(
      at com.backup42.service.CPService.authorizeServiceManager(
      at com.backup42.service.peer.Authorizer.doWork(
      Caused by: java.lang.IllegalStateException: Expected to be healthy after starting. The following services are not running: {FAILED=[AuthorizedStorageService [FAILED]]}
      at com.backup42.service.ClientServiceManager.authorize(
      … 4 more

      [10.03.16 15:46:35.259 INFO 10866_AUTH-2 backup42.service.peer.Authorizer] AUTH:: Error = CPErrors.Global.SYSTEM : []
      [10.03.16 15:46:35.263 INFO 10866_AUTH-2 backup42.service.peer.Authorizer] AUTH:: Send login response to the UI. LoginResponseMessage@12732768[ session=762951885109995037, errors=[CPErrors.Global.SYSTEM : []] ]{}
      [10.03.16 15:46:35.263 INFO 10866_AUTH-2 backup42.service.ui.UIController] UserActionResponse: LoginResponseMessage@12732768[ session=762951885109995037, errors=[CPErrors.Global.SYSTEM : []] ]{}
      [10.03.16 15:46:35.263 INFO 10866_AUTH-2 backup42.service.peer.Authorizer] AUTH:: *** END *** Failed after 25sec

      1. patters Post author

        Perhaps you need to stay on 4.7.0 until your CrashPlan account has been updated to 4.8.0. You can get the old package here:
        To manually upgrade to that version you can edit the version number in the file /var/packages/CrashPlan/INFO to a lower number first. Or if you’re not familiar with how to do that, just uninstall and reinstall manually from the spk. You will have to wait while it re-scans your entire backup set though.

      2. shashachu

        Gert @ patters – This is how far I’ve gotten, although this was from a manual install, and not from the updated packages. The AuthorizedStorageService won’t run because there’s an so file that it can’t find. It’s called libc42 something, so it seems to be a library built by CrashPlan. The file is there along side the other so files so it seems like it’s not compiled for ARM. It seems that the latest update will work if you have stored credentials, but if you’ve uninstalled or logged out, I haven’t been able to get it to work. Any ideas?

      3. patters Post author

        I completely wiped and reinstalled and it worked fine on mine (Intel i686). So must be an ARM/PowerPC lib that’s needed. Do you have the error message?
        If it’s then I doubt we can do anything, since I’m guessing c42 stands for Code42 (so it will be proprietary).

      4. Marten

        FWIW, I have not been able to use Crashplan on Synology for ages, because somehow the ‘on device Java JRE’ was installed, but didn’t work (apparently.. I had no other indications, and the crashplan binary DID start). The moment I took the effort to download java from Oracle is the moment things started actually working again.


      5. Per


        I get the same stack trace. Looks to be a non-compiled for arm…

        Oct 03, 2016 5:48:51 PM$Service Listener failed
        SEVERE: Service AuthorizedStorageService [FAILED] has failed in the STARTING sta te.
        java.lang.UnsatisfiedLinkError: Unable to load library ‘c42archive’: Native libr ary (linux-arm/ not found in resource path ([file:/volume1/@app store/CrashPlan/lib/com.backup42.desktop.jar, file:/volume1/@appstore/CrashPlan/ lang/])

        Will this mean that we are basically toast on DS715 (or other arm versions)?

      6. shashachu

        Yeah, looking like it. It’s unfortunate because it wasn’t even something I was thinking about when choosing a NAS. I guess that’s what you risk when using an unsupported setup. Patters, thank you for fighting the good fight thus far and providing this incredible package for free. Looks like it’s time to either choose a different backup solution or choose a different Synology model. For reference, which model do you use?

      7. patters Post author

        I have a DS214Play. I’m getting mighty pissed off with Synology still failing to release the DSM 6.0 GPL sources a whole year later, which is preventing me from building a more modern FFmpeg for the Serviio package. I’d be inclined to recommend buying from a company that isn’t carrying out large scale software theft, and one that actually cares about development on its platform. Have a look at this – they’re brazen, and the mods on their forum have deleted posts I’ve made about this:

      8. Per

        Just chatted with a support person. They of course couldn’t confirm that they dropped ARM support, but he gave me the standard requirements page and it lists only “1 GHz x86-64 CPU”.

        Looks like it’s time to switch from a DS715 to a DS216+II then. Any thoughts on that?


      9. Martin Hammer

        Yup. Also have this in my log. Time to switch from ARM to Intel or switch backup provider.

        ‘c42archive’:Oct 03, 2016 7:56:07 PM$ServiceListener failed
        SEVERE: Service AuthorizedStorageService [FAILED] has failed in the STARTING state.
        java.lang.UnsatisfiedLinkError: Unable to load library ‘c42archive’: Native library (linux-arm/ not found in resource path

      10. jerome

        Super-bummed to hear about the “” issue in ARM. I’m on a ReadyNAS RN204, which is also ARM-based and the latest 4.8.0 push really broke things. Normally, in the past, it was just pointing to the system Java that needed to occur to get things working again after botched-upgrades. Now it looks like they’ve added another dependency that has permanently broken ARM-based platforms (I would assume the same for RPI), which is really unfortunate. I wish they would reconsider their support for ARM as I think the use case for it is pretty broad…

    2. aadhoc78

      Upgraded. Won’t start.
      (BTW, thanks patters)

      I just performed the upgrade. Mid stream it wanted jre-8u101-linux-x64.tar.gz, so I put it in place, and continued again. No more complaints from upgrade in package manager. Looks like JAVACOMMON might not be set, but don’t know where java8 is or proper place for setting JAVACOMMON.


      ash-4.3# /var/packages/CrashPlan/scripts/ start
      Starting CrashPlan …

      ash-4.3# cat /var/packages/CrashPlan/target/log/engine_error.log
      /var/packages/CrashPlan/scripts/ line 189: /bin/java: No such file or directory

      ash-4.3# ls /volume1/@appstore
      AntiVirus CrashPlan HyperBackup HyperBackupVault Java7 PhotoStation PHP5.6 StorageAnalyzer TextEditor VideoStation VPNCenter

      ash-4.3# tail history.log.0
      I 09/29/16 11:34AM Download of upgrade complete – version 1435813200480.
      I 09/29/16 11:34AM Installing upgrade – version 1435813200480
      I 09/29/16 11:34AM Upgrade installed – version 1435813200480
      I 09/29/16 11:34AM CrashPlan stopped, version 4.7.0, GUID 674890120581087490
      I 10/03/16 09:32AM Synology Package Center updated CrashPlan to version 4.8.0-0042

      1. bagupremier

        If i use jre-8u101-linux-x64.tar.gz, crashplan stop working, but if i use the java8 package from synology, it work fine.

      2. John

        I have a DS411+II with an Intel Atom D525 Dualcore (2C/4T) 1.8GHz x86 Processor.
        I removed my old Crashplan package and public share, then installed the new Crashplan package, i.e. fresh install.

        Dedicated installation of Java 8 fails and engine_error.log says:
        /var/packages/CrashPlan/scripts/ line 189: /bin/java: No such file or directory

        CrashPlan works with Default system Java version and a Java8 package, that reports:
        Java version: 1.8.0_101
        CLASSPATH: /var/packages/Java8/target/j2sdk-image/jre

        The fresh install required an adoption of the old backup, but was easy on my Windows PC:
        The “%programdata%\CrashPlan\.ui_info” file was updated with the Guid from “/var/lib/crashplan/.ui_info” and the IP of my NAS, CrashPlan was then started, performed login, adopted the old backup and a new login and it is now “Synchronizing block information” which will take some time.

        All in all a very smooth installation.
        Thank you very much patters!

        A donation is on it’s way.
        It is my second, but I am happy that you keep this package up-to-date.

      3. aadhoc78

        Ok, I got mine to work. Mine wasn’t finding “jre” in the jre-syno directory, so JRE_PATH was empty.
        (BTW, I used the recommended file /volume1/public/jre-8u101-linux-x64.tar.gz)

        I added three lines to: /var/packages/CrashPlan/scripts/
        #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`”

        # vvv – aadhoc78 added
        if [ -z $JRE_PATH ]; then
        # ^^^ – aadhoc78 added

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

        (Note: I also had to tweak my CrashPlan client properties in the normal ways after upgrading it.)

      4. patters Post author

        Thanks – I’ve freshened the package with that fix.
        Also removed support for all architectures other than Intel :(

      1. patters Post author

        Same URLs but replace CrashPlan with CrashPlanPRO (case sensitive I think). Replace it in both the filename and the folder path. Likewise for CrashPlanPROe.

    3. Singularity


      Installed new package with Java Manager and Oracle Java 8 on my 412+ and the world was right! Working great! Big thanks again Patters, you rule!

  34. blue

    Thanks Patters! Saw the update 4.8.0-0042 now available. Uninstalled the older version, and installed the new one. Getting this, any ideas?

    [10.03.16 08:54:31.752 ERROR main com.backup42.service.CPService] Error starting up, com.code42.exception.DebugRuntimeException: Unable to persist ServiceModel, modelFilename=conf/service.model, byteCount=null
    STACKTRACE:: com.code42.exception.DebugRuntimeException: Unable to persist ServiceModel, modelFilename=conf/service.model, byteCount=null
    at com.backup42.service.CPService.loadModel(
    at com.backup42.service.CPService.start(
    at com.backup42.service.CPService.main(
    Caused by: java.lang.SecurityException: Invalid signature file digest for Manifest main attributes
    at java.util.jar.JarVerifier.processEntry(

    Using the Oracle java dedicated to crashplan:
    /var/packages/CrashPlan/target/jre-syno/linux_arm_sflt/jre/bin/java -version
    java version “1.8.0_101”
    Java(TM) SE Embedded Runtime Environment (build 1.8.0_101-b13, headless)
    Java HotSpot(TM) Embedded Client VM (build 25.101-b13, mixed mode)

  35. m rombout

    I 10/03/16 05:46PM CrashPlan started, version 4.8.0, GUID XXXXXXXXXXXXX
    I 10/03/16 05:48PM Back-up gepland om altijd te lopen
    I 10/03/16 05:48PM [DS1513 Backup] Scannen op bestanden om een back-up van te maken
    I 10/03/16 05:56PM [DS1513 Backup] Scannen op bestanden voltooid binnen 8 minuten: 204.607 bestanden (470,00GB) gevonden

    the procedure from Patters works on my DS! Great

  36. Martin


    Installed 4.8.0 and it says it is running. But when I try and connect the 4.8.0 client it says
    system error: if problem persists re-install crashplan.

    And the following is outputted into the engine_error.log.

    Oct 03, 2016 5:40:07 PM$ServiceListener failed
    SEVERE: Service AuthorizedStorageService [FAILED] has failed in the STARTING state.
    java.lang.UnsatisfiedLinkError: Native library (com/sun/jna/linux-ppc/ not found in resource path ([file:/volume1/@appstore/CrashPlan/lib/com.backup42.desktop.jar, file:/volume1/@appstore/CrashPlan/lang/])
    at com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(
    at com.sun.jna.Native.loadNativeDispatchLibrary(
    at com.sun.jna.Native.(
    at com.code42.archive.jna.Archive42JNA.(
    at com.code42.archive.jna.ArchiveComparator.getV2VirtualTableComparator(
    at com.code42.archive.MetadataLevelDB.getLevelDBOptions(

    Exception in thread “AuthorizedStorageService STARTING” java.lang.UnsatisfiedLinkError: Native library (com/sun/jna/linux-ppc/ not found in resource path ([file:/volume1/@appstore/CrashPlan/lib/com.backup42.desktop.jar, file:/volume1/@appstore/CrashPlan/lang/])
    at com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(
    at com.sun.jna.Native.loadNativeDispatchLibrary(
    at com.sun.jna.Native.(
    at com.code42.archive.jna.Archive42JNA.(
    at com.code42.archive.jna.ArchiveComparator.getV2VirtualTableComparator(
    at com.code42.archive.MetadataLevelDB.getLevelDBOptions(

    1. patters Post author

      Odd that libjnidispatch would show an issue suddenly. That lib was extremely sensitive on PPC and despite being updated during CrashPlan’s evolution for the other platforms, the PPC one would only work with this one particular version of the library – and now no more. However, even if I was able to fix that PPC users like ARM users will still hit the brick wall of not having a native compile of the proprietary – so I’m afraid this version is the end of the road for non-Intel CPUs.

      1. Martin

        I guessed that would be the case. Thanks for all of your effort over the years. I was getting a new Intel box at Xmas anyway. So will be back on crashplan then if they don’t break something else.

  37. Jon Etkins

    Patters, it seems that something is not being set correctly on x64 systems if we select the option to use your java. I uninstalled and reinstalled, selecting the system default java (I have Syno’s own Java8 installed), and it’s working fine now. Thanks again for your continued support.

  38. danimal4326

    x86-64 user here. Just upgraded to 4.8. Had to modify the script

    change the line:
    JRE_PATH=”`find ${OPTDIR}/jre-syno/ -name jre`”
    JRE_PATH=”`find ${OPTDIR}/jre-syno/ -name jre-syno`”

    and CrashPlan should start.

    There is similar error in as well. Just modify install.vars:

  39. ewfzapp

    I have updated crashplan today (—->4.8.0-0042) & since then it does not work… do u have any idea please?
    thnak you for your work.

  40. Luca Palli

    2 weeks ago I intalles CrashPlan on my new DS716+II successfully!
    After the upgrade he stopped to work and I tried to reinstall without success.

    Today I founded the update on my Synology but after the update CP still not work, I removed it and reinstall but now it still not working and the logs are empty!

    Any idea how to solve it?

  41. Edo

    As usual after each update nothing works anymore. I uninstall/reinstall Crashplan, uninstall/reinstall java 8 (both default from Synology & from Oracle website) nothing works.

  42. Edo

    Update… I installed Java 8 from Synology (not the one Crashplan requests me from Oracle) and reinstalled Crashplan, now it works.

    1. Edo

      Finally it doesn’t work neither with the default Java 8 from Synology. It keeps stopping, I suspect because the default Java 8 in the Synology is 32 bit. So back to square one… :/

      1. Jon Etkins

        Have you checked your java heap size? In my experience, if it starts then stops, that’s usually the problem.

  43. Maikel

    Am I correct in thinking the package is not available anymore for my DS411? Crashplan had an issue with upgrading, so I decided to uninstall and reinstall the package, but I can’t find it anymore in the package center.

      1. Dimi

        I tried all sorts of things but couldn’t stop it from auto updating. I tried hosts file entries looting to local host I tried creating read only files with the same name as the 4.8 update but it kept auto updating… If anyone has an idea how to do this I would be very grateful!

      2. jerome

        Only other thing I can think of would be to create firewall rules? Not sure what the workflow is with upgrades and if they stop CP services, etc before attempting to contact the CP servers but that could be a headache too…

      3. TD

        Hi Patters, you have done an amazing job keeping the package going so far. Can’t thank you enough.

        I have a DS413 that has the e500v2 cpu (shows up as FREESCALE QorIQ P1022 in the control panel). Am I basically screwed now in that I can never run CrashPlan on this box as it auto upgrades and there is nothing I can do about this?

        I have uninstalled the 4.8.0 and manually installed your old 4.7.0 package (because it doesn’t show up anymore in package centre either). Is there anyway to block the upgrade from running?

      4. patters Post author

        Unfortunately no way to block. At some point (if not already) Code42 will migrate your backup archive on their servers forcing you to version 4.8.0.

      5. Singularity

        @Jerome try this (copied from above)
        (0) Stay calm.
        (1) Uninstall CrashPlan package
        (2) Reinstall CrashPlan package
        (3) ssh to your DS; cd /volume1/@appstore/CrashPlan/
        (4) mv upgrade upgrade.tmp
        (5) touch upgrade

      6. jerome

        @Singularity, maybe I’ll give it a shot but I’m actually on a Netgear ReadyNAS RN204 which is ARM-based. And from the looks and sounds of it, a reinstall isn’t going to resolve the dependency issue with the library CP included that is precompiled for x86. So I’d imagine things will still be broken after an attempted reinstall. I think several others have confirmed this with their ARM-base Synology NASes so I don’t think it would be any different or better in my case

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