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

  1. Jon Etkins

    Interesting that this update managed to get around the “touch upgrade” workaround that I, and I’m sure many others, had in place. But after following the instructions from aadhoc78, I’m back up and running again. Thanks!

  2. Wayne

    Hi all…

    I’m having a bad time trying to get the client to connect.

    The new ui_info is:

    So I put this in the client, with the NAS IP instead, but it will not connect. Am I missing something here?


      1. KentA

        I´ve done the same thing but the ui_info change after a while to a new value. How did you solve it?

  3. Tim G

    For some reason CrashPlan isn’t showing up int he community repo for me (DS212j). Thought it might the DSM version, so am now up to date on 5.2-5967 Update 2, didn’t work. Also uninstalled Java 7 and updated to 8. Still nothing. Compatibility issue?

    1. Tim G

      Whoops, did some more searching on the comment list. Think it’s a Marvell CPU in the DS212j, so I guess no more Crashplan support. So SOL on that one. Any reccomendations for CrashPlan type software for local PC backup to my Synology NAS?

  4. KentA

    I managed to solve it myself and here is how:
    I followed aadhoc78 & Wayne´s instructions but it wasn´t until I did a second time it started to work. I may have missed something the first time or didn´t waited long enough.

    When I tried to fix the .ui_info file also reading Wayne´s instruction on the Win 10 client adding the key from the NAS and change the IP to the NAS IP. Starting CP on the client GUI shows up as it is the NAS. Then I revert the IP back to again it starts connecting to the NAS, don´t ask me how it works. After a while the key in the clients .ui_info file has changed to a new value but still has connection and seems to work????

    I´ve now successfully made a new backup.

    Maybe this can help someone or anyone with more knowledge please teach me. I wonder if one needs to change the GUI id somewhere?

    Thanks to aadhoc78 & Wayne and others on this forum and of course patters,

  5. Pingback: How to prevent CrashPlan’s auto-upgrade process | CrashPlan Community Forum - Support & Assistance

  6. thezfunk

    When I try and run the command:
    cp /volume1/@appstore/CrashPlan/bin/cpio /bin/cpio
    I get permission denied and I am using the admin account.

      1. thezfunk

        I think you are right but for some reason my admin password is being denied as the root password.

      2. Brad J.

        Starting with DSM 6 (or maybe 6.1?), you need to use “sudo -i” and then type your password (assuming you are an admin). This will then give you a shell with root access.

  7. adam

    Has anyone seen this error before:

    [05.01.17 10:37:35.053 INFO DefaultGroup .code42.messaging.peer.PeerGroup] PG::DefaultGroup RemotePeer not allowed to connect, missing PbK. RemotePeer-[guid=XXX]; PeerConnectionState-[state=DISCONNECTED, mode=PRIVATE, currentAddressIndex=0, layer=2/2(Peer::NIO), connecting=2017-05-01T09:36:58:345, connected=2017-05-01T09:36:58:346, disconnected=2017-05-01T09:36:58:352, attempts=0, connectActivity=2017-05-01T09:36:58:352, keepAliveSent=0, minRetry=26120, reconnectable, location=, transportPbK=null, transportPbKRequestable=false]; Session-null

    Crashplan 4.8.2 (displaying in package centre as 4.8.0-0044) Running on a synology DS1813+ running DSM 6.1.1-15101

    It has been running fine up until the 4.8.2 update. I’ve tried most of the suggestions above, plus the usual steps that i’ve done previously after updates.

    I’ve also un-installed and re-installed crashplan, java 8 (synology version) etc. But nothing seems to be working. I can’t connect to it with the client on my desktop either (after updating the ui GUID/Port)

    Any help would be greatly appreciated


  8. hanvanvilsteren

    The bastards ;-) they changed the default listner port on the nas.
    Crashplan Listner is ast TCP 4247 now!
    In the past it was 4243 so you need to adjust the of your client also to this port and adjust the token ofcourse.

  9. hanvanvilsteren

    i have disabled ipv6 on my synology but it looks there goes something wrong :
    Thats i think it uses 4247 now.

    netstat -na | grep LISTEN | grep 42
    tcp 0 0* LISTEN
    tcp6 0 0 :::4242 :::* LISTEN
    tcp6 0 0 :::* LISTEN

  10. underlircs

    Anyone else’s Crashplan package fails to start after updating to DSM 6.1.1-15101?

    Installed version is 4.8.0-0044

    I’d hate to have to start re-uploading terabytes of data yet again…

  11. David

    Thanks for the help aadhoc78
    I had a bit of trouble getting it going, like a few others it just wouldn’t start at step 10.
    It finally worked with a separate install of JAVA 8, NOT with the dedicated java (which caused a java not found error in the start_stop shell)
    Anyway, off for some synching now!

  12. guy

    Has anyone else seen crashplan stopping on the latest release, It started with me as of about 28th April?
    I’ve tried re-installing Java and Crashplan and it doesn’t help. When I examine the log I can see that after installing Crashplan using patters installer, it runs for a few minutes, then there is then an automatic upgrade at which point it all stops. It won’t restart. I’m not sure what else to try. Does anyone have any ideas?

    The Crashplan log reads-
    Crashplan started version 4.8.0 GUID 718360883745667557
    Stopping Crashplan (this was me doing as per instructions for set up)
    Crashplan started version 4.8.0 GUID 718360883745667557
    Downloading new version of Crashplan
    Download of upgrade compelte – version 1436674800482
    Installing upgrade – version 1436674800482
    Upgrade installed – version 1436674800482
    Crashplan stopped, version 4.8.9, GUID 718360883745667557
    Synology extracting upgrade from /var/packages/Crashplan/target/upgrade/1436674800482_4

    and that’s it. Any attempts to re-start immediately stop again

    I am running java 1.8.0_121 which is the latest from patters install, although i note that Oracle now has a later version.
    The box is DS214play with Intel Atom CE5335 and DSM 6.1.1-1501 Update 1 (that DSM update arrived today and made no difference to the symptoms)

  13. Benjamin

    Try to install package on my DS412+ and it keep’s running till 2nd update: then I don’t get it back to life. Last Log Entry: Synology extracting upgrade from /var/packages/CrashPlan/target/upgrade/1436674800482_4.jar Any Idea how to get this excellent tool back to work?

  14. ZeusII

    OK, just did a quick fix and seems it worked. After doing this, CrashPlan was updated succesfully to 4.8.2 and started on first try on a DS713+ with DSM6.1.1!

    Just edit the “” from the spk package replacing all the references to “4.8.0” with “4.8.2” and “480” to “482” and then install it manually through package manager (without uninstalling the previous version). You might also have to edit the file “INFO” upping the “version” field.

    1. underlircs

      Can you elaborate on how you‘re accomplishing this for an existing install that won’t start after the latest update?

    2. B. Goodman

      Would you elaborate on your fix, please? I’m trying to find and coming up with nothing, even from a terminal session.

      1. B. Good

        This link got me back in business

        After following the instructions EXACTLY, CP started and started running. I did have to sign in, reenter my encryption key, and wait for things to sync again, but it all seems to be operational again.

        I noticed that several of my remote backup locations looked like they lost my backup set, but what appeared to be a new backup went to over 90 percent in about 15 minutes. So be patient!

      2. Shane

        What got me was the JAVAHASH. I had mine set to 4096 and looking at engine_error.log i saw:

        Invalid maximum heap size: -Xmx4096m
        The specified size exceeds the maximum representable size.
        Error: Could not create the Java Virtual Machine.
        Error: A fatal exception has occurred. Program will exit.

        So I chagned the heap size to 4095. Crashplan on my Synology started and is working.

      1. Kurt

        Go to and download crashplan4.8.0-merged-0044.spk ( or try this direct link: )

        This is just a tar file without the .tar extension. You can untar it (warning- it does not have its own subfolder so the contents will be placed in the current directory. I created a new directory and untarred the files into that) then edit the scripts/ file to replace 4.8.0 with 4.8.2 (3 occurrences) and “480” with “482” (1 occurrence)

        I also edited the INFO file to change the version to “4.8.2”

        Then I tarred up the files into a new SPK file with the command tar cvf ../crashplan4.8.2.spk *

        On the synology, in the Package Center, I clicked on “Manual Install” and chose my new spk file.

        I chose the default system Java (I had already updated it in the Package Manager) and it is now running just fine. Note I had also copied the cpio file from /var/packages/CrashPlan/target/bin to /bin during previous attempts to get this running

        Hope this helps other – thanks for the tip ZeusII !!


    3. KJL

      Thank you so much: this finally got my RS3617xs (running DSM 6.1.1-15101 Update 2) back up and running.

  15. Ethan

    I got the Java installed and the package will start. But when I stop and then try to restart it, it will fail to restart, or only run for a few seconds. Any ideas?

    1. chaoskcw

      Any progress on resolving the latest update yet? Been not working for a few weeks now.

  16. Anders

    Have any of you tried iDrive? I have been testing it,seems to work ok. But only runs on schedule.

    tested the Beta Synology C2, and it made the NAS so slow I hade to remove it…

    But now CP has stopped again.

  17. Doxuni

    Just update to latest DSM 6.1.1-15101 Update 1. Crashplan was stopped and can’t be started again. It work months before this update. Anyone having same issue?

  18. Louie Larson

    This is what I did to get CrashPlan back up and running under DSM 6 after the attempted 4.8.2 upgrade, without having to uninstall and reinstall CrashPlan and Java8.

    SSH to Synology server, then run the following:

    sudo -i
    cd /var/packages/CrashPlan/target
    mkdir old_ver
    mv * old_ver/
    gunzip < old_ver/upgrade.cpi | cpio -im
    cp -p old_ver/bin/run.conf bin/
    cp -p old_ver/bin/CrashPlanEngine bin/
    cp -p old_ver/bin/ bin/
    cp -p old_ver/conf/my.service.xml conf/
    cp -p old_ver/conf/service.model conf/
    cp -p old_ver/syno_package.vars .
    cp -p old_ver/install.vars .
    chown -R root:root *

    Start CrashPlan from DSM.

    I then saw this in the logs/service.log.0 file:
    [05.05.17 20:11:16.003 WARN e-listen-1-1 .handler.BasePipelineInitializer] SABRE::Exception initializing channel:, java.lang.IllegalArgumentException: Cannot support TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA with currently installed providers
    STACKTRACE:: java.lang.IllegalArgumentException: Cannot support TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA with currently installed providers

    Stop CrashPlan from DSM.

    Open Java8 in package center, which only had OpenJDK installed, which has limited TLS/SSL protocols.
    Click Upgrade Java
    Follow the instructions to download, select, and install the latest jdk-8u131-linux-x64.tar.gz file

    Start CrashPlan from DSM.

    Then I saw this in the log file: RemotePeer not allowed to connect, missing PbK

    Connected my CrashPlan UI to the server, logged in, and then everything started working.

  19. altair

    Ethan, I have the same problem and I think I tried everything. Impossible to run it again.

  20. Pingback: Updating Crashplan on the Synology – The Infosec Noob

  21. John

    I recently uninstalled/reinstalled crashplan 4.7 on my DS410 and Desktop. It is all configured and communicating fine as far as I can tell. However, it would appear that my backup sets and file selections are missing. Do I really have to re-select everything? Any advice is appreciated.

  22. Nicholas Riley

    Your site’s certificate appears to have expired in late April. Could you renew it?

    Thanks for providing these packages!

  23. Lared

    I am having the same issue as Ethan. The package installs but stops shortly after installation and will not restart. I have stopped the service immediately after install and then started it and it will start but it fails to start after a few minutes of running for the first time. The log shows that it’s checking for an update, and a while later downloads the update from Crashplan and that’s as far as it goes. Has anyone found a fix or workaround to this?

  24. DJ


    I’ve had it with Crashplan on my Synology.
    With every update I have to troubleshoot so I want to:
    Move _from_ Crashplan running on my Synology _TO_ Crashplan running on a Windows computer.

    QUESTION: How can I do that without having to re-upload every file that’s already in the Crashplan Datacenter?

    Thank you!

    1. badbob001

      I haven’t tried going from linux (synology) to windows (scary), but I did successfully go from linux to linux. I had some old computer parts and basically threw them into a cardboard box, installed ubuntu from a usb flash, made a nfs mount to the synology volume using the exact same path as the original, installed crashplan, and it doesn’t suspect any change (did not have to adopt).

      I was limited to 4GB ram in my old synology but now I have 16GB in my linux box and so no more out of memory errors. I suspect synchronization is slower since it’s going over the LAN instead of SATA, but once that’s done, you’re back to being limited by Crashplan’s super slow uploads.

      1. Monte

        I’ve tried to get crashplan running til I’m blue in the face. start stop uninstall reinstall….seems crazy. I’ve unistalled the Java version and reinstalled and have followed everyones methods on here. Nothing works. I’ve updated the .ui_info on my iMac . My crashplan on the package center is 4.8.0 -0044. I saw someone mention an newer version I think I saw 4.8.2. Where do you get that? Any help on this would be greatly appreciated. I’m 18 days without backup and not sure what to do. Would uninstalling completely from my iMac and reinstalling everything from scratch be the fix? Please Please help. I’m a novice and have learned a lot from this website. One thing I’ve never been able to find is all the cpio and jar files everyone is referencing. Maybe I don’t have permission on my imac to look at those, but I can’t find them to even try to edit them. Any help on that would be very helpful as well because I know there must be some mac users out ther that are doing this crazy stuff…….Patters… us!!!!! Please!!!!!
        Thank to everyone!!!!!

      2. Anders

        Also getting tired of fixing all the time. Thinking of switching to Office 365 and get 1TB on OneDrive and try to get that to work, just figure out how to sync folders outside the onedrive folder…

      3. altair

        Just follows the explanations of Zeus. To extract crashplan4.8.0-merged-0044.spk don’t use winrar but pkzip. After have replaced all the references to “4.8.0” with “4.8.2” and “480” to “482” in the files, compress the files in *.tar (and not another !!), then rename it to *.spk. For users with 415+ you must add “avoton” to the line “arch=”x86 bromolow cedarview evansport avoton braswell broadwell grantley ” (like this : arch=”x86 bromolow cedarview evansport avoton braswell broadwell grantley avoton”) in the INFO file. Without this, it impossible to manually install the spk file. For users which have made a lot of install/uninstall don’t forget to verify the LAN adress in the files on NAS (remove the hash symbol and set to the IP address of your NAS, e.g.:serviceHost= and to redirect to a correct path Java in the file /var/packages/CrashPlan/target/install.vars (like this : JAVACOMMON=/volume1/@appstore/Java8/j2sdk-image/jre/bin/java)

      4. Marc

        Did you read the other messages ? Reinstalling is not enough. You also have to do this :
        sudo cp /volume1/@appstore/CrashPlan/bin/cpio /bin/cpio
        Personally I didn’t get much problem to get CP back running. Please note that I am using the Synology Java 8 package. I also had to increase the heap size of Java because I have a huge quantity of data to backup.
        Did you check the log ? It gives you some clue also about what is wrong with you system.

    2. Marc

      You just “adopt” the old computer (the NAS) in your new Windows CrashPlan. Very easy and we’ll explained on the CrashPlan website.

  25. Carlton Bale

    I’m frustrated with how often Synology breaks this method when something is updated. A lot of Synology users are switching to the Docker version, which runs crash plan inside a supported container, eliminating the compatibility issues we’re seeing with the native Sonology plugin method. Search the web for “run crashplan docker synology” for more details.

  26. Pingback: How to: Synology Backups with CrashPlan | 0x2142

  27. Matthew

    I have CrashPlan running on two Synology DS1515+ NAS drives located in different locations on different networks for backup redundancy. I followed the steps above and now both CrashPlan instances are back up and running again. One is working great, the other NAS only backs up local machines on the same network, but no longer allows connections for computers outside it’s local network? The only weird thing that I see is now when I setup my headless client on this NAS it has the port set to 4259 instead of the standard 4243? Every time I try to change the port back to 4243 using the headless client it says Port is already in use and does not save the change? Any help would be appreciated… Everything has been working great until this latest update/bump in the road…

    1. Matthew

      Correction, I meant to say port 4242 not 4243… Every time I change the port to 4242 in my headless client it picks a random port like 4265, 4244, 4251… I cant get it to accept port 4242???

  28. Brad

    I just did the update and got things working again on two DS412+ boxes.

    Here are the steps, shamelessly cobbled together from suggestions from several other people.
    The key difference here is that you don’t have to uninstall and reinstall using these steps using a trick Patters posted a while ago (basically you trick the Package Manager into thinking you have an older version and then you can do an update even though you have the latest version). This means you don’t have to update your uuid in the client you use to connect in and don’t ever have to adopt, etc..

    4.8.2 Update steps:

    1) SSH in and use “sudo -i” to get root. Then “cp /volume1/@appstore/CrashPlan/bin/cpio /bin/cpio”
    2) “vi /var/packages/CrashPlan/INFO”. Lower package version number by one in that file, save and exit.
    3) Go to package center. It should let you update, or, should do so after a refresh.
    4) DSM CrashPlan Action->Run
    5) “tail -f /var/packages/CrashPlan/target/log/service.log.0” in the SSH window
    (Leave that tail running).
    6) Wait ~1min for: Waiting 60 seconds for upgrade script to shutdown service…
    7) Wait ~1min for the following in SSH/tail: Service stopped normally
    8) DSM CrashPlan Action->Run, receive: “Failed to run the package service”
    9) Wait ~1min for: Enough time to do a good luck dance.
    10) DSM CrashPlan Action->Run
    11) Watch tail produce lots of output (including various warnings)
    12) Reconnect CrashPlan client. You may need to re-enter your encryption key to start the backup process again.
    13) Let scan for long time.

    Hope this saves somebody some time!

    1. Austin

      THANK YOU! After three weeks of not being able to get CrashPlan back up and running on my 1512+, these instructions finally did the trick.

      Only difference was that instead of 1 minute to hit the “Waiting 60 seconds for upgrade script to shutdown service…” message, it took nearly 15 minutes. It was trying to do some kind of automated upgrade and spit out dozens of errors along the way…but it got there eventually.

      For those of you who might be searching this page for keywords, some of the errors it hit repeatedly were “PG::DefaultGroup RemotePeer not allowed to connect, missing PbK.” “Closing connection to unknown peer, peerId=…” “ClientIdentifierAgent: connected() – Error marking the session as authorized. null, com.code42.messaging.MessagingClosedException”

      After CP was up and running for the final time, I also had to repeat the token copying steps to reconnect my client…

      – (On Synology) echo `cat /var/lib/crashplan/.ui_info`
      – Put the token and your Synology IP address into “/Library/Application Support/CrashPlan/.ui_info” on your Mac (or the equivalent on Windows)

      I really appreciate patters’ package! But every few updates it inevitably breaks, requiring some voodoo to get it up and running again. Pouring through comments here every time is time consuming and not always fruitful.

      I wish I could switch to another backup service, but my 4TB DNG archive is too much to reupload now that Comcast is capping me at 1TB total every month. I hit half that just from normal Internet use, so that’d be at least 8 months to reupload to another service. >:| If anyone has any suggestions that wouldn’t break the bank, I’m all ears.

    2. bgmess

      I am running Patter’s package on my Synology. I have been successfully backing up to crashplan server for more than a year.
      I recently updated to 4.8.0-0044. I install following the instructions on pcloadletter page.
      Patter’s crashplan installs and starts running. I stop the package according to the instructions….but when I try to restart it, it fails – just says stopped.
      I can’t seem to figure out why it is not restarting. The log says it installed correctly.
      I am fairly new to Linux and need some help.
      Running DSM 6.1.1-15101 Update 4, DSM 6.1.1-15101 Update 4
      I have Patters Java 1.8.0_121-0043 installed.

      What am I missing?



    3. tomwhelan

      Thanks, Brad – this seems to have worked, the client is synchronizing now.
      For the benefit of others, here are a few things that tricked me:
      – Crashplan updated itself to 4.8.2, and it was running – but the log, inspected with tail
      (tail -f /var/packages/CrashPlan/target/log/service.log.0) showed connection errors and timeouts.
      – The /var/packages/CrashPlan/INFO file was still at version 4.8.044
      – The client (still at version 4.8.0) started up normally, showed a backup underway, but exited without an error. The token in .ui-info was correct.
      I recovered by:
      – Uninstalling 4.8.0 client, installing 4.8.2 client (token was still OK)
      – Using Brad’s procedure with slight tweaks to reinstall the 4.8.2 package: update cpio, change package version to 4.7.044 in INFO file, update in Package Center, it started running, stop in DSM, start again, start tail process, observe shutdown in log, start in DSM, see “failed to run” message, start again, do happy dance.

      1. Shane

        I have two of these (one home and one work). Got my home one going but the work one is still not going. I’ve tried the original fix to this a bunch of times and then the updated notes but I am unable to get CP to backup. The app does not stop on the Synology and I am not able to connect using the CP client on windows.

        Any more suggestions?

      2. tomwhelan

        Afer the synchronization completed, I had to do more to prevent the connection errors I saw earlier. I edited a file:
        sudo vi /var/packages/CrashPlan/target/syno_package.vars
        increasing the value of the Java heap USR_MAX_HEAP in it. I also compacted my archive at the Crashplan site (that may not have been necessary). After I did both, backups completed.

    4. bertxl

      Seems to work for me. I skipped step 2 (since the upgrade did not really occur yet). The real issue seems to be the missing cpio.
      Thanks for the help!

  29. Brian

    The instructions above didn’t quite work for me. I had been using a dedicated jre at step 11, I was getting an error in engine_error.log that said it couldn’t find /bin/java. I tried linking to the embedded verison but that didn’t work.

    I uninstalled everything, then installed Patter’s Java8 package and then CP again from scratch. I tailed the logs as described above and was able to see it go through the upgrade process. After a few starts and stops, it came back up as 4.8.2 and then i was off to the races. Of course I had to re-fetch the ui_info id but it seems I’m back in business now.

  30. Brian Mess

    I have been running Patter’s Crashplan, but recently it stopped backing to the Crashplan server. I uninstalled and reinstalled Java (jre-8U121-linux-x64.tar.gz) in the public folder. Reinstalled Patter’s Crashplan. It started fine. I stopped it as instructed, but now it won’t restart. Running on DSM 6.1.1-15101 Update 3 with INTEL Atom C2538. It used to work, but I can’t figure out why it is not working now. Any ideas?

  31. aadhoc78

    I’ve got these directories accumulating over the years:
    crashplan_1, crashplan_2, … crashplan_32

    So many now they are hard to ignore. I haven’t looked into it.
    Are they created each update? Safe to delete any/all? …

  32. Ajay

    is it still possible to install crashplan 4.7 on DS212J arm? I download and tried to install and it does not create .ui_info in crashplan directory. the directory is blank. what am I missing? thanks for your help.

  33. Rich

    Question1: Can the typical setup be modified to backup both a volume1 _and_ a volume2? Or do I need to config some things differently?

    Question2: It looks like the max heap that Java can be set to is 4095M. Is this correct?

  34. spyrule

    Seems as though is offline (Internal error 500) on June 14, 2017 ?

      1. spyrule

        It seems to be very intermittent. It loaded once, and then stopped loading again. I checked my firewall, and I’m getting a server 500 error when loading, so its not my firewall. This is in Canada.

  35. Yves Soers

    4.8.3 released. One server succesfully upgraded by himself, other 2 failed and Crashplan doesn’t start anymore.

    1. Martin

      Upgrade failed for me. Used the same instruction @Martin posted a month ago.

      Seems to have been a lack of cpio again.

      1. copied cpio to /usr/bin
      2. Uninstalled
      3. Reinstalled
      4. Restarted
      4. Connected client and logged in

    2. Excalibr79

      Mine seemingly upgraded successfully but it would keep restarting every few minutes. I ended up doing the same set of tasks that @aadhoc78 posted on April 28, 2017 when 4.8.2 was released:

      1) SSH into the Synology (I used PuTTY), type (only stuff within “”):
      “sudo cp /volume1/@appstore/CrashPlan/bin/cpio /bin/cpio”
      2) Uninstall CrashPlan from DSM Package Center
      3) Install CrashPlan from DSM Package Center (Used System Java Installation. Do not run after install)
      4) DSM Package Center -> CrashPlan -> Action -> Run
      5) In PuTTY, type (only stuff within “”):
      “tail -f /var/packages/CrashPlan/target/log/service.log.0”
      (Leave that tail running)
      6) Wait ~1min for: Waiting 60 seconds for upgrade script to shutdown service…
      7) Wait ~1min for: Service stopped normally
      8) DSM Package Center -> CrashPlan -> Action -> Run, receive: “Failed to run the package service”
      9) Wait ~1min for: Enough time to do a good luck dance.
      10) DSM Package Center -> CrashPlan -> Action -> Run
      11) Watch tail produce lots of output (including various warnings)
      12) Fix CrashPlan UI token:
      12a) Edit the syno_package.vars to change the Java heap size:
      13) Reconnect CrashPlan
      Start CrashPlan UI
      client: Existing Account
      Provide archive key, save
      Let scan for long time to re-synchronize.

      I’m currently at the “Let scan for long time to re-synchronize” part but so far it hasn’t restarted.

    3. desiredtrash

      same here my DS1515+ tried to upgrade to 1436674800483_15.jar and now it crashes out wont load. please help.

      1. Hal Sandick

        okay. copied the cpio file over, uninstalled, reinstalled and then restarted a few times and now working. sigh!

  36. Yoz

    I have tried to install Crashplan on a DS216play (DSM 6.1.2). It’s ok for Java8 install, but when i added “” on packages sources, i am unable to see crashplan app. When i have tried to manually install the “crashplan4.8.0-merged-0044.spk”, it says me that the package is not supported on the platform of Diskstation. But i have successfully installed the “crashplan4.7.0-merged-0041.spk” found on old directory.

    Thanks in advance for help.


  37. Hal Sandick


    First, thanks for reaching out.

    I had set it a while ago and didn’t check before I uninstalled. It was not set when I looked at just now. I assume the conf file was deleted and a default file created when I reinstalled the software. So it’s was working without me setting it.


    1. Brian Mess


      I am having the same issue….Patter’s Crashplan starts and shortly after stops. I don’t know how to copy the CPIO file over. Can you help with some instructions on that? I don’t do much in Linux and could use some help.

      Should I try resetting my USR_MAX_HEAP setting in syno_package.vars? If so, how would I do this. Sorry to be a newb on these…..and thanks for your help.


  38. Julian

    My NAS downloaded an update as you can see:

    I 04/24/17 07:34PM Downloading a new version of CrashPlan.
    I 04/24/17 07:38PM Download of upgrade complete – version 1436674800482.
    I 04/24/17 07:38PM Installing upgrade – version 1436674800482
    I 04/24/17 07:38PM Upgrade installed – version 1436674800482
    I 04/24/17 07:39PM CrashPlan stopped, version 4.8.0, GUID 628561899896177057
    I 06/04/17 01:07PM Synology extracting upgrade from /var/packages/CrashPlan/target/upgrade/1436674800482_4.jar

    Since then, It hasn’t run. Can anyone tell me what I need to do? I really don’t want to have to reinstall because I’m no longer running CrashPlan on any PC’s

    1. Julian

      I trawled through all the various posts to get an answer of sorts. It seems like the unpack of upgrade.cpi failed so that none of the libraries or java files were present and for some reason the update wouldn’t retry.

      I manually unpacked it and manually copied cpio file to /bin (not sure whether that was actually needed).

      I also switched to the Syno Java 8 package and increased the heap slightly since I’d upgraded my RAM a while back to 2GB, so running heap at 1.8GB for now.

      Then restarted the package and it worked. It immediately ran the upgrade to 4.8.3 (from 4.8.0) which worked fine.

      One weird thing, at the moment, the package centre shows that CP is NOT running – but it absolutely is running! I’m connected to the CP service and backups are running. I’ll see if this clears up after a reboot but I don’t want to do that until the current backup has finished.

  39. Martin

    4.8.3 arrived here and failed to upgrade due to missing cpio. Copied it back to /usr/bin then done the uninstall/reinstall and all is well. Had to re add the heap size too.

    I’ve now added to a scheduled task (that copies the file to a more useful location) to copy cpio daily as it’s obviously going AWOL, probably as part of a Synology update.

  40. Desiredtrash

    Just ended up uninstalled it and now running crashplan though synology docker… all up and running.


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