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.

CrashPlanPRO-Windows

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:
    Community-packages
    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 (0.0.0.0 means the server is listening for connections on all interfaces) e.g.:
    4243,9ac9b642-ba26-4578-b705-124c6efc920b,0.0.0.0
    port,--------------token-----------------,binding

    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:
    4243,9ac9b642-ba26-4578-b705-124c6efc920b,192.168.1.100
    assuming that the Synology NAS has the IP 192.168.1.100
    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/ui.properties” (Mac OS X installed for all users)
    “~/Library/Application Support/CrashPlan/ui.properties” (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!
 

Notes

  • 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:
    /var/packages/CrashPlan/target/log/engine_output.log
    /var/packages/CrashPlan/target/log/engine_error.log
    /var/packages/CrashPlan/target/log/app.log
  • 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.

installer.sh

#!/bin/sh

#--------CRASHPLAN installer script
#--------package maintained at pcloadletter.co.uk


DOWNLOAD_PATH="http://download2.code42.com/installs/linux/install/${SYNOPKG_PKGNAME}"
CP_EXTRACTED_FOLDER="crashplan-install"
OLD_JNA_NEEDED="false"
[ "${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
  CP_EXTRACTED_FOLDER="${SYNOPKG_PKGNAME}-install"
  OLD_JNA_NEEDED="true"
  [ "${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="3.6.1.4"
  [ "${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"
  DOWNLOAD_FILE="CrashPlanPROe_${CPPROE_VER}_Linux.tgz"
fi
DOWNLOAD_URL="${DOWNLOAD_PATH}/${DOWNLOAD_FILE}"
CPI_FILE="${SYNOPKG_PKGNAME}_*.cpi"
OPTDIR="${SYNOPKG_PKGDEST}"
VARS_FILE="${OPTDIR}/install.vars"
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"
NATIVE_BINS_URL="http://packages.pcloadletter.co.uk/downloads/crashplan-native-${SYNO_CPU_ARCH}.tar.xz"   
NATIVE_BINS_FILE="`echo ${NATIVE_BINS_URL} | sed -r "s%^.*/(.*)%\1%"`"
OLD_JNA_URL="http://packages.pcloadletter.co.uk/downloads/crashplan-native-old-${SYNO_CPU_ARCH}.tar.xz"   
OLD_JNA_FILE="`echo ${OLD_JNA_URL} | sed -r "s%^.*/(.*)%\1%"`"
INSTALL_FILES="${DOWNLOAD_URL} ${NATIVE_BINS_URL}"
[ "${OLD_JNA_NEEDED}" == "true" ] && INSTALL_FILES="${INSTALL_FILES} ${OLD_JNA_URL}"
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"
LOG_FILE="${SYNOPKG_PKGDEST}/log/history.log.0"
UPGRADE_FILES="syno_package.vars conf/my.service.xml conf/service.login conf/service.model"
UPGRADE_FOLDERS="log cache"
PUBLIC_FOLDER="`synoshare --get public | sed -r "/Path/!d;s/^.*\[(.*)\].*$/\1/"`"
#dedicated JRE section
if [ "${WIZARD_JRE_CP}" == "true" ]; then
  DOWNLOAD_URL="http://tinyurl.com/javaembed"
  EXTRACTED_FOLDER="ejdk1.8.0_144"
  #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_BINARY="ejdk-8u144-linux-arm-sflt.tar.gz"
    JAVA_BUILD="ARMv5/ARMv6/ARMv7 Linux - SoftFP ABI, Little Endian 2"
  elif [ "${SYNO_CPU_ARCH}" == "armv7l" ]; then
    JAVA_BINARY="ejdk-8u144-linux-arm-sflt.tar.gz"
    JAVA_BUILD="ARMv5/ARMv6/ARMv7 Linux - SoftFP ABI, Little Endian 2"
  elif [ "${SYNO_CPU_ARCH}" == "armhf" ]; then
    JAVA_BINARY="ejdk-8u144-linux-armv6-vfp-hflt.tar.gz"
    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_BINARY="ejdk-8u6-fcs-b23-linux-ppc-e500v2-12_jun_2014.tar.gz"
    JAVA_BUILD="Power Architecture Linux - Headless - e500v2 with double-precision SPE Floating Point Unit"
    EXTRACTED_FOLDER="ejdk1.8.0_06"
    DOWNLOAD_URL="http://tinyurl.com/java8ppc"
  elif [ "${SYNO_CPU_ARCH}" == "i686" ]; then
    JAVA_BINARY="ejdk-8u144-linux-i586.tar.gz"
    JAVA_BUILD="x86 Linux Small Footprint - Headless"
  elif [ "${SYNO_CPU_ARCH}" == "x64" ]; then
    JAVA_BINARY="jre-8u144-linux-x64.tar.gz"
    JAVA_BUILD="Linux x64"
    EXTRACTED_FOLDER="jre1.8.0_144"
    DOWNLOAD_URL="http://tinyurl.com/java8x64"
  fi
fi
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
    )

    JAVA_BINARY_FOUND=
    [ -f ${PUBLIC_FOLDER}/${JAVA_BINARY}.tar.gz ] && JAVA_BINARY_FOUND=true
    [ -f ${PUBLIC_FOLDER}/${JAVA_BINARY}.tar ] && JAVA_BINARY_FOUND=true
    [ -f ${PUBLIC_FOLDER}/${JAVA_BINARY}.tar.tar ] && JAVA_BINARY_FOUND=true
    [ -f ${PUBLIC_FOLDER}/${JAVA_BINARY}.gz ] && 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
    fi
  else
    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 http://wp.me/pVshC-z5" >> $SYNOPKG_TEMP_LOGFILE
      exit 1
    fi

    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 http://wp.me/pVshC-z5" >> $SYNOPKG_TEMP_LOGFILE
      exit 1
    fi

    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
      fi
    fi
  fi
}


preinst ()
{
  pre_checks
  cd ${TEMP_FOLDER}
  for WGET_URL in ${INSTALL_FILES}
  do
    WGET_FILENAME="`echo ${WGET_URL} | sed -r "s%^.*/(.*)%\1%"`"
    [ -f ${TEMP_FOLDER}/${WGET_FILENAME} ] && rm ${TEMP_FOLDER}/${WGET_FILENAME}
    wget ${WGET_URL}
    if [[ $? != 0 ]]; then
      if [ -d ${PUBLIC_FOLDER} ] && [ -f ${PUBLIC_FOLDER}/${WGET_FILENAME} ]; then
        cp ${PUBLIC_FOLDER}/${WGET_FILENAME} ${TEMP_FOLDER}
      else     
        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
      fi
    fi
  done
 
  exit 0
}


postinst ()
{
  if [ "${WIZARD_JRE_CP}" == "true" ]; then
    #extract Java (Web browsers love to interfere with .tar.gz files)
    cd ${PUBLIC_FOLDER}
    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
      #Chrome
      tar xzf ${JAVA_BINARY}.gz
    elif [ -f ${JAVA_BINARY}.tar ]; then
      #Safari
      tar xf ${JAVA_BINARY}.tar
    elif [ -f ${JAVA_BINARY}.tar.tar ]; then
      #Internet Explorer
      tar xzf ${JAVA_BINARY}.tar.tar
    fi
    mv ${EXTRACTED_FOLDER} ${SYNOPKG_PKGDEST}/jre-syno
    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}
  fi
   
  #extract CPU-specific additional binaries
  mkdir ${SYNOPKG_PKGDEST}/bin
  cd ${SYNOPKG_PKGDEST}/bin
  tar xJf ${TEMP_FOLDER}/${NATIVE_BINS_FILE} && rm ${TEMP_FOLDER}/${NATIVE_BINS_FILE}
  [ "${OLD_JNA_NEEDED}" == "true" ] && tar xJf ${TEMP_FOLDER}/${OLD_JNA_FILE} && rm ${TEMP_FOLDER}/${OLD_JNA_FILE}

  #extract main archive
  cd ${TEMP_FOLDER}
  tar xzf ${TEMP_FOLDER}/${DOWNLOAD_FILE} && rm ${TEMP_FOLDER}/${DOWNLOAD_FILE} 
  
  #extract cpio archive
  cd ${SYNOPKG_PKGDEST}
  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 TARGETDIR=${SYNOPKG_PKGDEST} > ${VARS_FILE}
  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
  rm -r ${TEMP_FOLDER}/${CP_EXTRACTED_FOLDER}
  
  #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}/
    fi  
  fi

  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
  fi
  [ -e ${OPTDIR}/lib/libffi.so.5 ] && rm ${OPTDIR}/lib/libffi.so.5

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

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

 exit 0
}


preupgrade ()
{
  `dirname $0`/stop-start-status stop
  pre_checks
  #if identity exists back up config
  if [ -f /var/lib/crashplan/.identity ]; then
    mkdir -p ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig/conf
    for FILE_TO_MIGRATE in ${UPGRADE_FILES}; do
      if [ -f ${OPTDIR}/${FILE_TO_MIGRATE} ]; then
        cp ${OPTDIR}/${FILE_TO_MIGRATE} ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig/${FILE_TO_MIGRATE}
      fi
    done
    for FOLDER_TO_MIGRATE in ${UPGRADE_FOLDERS}; do
      if [ -d ${OPTDIR}/${FOLDER_TO_MIGRATE} ]; then
        mv ${OPTDIR}/${FOLDER_TO_MIGRATE} ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig
      fi
    done
  fi

  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
    for FILE_TO_MIGRATE in ${UPGRADE_FILES}; do
      if [ -f ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig/${FILE_TO_MIGRATE} ]; then
        mv ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig/${FILE_TO_MIGRATE} ${OPTDIR}/${FILE_TO_MIGRATE}
      fi
    done
    for FOLDER_TO_MIGRATE in ${UPGRADE_FOLDERS}; do
    if [ -d ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig/${FOLDER_TO_MIGRATE} ]; then
      mv ${SYNOPKG_PKGDEST}/../${SYNOPKG_PKGNAME}_data_mig/${FOLDER_TO_MIGRATE} ${OPTDIR}
    fi
    done
    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}
  fi
  
  exit 0
}
 

start-stop-status.sh

#!/bin/sh

#--------CRASHPLAN start-stop-status script
#--------package maintained at pcloadletter.co.uk


TEMP_FOLDER="`find / -maxdepth 2 -path '/volume?/@tmp' | head -n 1`"
MANIFEST_FOLDER="/`echo $TEMP_FOLDER | cut -f2 -d'/'`/crashplan" 
ENGINE_CFG="run.conf"
PKG_FOLDER="`dirname $0 | cut -f1-4 -d'/'`"
DNAME="`dirname $0 | cut -f4 -d'/'`"
OPTDIR="${PKG_FOLDER}/target"
PID_FILE="${OPTDIR}/${DNAME}.pid"
DLOG="${OPTDIR}/log/history.log.0"
CFG_PARAM="SRV_JAVA_OPTS"
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"`"
FULL_CP="${OPTDIR}/lib/com.backup42.desktop.jar:${OPTDIR}/lang"
source ${OPTDIR}/install.vars
source /etc/profile
source /root/.profile


start_daemon ()
{
  #check persistent variables from syno_package.vars
  USR_MAX_HEAP=0
  if [ -f ${OPTDIR}/syno_package.vars ]; then
    source ${OPTDIR}/syno_package.vars
  fi
  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/
  fi

  #fix up some of the binary paths and fix some command syntax for busybox 
  #moved this to start-stop-status.sh from installer.sh 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}"
    fi
  done

  #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/restartLinux.sh

  #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 chrisnelson.ca 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
  fi

  #updates may also overwrite our native binaries
  [ -e ${OPTDIR}/bin/libffi.so.5 ] && cp -f ${OPTDIR}/bin/libffi.so.5 ${OPTDIR}/lib/
  [ -e ${OPTDIR}/bin/libjtux.so ] && cp -f ${OPTDIR}/bin/libjtux.so ${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/
  fi

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

  #set appropriate Java max heap size
  RAM=$((`free | grep Mem: | sed -e "s/^ *Mem: *\([0-9]*\).*$/\1/"`/1024))
  if [ $RAM -le 128 ]; then
    JAVA_MAX_HEAP=80
  elif [ $RAM -le 256 ]; then
    JAVA_MAX_HEAP=192
  elif [ $RAM -le 512 ]; then
    JAVA_MAX_HEAP=384
  elif [ $RAM -le 1024 ]; then
    JAVA_MAX_HEAP=512
  elif [ $RAM -gt 1024 ]; then
    JAVA_MAX_HEAP=1024
  fi
  if [ $USR_MAX_HEAP -gt $JAVA_MAX_HEAP ]; then
    JAVA_MAX_HEAP=${USR_MAX_HEAP}
  fi   
  if [ $JAVA_MAX_HEAP -lt $JAVA_MIN_HEAP ]; then
    #can't have a max heap lower than min heap (ARM low RAM systems)
    $JAVA_MAX_HEAP=$JAVA_MIN_HEAP
  fi
  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}"
  fi

  #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 -Djava.io.tmpdir=${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/ui.properties 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
    fi

    #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 -Djava.net.preferIPv4Stack=true\"/" "${OPTDIR}/bin/${ENGINE_CFG}"
   else
    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}"
  fi

  #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
  #http://support.code42.com/Administrator/3.6_And_4.0/Troubleshooting/Too_Many_Open_Files
  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}
    fi
    [ -z ${LANG} ] && export LANG=en_US.utf8
    export CLASSPATH=.:${OPTDIR}/jre-syno/lib

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

  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
    fi
  else
    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
  fi
}

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
  fi
  #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
    return
  fi
  rm -f ${PID_FILE}
  return 1
}

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


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

  stop)
    if daemon_status; then
      echo Stopping ${DNAME} ...
      stop_daemon
      exit $?
    else
      echo ${DNAME} is not running
      exit 0
    fi
  ;;

  restart)
    stop_daemon
    start_daemon
    exit $?
  ;;

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

  log)
    echo "${DLOG}"
    exit 0
  ;;

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

esac
 

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": "3.6.1.4",
            "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
          }
        ]
      }
    ]
  }
]
 

Changelog:

  • 0031 Added TCP 4242 to the firewall services (computer to computer connections)
  • 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 libc42archive.so
  • 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 start-stop-status.sh
  • 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 chrisnelson.ca 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
    libjnidispatch.so taken from Debian JNA 3.2.7 package with dependency on newer libffi.so.6 (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 3.6.1.4 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), start-stop-status.sh 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 3.2.1.2)
  • 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 installer.sh to start-stop-status.sh 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 libffi.so 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 0.0.0.0 each startup
  • 003 fixed ownership of /volume1/crashplan folder
  • 002 updated to CrashPlan 3.2
  • 001 30/Jan/12 – intial public release
 
 
Advertisements

6,394 thoughts on “CrashPlan packages for Synology NAS

  1. Tom

    Crashplan stopped working for me about a week ago. Looking at engine_error.log it appears to be due to the wrong Java version (I installed with the dedicated java engine and also tried reinstalling using the system engine; same error both times).

    ‘Exception in thread “main” java.lang.UnsupportedClassVersionError: com/backup42/service/CPService : Unsupported major.minor version 52.0’

    I have Java8 and Java7 from Synology installed also. This is on a 214play

    Reply
  2. C

    Hello.

    In my case the 4.8.3 installs the official Linux JDK and overrides the embedded one; further more the memory options do not apply anymore.
    The only way I managed to upgrade was to let it upgrade, save the jars, uninstall, install patters version and the finally copy the saved jars.
    However I keep getting OOM despite setting 3GB memory like before. What’s weird is that even I set the Xms and Xmx the same value, I can see the new processes not allocating the whole 3GB.
    Is there anything I’m missing?

    Reply
  3. Mark OConnell

    Really struggling to get 4.8.0-044 running on Synology DS214 Play. Using dedicated Java. Downloaded that and renamed to filename required. Tries to start and then stops immediately. Any advice much appreciated.

    Reply
  4. spyrule

    Anybody else having a problem where it backs up successfully, but then never picks up and future changes to any files on the NAS, and only after editing the backup list, does it re-scan and then wait to backup more files? 4.8.3 running, not sure why this is happening.

    Reply
  5. D S

    Mine keeps starting and stopping over and over. It’s trying to upgrade so I took the steps outlined above to stop that process. That worked but now it keeps starting and stopping. Does anyone have any suggestions?

    Reply
    1. D S

      I uninstalled and reinstalled. Put the memory configurations back in and it successfully upgraded to 4.8.3 and it’s now working. No idea. Magic.

      Reply
  6. Yoz

    Hello,

    I have tried to install Crashplan on a DS216play (DSM 6.1.2). It’s ok for Java8 install, but when i added “packages.pcloadletter.co.uk” 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.

    Regards !

    Yoz

    Reply
  7. craig1001

    4.8.3 is now on my Linux Mint machine, but the DS415+ with CrashPlanPro 4.8.0-0044 won’t run. I’ve reinstalled it and copied the new token over to the PC but CPP on the NAS just won’t run. Basically it stopped after the DS upgraded to DSM 6.1.2-15132 about 10 days ago. This is an installation that’s been running for a few years and been fixed successfully a couple of times a year when upgrades stop it working. I’m at a loss to know what the problem is this time. What’s this CPIO file mentioned earlier? Where to I check for it?

    Reply
      1. craig1001

        Thanks for that, but I’m afraid I don’t have a cpio file at sudo cp /var/packages/CrashPlanPRO/target/bin/cpio and I don’t have an install.vars at /var/packages/CrashPlanPRO/target/install.vars. I’ve had Java8 in for sometime as 4.8.x has worked for ages now. I reinstalled just to make sure I selected the default java installation. So still at a loss.

      2. ajwillmer

        Ah, if you are NOT running the PRO version you need to check:/var/packages/CrashPlan/target/bin to find the cpio file and you will find the install.vars file at: /var/packages/CrashPlan/target

  8. craig1001

    But I AM running the PRO version which is why I changed /CrashPlan/ for /CrashPlanPRO/ ;)

    Reply
  9. craig1001

    Yes it does. And it now has a cpio file it too. It didn’t before. However, it still doesn’t have an install.vars file but it does have a file call vars.sh.

    Reply
      1. craig1001

        No, I’m totally stuck as to what to do. Anything I’ve done in the past doesn’t work. So I’ve not been able to back up for nearly 2 weeks now.

  10. James Russo

    I’m trying to install for the first time, and it seems to stop working after upgrading to 4.8.3? Any chance of getting an updated package?

    Reply
  11. ZeusII

    Hi, here is a link to download my fixed version with the instructions I explained in previous posts.

    To install, just use the Manual Install button. There is NO need to uninstall a previous non working version, this works as an upgrade.

    This method worked perfectly on my DS713+ for the last two crashplan upgrades, however it may not work for you, so use at your discretion.

    Here’s the link: https://www.dropbox.com/s/tidduxmkcp2ox2c/crashplan4.8.3-custom-0045.spk?dl=0

    As I said before, there’s only two changes:
    – INFO file: upped version number
    – installer.sh: added reference to 4.8.3 to download that build

    Reply
    1. craig1001

      Thanks for that but the install failed. Even allowing for setting permissions to install from any publisher.

      Reply
    2. Tad

      I am getting a “The package file is corrupt. Please download again or contact the package developer…”

      Reply
    3. thelke

      I am getting “The package file is corrupt. Please download it again or contact the package developer…”

      Reply
    4. erben22

      Thank you for this — it pointed me in the right direction to get things back up and running. I ran into two quirks:

      – The http download link seems to be unavailable for the 4.8.3 package, but using https worked fine. I downloaded it manually and placed it in the public share of my synology.
      – The client service on my synology was only listening on localhost:4243. I had to edit /var/packages/CrashPlan/target/conf/my.service.xml and update the serviceUIConfig/serviceHost element to be 0.0.0.0 instead of 127.0.0.1.

      Reply
  12. craig1001

    I’ve now got CPPro running on the NAS by using some of Martin’s instructions:-

    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

    It let me do a full update after which it ran ok. Even let me stop and start it. It’s now been running for several hours. However, now need to remove and reinstall CPPro on the Linux PC as last time it managed to “adopt” my diskstation as my PC so that’ll need readopting if I can change the key before it starts up so it’s pointing to the NAS. So nearly there. Thanks for help so far :)

    Reply
  13. craig1001

    What’s going on with this message board? I tried several times to post a reply. Nothing appears but it recognises I’ve posted the same message before. Weird!

    Reply
  14. cyprianpl

    After almost a month of downtime(!) I finally managed to get it to run!… CP Syno package complained for the first time that it couldn’t download CP 4.8.0 from code42 website, so I downloaded the latest CP linux package to public shared folder, changed the version in the file name to 4.8.0, and then CP syno package installed and run without trying to upgrade CP.

    Reply
  15. craig1001

    Tried posting my investigation results and further question but the blog won’t let me. Looks like I’m stuffed :(

    Reply
  16. ccanzone

    Hello Everyone,

    After a few months trying to use Amazon Cloud Drive I came back to Crashplan. But Patters package does not install. It looks for 4.8.0 but there is only 4.8.3 in Crashplan’s site. I’ve tried all the tricks mentioned here (including a 4.8.3 mod) but was unlucky. Does someone have the 4.8.0 install to share, so I can install it using Patters official process and then upgrade it to 4.8.3? Many thanks.

    Reply
  17. aadhoc78

    Oh come on…. am I the only one with this nuisance?!?

    I’ve got these directories accumulating over the years:
    /volume1/crashplan_1, crashplan_2, … crashplan_35

    All those directories appear in DSM -> control panel -> shared folders

    I can’t tell if these come from updates, reboots, …
    They seem to be copies of “/volume1/crashplan” so they’ve all got an empty “backupArchives” directory within. If that’s a repo for backup files, I don’t use it (ergo, always empty). I’d suspected that these come from an upgrade script, or a synology archive retention service… but I can’t find where/when they are created.

    Reply
      1. aadhoc78

        I started removing the older crashplan_NN directories, leaving only the most recent. Mine all seemed empty, so I’m nuking them. Even my most recent crashplan_38 is empty. At one point I had been backing up another computer via CrashPlan to my Synology as the destination, and the Synology had the CrashPlan service as its destination. Maybe these are from my old backup experiment. Is that anything like your situation?

  18. craig1001

    I’m going to try to drip-feed my question that this blog told me it had accepted, doesn’t show and won’t let me post it again! So here goes….. Part 1
    “So CPP is running on the DS415+. It’s ui_info file is 4243,the token,0.0.0.0. Code42 reckons the IP should be 127.0.0.1 but if I set it to that it’s reset to 0.0.0.0 every time I restart the app. I believe 0.0.0.0 means listening to all devices.”

    Reply
  19. craig1001

    Part 2 (for the 3rd time!)
    “The problem now is connecting the Linux Mint Desktop to it. It’s .ui_info says 4200,the token,127.0.0.1. I have followed Code42’s advice (web page: Use_CrashPlan_on_a_headless_computer) and carried out the port redirect: ssh -L 4200:127.0.0.1:4243 rootATxxx.xxx.xxx.xxx. The PC normally connects without a password to the NAS for automatic backups. However, when I run the CPP desktop, it never connects. I’ve totally uninstalled and reinstalled PPC but still no joy. This all used to work fine before the last DSM update. Think I’m in a bit of a pickle. Any advice appreciated.”

    Reply
  20. craig1001

    Think the problem was something looked like a URL so have replaced the link to Code42’s site with the words “web page:”. Seemed to do the trick.

    Reply
  21. Jeff

    I am having trouble getting my CrashPlan Home client to connect to my Synology NAS. I have successfully installed and am running CrashPlan version 4.8.0-0044 on my Synology. I have tried installing CrashPlan version 4.8.3 on my Windows PC, using the configuration guidelines provided above. However, when I run the client on my PC, it cannot connect to my NAS. Is this a problem of running different versions on the PC and the NAS? If so, where can I download version 4.8.0-0044 for my Windows PC?

    Reply
  22. rocko36

    I am having trouble getting my CrashPlan client to connect to my Synology NAS.

    I have successfully installed and am running version 4.8.0-0044 on my NAS.

    The only version of the client software available for download from CrashPlan’s website is version 4.8.3. I have installed this on my Windows PC and made the configuration changes cited in the above post. However, the client will not connect with the Synology NAS.

    Is this a problem of running different versions of CrashPlan on the NAS and the PC? If so, where can I download version 4.8.0-0044 for my Windows PC?

    Reply
    1. Thor Egil Leirtrø

      It is more likely that the .ui_info file on your PC does not match the one on your NAS. It must have the port and guid from the NAS-side file, and also the NAS IP address.

      I’m running 4.8.3 UI and 4.8.0 NAS – no problem.

      Reply
  23. craig1001

    Finally sorted it all. Turns out I couldn’t make an automatic, passwordless connection to the NAS because somehow, my /.ssh/id_rsa file permissions were set to wide. They were 777. Had to reduce to 400 then connections sprung to life between PC and NAS and all is well. It was a nasty “gotcha” only found because I use a cron job to run a backup script that SSH’s to the NAS from the same machine. Had to push the cron output to a log file to debug it. Hope this tale of woe helps someone else.

    Reply
  24. Haim

    I have DS216j and I tried to follow this guide.
    1. I configured the Package Center but I don’t see CrashPlan in the Community tab (I do see other things from the same source like Minecraft).
    2. I don’t have Java Manager available, I used the Java8 from Synology – I hope this is ok.

    Did anyone try it on this model? Any ideas?

    Thanks!

    Reply
  25. JohnC

    When I reboot my Synology DSM 712+ Intel ATOM sometimes / often the CrashPlan package does not run automatically. Usually I only discover this when I get an email alert “unable to reach any backup destinations for 3 DAYS”. DSM 5.2-5967 Update 3, CrashPlan package and Java are latest versions. Is this a known issue?

    Reply
  26. Thor Egil Leirtrø

    So – it seems I may have perhaps finally hit the ceiling with my about 6TB backup set.
    My Crashplan has been restarting every 5 minutes for the last two weeks. I have USR_MAX_HEAP=1536M and even increasing this somewhat makes no difference. Looking into service.log.0 I see “oomStack=java.lang.OutOfMemoryError: Java heap space” So everything is consistent with the “not enough heap” syndrome.
    But the weird thing is that it happens every 5 minutes, and creating a small backup set makes no difference – it crashes anyway. Everything is located in the same volume, so the volume size might be the deciding factor rather than the backup set.

    Maybe time to move on to a DS1517+ which supports up to 16GB RAM – does anyone have any experience with this one?

    DS412+ / 2GB RAM / DSM 6.1.3-15152 Update 1 / Crashplan 4.8.3

    The error message:
    [07.26.17 11:58:38.311 ERROR ub-BackupMgr .service.backup.BackupController] OutOfMemoryError occurred…RESTARTING! message=OutOfMemoryError in BackupQueue! FileTodo[fileTodoIndex = FileTodoIndex[backupFile=BackupFile[697f8ba2ec02ecebf56482adf06132db, parent=04f3581b15e112cc23b1d7bd1904073a, type=0, sourcePath=/volume1/public/@eaDir/jre-8u121-linux-x64.tar.gz@SynoEAStream], newFile=true, state=NORMAL, sourceLength=347, sourceLastMod=1501016837000], lastVersion = null, startTime = 1501062894337, doneAnalyzing = false, numSourceBytesAnalyzed = 0, doneSending = false, %completed = 0.00%, numSourceBytesCompleted = 0, isMetadataOnly = false], source=BackupQueue[608721169522622978>42, running=t, #tasks=0, sets=[BackupFileTodoSet[backupSetId=1, guid=42, doneLoadingFiles=t, doneLoadingTasks=f, FileTodoSet@625788232[ path = /volume1/@appstore/CrashPlan/cache/cpft1_42, closed = false, dataSize = 475, headerSize = 0], numTodos = 3, numBytes = 421755]], BackupFileTodoSet[backupSetId=805750894876710211, guid=42, doneLoadingFiles=t, doneLoadingTasks=f, FileTodoSet@1853453501[ path = /volume1/@appstore/CrashPlan/cache/cpft805750867896710211_42, closed = false, dataSize = 432, headerSize = 0], numTodos = 4, numBytes = 149599318]]], env=BackupEnv[envTime = 1501062894328, near = false, todoSharedMemory = SharedMemory[b.length = 2359296, allocIndex = -1, freeIndex = 0, closed = false, waitingAllocLength = 0], taskSharedMemory = SharedMemory[b.length = 2359296, allocIndex = -1, freeIndex = 0, closed = false, waitingAllocLength = 0]], TodoWorker@1722366757[ threadName = BQTodoWkr-42, stopped = false, running = true, thread.isDaemon = false, thread.isAlive = true, thread = Thread[W775142089_BQTodoWkr-42,5,main]], TaskWorker@1061115215[ threadName = BQTaskWrk-42, stopped = false, running = true, thread.isDaemon = false, thread.isAlive = true, thread = Thread[W1462186205_BQTaskWrk-42,5,main]]], oomStack=java.lang.OutOfMemoryError: Java heap space

    Reply
    1. badbob001

      I encountered the same on my 1812+ with 4GB ram, but my backup size is 10-12TB. Even a heap size of 3+ MB didn’t help. Memory requirements are closely related to total objects in backup, including deleted and versioned items. Breaking that up into backup sets does not help at all. I tried messing around with disabling compression, encryption, and reducing versions kept, but it didn’t really help at all.

      I considered getting a 1817+ with even larger drives, but I didn’t like seem like I would be getting my money’s worth since the 1817+ is minimally changed from the prior 1815+ and has the same old cpu.

      I ended up creating an ubuntu system from old pc parts (i3 cpu, 16GB ram, 40GB hd, cardboard box), nfs mounted synology volume so it has the same path as on the nas, installed crashplan, adopt volume, and done. Checking the files to upload does take longer since it’s checking over the LAN instead of over SATA. But no worries about crashplan upgrades as that now happens on its own.

      Reply
      1. Thor Egil Leirtrø

        Thanks for chiming in. Your experience seems to confirm that messing with back sets doesn’t help me and that I have really hit the limit on the current system.
        I will have a look the DS1517+ with 8GB RAM. It supports up to 16GB RAM and 50TB disk, so it looks like it will have room enough for me – at least in the immediate future :)

  27. haimcn

    Hi,
    I’m trying to install crashplan on Synology DS216j.
    I followed the instructions but I don’t see crashplan in the community section, I see some of the other applications but none of crashplan.
    Any advice? anybody installed it on this model?
    Thanks!

    Reply
    1. patters Post author

      If you don’t see it, then it doesn’t work for your CPU type. ARM and PowerPC CPUs were excluded a few versions back due to Code 42 introducing new proprietary native binary dependencies.

      Reply
  28. Thor Egil Leirtrø

    So, after Crashplan stopped working on my DS412+ (>6TB backup with only 2GB RAM) I decided to upgrade to a DS1517+ with 8GB RAM (max 16GB). (see two posts above).
    When it arrived I moved the disks over to the new cabinet and booted up. I selected migration with “keep settings”, it upgraded the OS to latest version, I fixed the IP address and adjusted the Crashplan heap to 6GB – and everything worked. Easiest migration ever.

    Two things though
    – Before the new box arrived I did a few uninstall/installs of the Crashplan package, and it somehow stopped upgrading itself to 4.8.0 after install. It is still stuck on 4.8.0 – any ideas?
    – The realtime detection of changed files still does not work, I’m relying on the daily scan of the file system to get a backup of new and changed files. Any ideas?

    DS1517+ / 8GB RAM / DSM 6.1.3-15152 Update 2 / Crashplan 4.8.0

    Reply
    1. patters Post author

      There were some issues with the hosting server having a library missing which caused it to log an error with every web hit. My hosting co fixed that, but then I had to re-write my PHP code to use the new MySQL commands because the old ones are deprecated in PHP 5.5 and this was also causing continuous errors to be logged. Despite resolving this there are frequent 500 internal server errors when attempting to connect now. This appears to be because my hosting account is limited in its virtual memory pool.

      Reply
  29. Shaun McCloud

    I just got a notification of CrashPlanPRO 4.9 being available. I upgraded my Windows boxes fine (mine is the admin for my DS1515+). However, my DS1515+ will not upgrade. I get the following error.
    [08.08.17 08:44:04.070 WARN 3291_DwldMgr .service.upgrade.DownloadManager] DOWNLOAD:: Unable to download patch. url=https://download.crashplan.com/installs/linux/upgrade/crashplanpro/1436674888490_33.jar?guid=783859919612263755, FileTransferException [srcPath=/linux/upgrade/crashplanpro/1436674888490_33.jar, errors=[MESSAGE_ERROR]]; DownloadManager[patchDir = upgrade, patchFiles = [1436674888490 (2015-07-12T04:21:28:490+0000)], patchProblem = false], FileTransferException [srcPath=/linux/upgrade/crashplanpro/1436674888490_33.jar, errors=[MESSAGE_ERROR]]
    STACKTRACE:: FileTransferException [srcPath=/linux/upgrade/crashplanpro/1436674888490_33.jar, errors=[MESSAGE_ERROR]]

    I tried visiting the download URL directly and got a 404 not found error. Anyone else able to upgrade to 4.9 on their Synology? Mine stores all user backups at work and I kind of need it to upload the data.

    Reply
  30. Grich

    Looks to be working , but client reports “connecting to backup destination” for over 30 minutes now. Engine_error.log has nothing but servicelog has below error.
    [08.08.17 16:42:03.229 WARN e-listen-1-2 code42.messaging.peer.RemotePeer] RP::unable to complete session close for failed connection, session=RemotePeer-[guid=802397960060444013]; PeerConnectionState-[state=CONNECTING, mode=PRIVATE, currentAddressIndex=1, layer=1/2(Peer::Sabre), connecting=2017-08-08T16:41:48:231, connected=0, disconnected=2017-08-08T16:41:18:225, attempts=1, connectActivity=2017-08-08T16:41:48:231, keepAliveSent=0, minRetry=28599, reconnectable, location=192.168.2.168:4242, transportPbK=X509.checksum(f1db104f9f20196178a5250ac37f44d4), transportPbKRequestable=false, public=108.192.152.105:8255]; Session-[id=807784904845018151, closed=true, valid=Optional.absent(), isAcceptor=false, remoteIdentity=ENDPOINT, completedAuth=false, lat=0, lrt=0, lwt=0, enqueued=false, local=null, remote=null, usingProtos=false, sessionState=null, remoteSessionId=0, WAN], io.netty.util.concurrent.BlockingOperationException: DefaultChannelPromise@2b230939(uncancellable)
    STACKTRACE:: io.netty.util.concurrent.BlockingOperationException: DefaultChannelPromise@2b230939(uncancellable)
    at io.netty.util.concurrent.DefaultPromise.checkDeadLock(DefaultPromise.java:398)
    at io.netty.channel.DefaultChannelPromise.checkDeadLock(DefaultChannelPromise.java:157)
    at io.netty.util.concurrent.DefaultPromise.await0(DefaultPromise.java:594)
    at io.netty.util.concurrent.DefaultPromise.await(DefaultPromise.java:280)
    at com.code42.messaging.network.sabre.SabreNetworkChannel.close(SabreNetworkChannel.java:161

    Reply
  31. Dirk G

    I finally got 4.9.0 to install with Patters’ current (4.8.3) package. I just had to switch back to default system Java 8 instead of using the embedded Java that had been working before.

    Reply
    1. Dirk G

      also: I had to manually set JAVA_HOME variable. export JAVA_HOME=/var/packages/java8/target/ejdk1.8.0_144/linux_i586/jre

      Reply
  32. billerr

    …Aaaand this is the end of the road for Crashplan Home users. They just sent out a newsletter with the news that they will focus on enterprise and small business offerings only. Too bad – though I guess now we’ll be forced to find another, less break-prone way to backup our Synology NASes.
    It was good while it lasted. Many thanks, Patters, for the continued support of this package!

    Reply
    1. Martin

      Just read the newsletter also. Does anyone have opinion about Carbonite?
      Is there any other package that will run togheter with Synology?

      Reply
      1. davidjpatrickDavid Patrick

        Could we not stay with Crashplan for $10 per month for a single NAS box? I’m assuming the limit is now 5TB as per the communication. I’m running a docker crashplan “engine” and wonder also if the Crashplan engine actually changes and all we’re doing is moving to another subscription. The price point doesn’t seem that far out from what I’m paying now…

      2. mike

        Most importantly, is Patters going to keep supporting the crashplan app (even if its just the pro version)?
        So that if you decide to “upgrade” and keep crashplan.
        Without Patters constant support here, I would go else where even with the better pricing crashplan provides.

    2. Martin

      Not massively surprisingly. Been suspicious this was going to happen for a while now especially as v5 and the native clients never arrived.

      Anyone any suggestions with unlimited storage and similar prices?

      Reply
      1. runt

        That will run on a Synology NAS? Nothing yet. I’m looking at migrating my personal server to Windows so I can use Backblaze.

    3. ZeusII

      I’m even happy to have received this notice… CrashPlan client is horrible, so one less thing to worry about. I have just seen that Synology have published pricing for it’s C2 solution: https://c2.synology.com/en-us/backup#tab_plan

      I have been using this service in beta for several months in parallel with CrashPlan without problems. I think I’m gonna stick with them.

      Reply
  33. chris

    as crashplan is cancelling all consumer plan, has anyone found a cheap and similar ($60, unlimited storage) alternative?

    Reply
  34. craig1001

    What newsletter is this? I haven’t been sent one from CPP and don’t see one on the Code42 website. Must say I’m totally sick of CPP and Synology breaking all the time. It’s off more than it’s on! Could someone post a link to the newsletter please?

    Reply
    1. eric

      Good catch, Tom. This looks like a viable alternative. It gives you the flexibility of using the Synology still + having the client on some of your desktops you wanted to backup previously.

      Reply
  35. OleDK

    This is the last straw. I think that Crashplan/code42 does not realize that the product they sell is not storage, not backup, not disaster recovery, but trust. And they just flushed out any trust we had. I have just ordered a second Synology which I will place at another physical address and which will run Hyper Backup Vault.

    Patters, thank you very very much for your dedicated support throughout the years.

    Reply
  36. Hal Sandick

    Patters,

    So here’s a question for you. Will you continue to support crashplan small business?

    thanks for all you’ve done

    hal

    Reply
    1. patters Post author

      I just received the email notification about this today. Hopefully the client is basically the same, and it’s just a branding and pricing change. If so I should be able to keep things going. Considering you get a big reduction off the small business rate as an existing customer for the first year it actually translates to a net saving for that time.

      Reply
      1. chris

        hi, Fyi I switched to crashplan on synology docker 2 months ago. Its running flawlessly and updates itselt.
        there are easy to find / follow tutorials…
        I would assume theyll make a crashplan pro docker soon.

        there is also synology c2 beta but only in europe right now.

        carbonite synology setup guide looked suboptimal as far as i could see.

      2. patters Post author

        Did some testing just now. I have the installer working. Judging from Twitter, the Code 42 servers aren’t coping with the migration properly. It sits on a “Migrating” spinner on the website, and my CrashPlan PRO client says its subscription has expired. Lots of similar reports on Twitter. I’ll wait until my subscription is migrated successfully before publishing the update.

        The migration process for Synology from a paid CrashPlan subscription to CrashPlan For Small Business (CrashPlan PRO) will be as follows:

        • Leave the CrashPlan 4.8.3 Synology package installed.
        • Go through the migration process as indicated in the email/website. This seems to trigger the client to begin an update to 4.9 which will fail. It will also migrate your account onto a PRO server.
        • Log into the CrashPlan PRO admin console as per these instructions, and download the 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. Preferably use Firefox for the Linux version download – most of the other web browsers will try to unpack the archive, which you don’t want.
        • 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 Synology.
        • Manually install my soon to be published CrashPlan PRO 4.9 Syno package concurrently with your existing CrashPlan 4.8.3 Syno package.
        • This will stop the CrashPlan package and automatically import its data. Notice that it will also backup your old CrashPlan .identity file and leave it in the public shared folder
        • Start the CrashPlan PRO Syno package, and connect your CrashPlan PRO console from your computer.
        • You should see your backups as usual. At first mine reported something like “insufficient device licences”, but now it says “subscription expired”.
        • Hopefully this should fix itself once the demand on Code 42’s infrastructure settles down. I will publish an updated Syno package once my subscription is confirmed working.
        • Uninstall the CrashPlan 4.8.3 Syno package once your backups are confirmed working in CrashPlan PRO 4.9.
      3. runt

        I have a contact at Code 42 and he says almost all migrations fail. If it sounds for longer then half an hour, it failed. My personal account is currently at that state although it has removed my backed up data and additional computers in not migrating.

  37. Andrew Warren

    If your backing up only the NAS and have large storage requirements and want private encryption key it seems that crashplan business is still by far the cheapest option.
    Please let us know Patters if your going to keep supporting the business version.

    Cheers

    Reply
    1. mike

      I agree with Andrew. If Patters continues to support Crashplan then there is not an equal cost/feature cloud solution in the US.
      What say you Patters?

      Reply
      1. ahershler

        Please consider carefully! The information about migrating to CrashPlan for (Small) Business (formerly CrashPlan Pro) states that CrashPlan for Business will NOT migrate any cloud backup (i.e. a backup made to CrashPlan) larger than 5 GB. Such backups will be permanently lost, and cannot be re-done on CrashPlan for Business.

      2. Thor Egil Leirtrø

        Actually, they say: (https://support.crashplan.com/Subscriptions/Migrate_your_CrashPlan_for_Home_account_to_CrashPlan_for_Small_Business)

        “Most backups to CrashPlan Central continue automatically.
        There is one exception: cloud backups that are larger than 5 TB cannot be migrated to CrashPlan for Small Business, due to technical platform constraints.
        If one of your computers has more than 5 TB of data backed up to CrashPlan Central, that computer’s cloud backup is permanently lost when you migrate. That computer starts a new backup when you migrate your account to CrashPlan for Small Business. Local backups on that same computer are not affected.”

        i.e. It will start over from scratch if the backup set is bigger than 5TB when you convert. I guess I will have to reduce the size somewhat before converting.

  38. craig1001

    So having done without CrashPlanPRO backing up for 10 days (having only had it working for a couple of weeks since it went off for weeks last time!!!!!) I deleted it off my DS415+, restarted the NAS reinstalled it (V4.8.3-0045) with default java. It was running, so stopped it and restarted ok. Left it running for an hour. Then found the new token, modified the ui_info file on my Linux Mint PC, ran the port redirect and finally connected to CPP on the NAS. Yippee!!. As soon as I selected Volume1 in the backup section, it all stopped. CPP had stopped on the NAS. Logs said NAS had downloaded a new version of CPP then “synology extracting upgrade from /var/packages/CrashPlanPRO/target/upgrade/1436674888490_33.jar”. The following (last) line said CPP stopped. It won’t restart. I’m thoroughly sick of the whole affair. I need to work, not baby sit this piece of crap for days on end! It’s supposed to be sitting their, quietly in the background, doing it’s stuff while I do mine. Have mailed Code42 and suggested they talk to Synology or do without my business. Sent them a link to this too.

    Reply
  39. Pingback: CrashPlan leaving home market - rebelpeon.com

  40. craig1001

    Looking further at the log files it appears the NAS downloaded and installed the upgrade successfully. It was only AFTER that was done that the NAS then tried to extract the upgrade?! Then it failed. Looking at the directory the upgrade was supposed to be in, there is no .jar file there of any description. I’m wondering if there is a sequencing issue in something somewhere. I’ve restarted the NAS to no effect. Totally stuffed (again!).

    Reply
  41. craig1001

    Anyone have any advice on how to progress this issue. For a start it would be good to know definitively which Java version should be selected on installation.

    Reply
    1. patters Post author

      Updated package is nearly done. I just need to confirm the migration from Home to PRO actually works but currently Code 42 seems to have completely dropped the ball on account migrations according to Twitter feedback, and a comment on here by ‘runt’. The Java version is immaterial.

      Reply
      1. davidjpatrick

        Account migration didn’t work for me either – had to do it in two steps as I was signed up to the free month trial. Once logged in and completed the account settings/payment options all is now OK. I run the docker crashplan app which seems to work flawlessly – after account migration the engine updated itself to PRO although suspect there’s not that much difference – just branding. Client side set-up was pretty easy – no difference and apps downloaded from the PRO web page. All-in-all not bad – the re-sync took a long time though after the PRO engine upgrade.

      2. patters Post author

        But don’t you lose the price reduction if you sign up to the free trial? Or does the migration work after you activate the trial?

      3. davidjpatrick

        It was a little odd but I did get the price reduction for 12 mths after completing the account set-up (following the links to account migration in the email communication) and I also received confirmation of the free trial of PRO. I’ll keep an eye on the billing to be sure but all seems to be Ok now. I can see the subscription starting in November this year for 12 mths. Still think at $10 per month for unlimited storage is by far the cheapest option.

      4. patters Post author

        Code 42 sent a mail saying that the migration is not complete and I need to sign into the Admin Console and retry the migration web link in order to save my data from imminent deletion.

        It doesn’t work :(

      5. patters Post author

        It says Registration Incomplete. If I click on that it takes me to the same Next Steps announcement web page (same one linked in that migration incomplete email) that then has the migration offer and the same old broken “Migrating” spinner thing that doesn’t demonstrably do anything.

        Support responded and said I had to clear the browser cache. They provided a web URL that’s meant to take you to the store, after authenticating with the admin portal (same URL as provided in the auto generated Migration Incomplete email). But it just spawns the Next Steps announcement page with the video of the CEO. It seems like if you see that then the process has failed and the referrer link to the store has not worked. They’re blaming their payment provider which I noticed is Digital River. How on earth could they not have tested this rigorously?

        EDIT, tried the store URL again and this time it suddenly worked. If you see a store basket with $0.00 in it and some blue text on white then that’s worked. It asks you for credit card details and then my CP PRO client immediately started working. So maybe the trick is to sign into the admin console and leave it idle for a few minutes, then try the store link URL. Or perhaps it was a total fluke.

        It’s late here so I’m off to bed. I will update the blog page with migration instructions and publish the new package tomorrow. Syno CrashPlan lives on!

      6. davidjpatrick

        Just got the email saying migration not completed!! Seems they have messed up after all!! I’ll take back my earlier comments – all-in-all – bit of a mess!

    2. Badbob001

      I considered backblaze since they are unlimited , has no restrictions on file types and sizes, and seems comparable in pricing, BUT doesn’t directly support Linux and doesn’t allow backup of mounted drives (so basically no way to backup nas).

      I currently have 10+ TB on crash plan so can I still get the discounted first year pricing for a sb (small biz) account even if I can’t do the migration? I probably can’t run the home and sb clients at the same the time so I guess I’ll can’t start the new sync to the sb account while maintaining the home sync running until my home membership expires.

      Reply
    1. fatboyw

      I tried iDrive for a day (I know it is probably not long enough) and backing during day time and night time. It is even slower than Crahsplan. I am in Australia backing up to Crashplan’s Australia server. On Crashplan, I get up to about 3-4Mbps backup speed. With iDrive, I only get 1-1.5Mbps. It is probably my location that’s a problem and may not reflect other’s situation.

      I am waiting out for patters’ test and package to move to Crashplan Small Business.

      Thanks patters for the dedication to this work.

      Reply
      1. ilkevinli

        If patters continues to support Crashplan Small Business, I will convert and continue my subscription.

  42. kipik

    Migration done, no issues, 1.8 TB now on CP Small Business, price plan 2.5 US$ until nov 2018, then 10$ per month. Did that Aug 24, 5 PM CET

    Reply
      1. kipik

        No, i had to install Syno Java package + Patters CP PRO 4.8.3, which upgraded to 4.9. Worked perfectly. Patters upgraded package was not available yet. Only i did a maintenance of my data on CP, and it is currently to 65.9% after 2 1/2 days, 3 day left before finish ^^

Leave a Reply

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

WordPress.com Logo

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

Twitter picture

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

Facebook photo

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

Google+ photo

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

Connecting to %s