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"
[ "${SYNOPKG_DSM_ARCH}" == "rtd1296" ] && 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_151"
  #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-8u151-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-8u151-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-8u151-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-8u151-linux-i586.tar.gz"
    JAVA_BUILD="x86 Linux Small Footprint - Headless"
  elif [ "${SYNO_CPU_ARCH}" == "x64" ]; then
    JAVA_BINARY="jre-8u151-linux-x64.tar.gz"
    JAVA_BUILD="Linux x64"
    EXTRACTED_FOLDER="jre1.8.0_151"
    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)
  • 0047 30/Oct/17 – Updated dedicated Java version to 8 update 151, added support for additional Intel CPUs in x18 Synology products.
  • 0046 26/Aug/17 – Updated to CrashPlan PRO 4.9, added support for migration from CrashPlan For Home to CrashPlan For Small Business (CrashPlan PRO). Please read the Migration section on this page for instructions.
  • 0045 02/Aug/17 – Updated to CrashPlan 4.8.3, updated dedicated Java version to 8 update 144
  • 0044 21/Jan/17 – Updated dedicated Java version to 8 update 121
  • 0043 07/Jan/17 – Updated dedicated Java version to 8 update 111, added support for Intel Broadwell and Grantley CPUs
  • 0042 03/Oct/16 – Updated to CrashPlan 4.8.0, Java 8 is now required, added optional dedicated Java 8 Runtime instead of the default system one including 64bit Java support on 64 bit Intel CPUs to permit memory allocation larger than 4GB. Support for non-Intel platforms withdrawn owing to Code42’s reliance on proprietary native code library 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
 
 

6,692 thoughts on “CrashPlan packages for Synology NAS

  1. Ian Hargreaves (@Ian___H)'s avatarIan Hargreaves (@Ian___H)

    I need help please … I’m trying to follow the steps here to upgrade… and I get an error on the first instruction .. :-(

    I’m a complete Unix novice – so please bear that in mind…

    NAS> unzip -o /var/packages/CrashPlan/target/upgrade/1425276000420.jar *.jar -d
    /var/packages/CrashPlan/target/lib/
    Archive: /var/packages/CrashPlan/target/upgrade/1425276000420.jar
    error: cannot delete old /var/packages/CrashPlan/target/lib/bcprov-jdk15on.jar
    Permission denied
    error: cannot delete old /var/packages/CrashPlan/target/lib/c42_protolib.jar
    Permission denied
    error: cannot create /var/packages/CrashPlan/target/lib/com.backup42.desktop.jar
    Permission denied
    NAS>
    NAS> pwd
    /var/packages/CrashPlan
    NAS>

    Reply
  2. fred's avatarfred

    Anyone else having trouble with the latest update to Synology ? Not sure if it is Synology or Crashplan since Code42 seems to be on 4.2 now as well.

    Ugh no luck getting to run on my end . looking at the log it seems it is trying to pull down an update version 1425276000420, but fails to run after that…Then if you try and manually run the program you can see Synology repairing upgrade

    Reply
  3. Yves Soers's avatarYves Soers

    I have Crashplan running on 2 Synology’s, one for home use one for work.
    On one NAS the version was updated 2 days ago, however on the second NAS it’s still on version 3.7.0 Shouldn’t it be updated also to version 4.2.0?

    Reply
  4. George's avatarGeorge

    Crashplan log timestamp now UTC after DSM 5.2 update

    Does anybody else see this symptom following the DSM 5.2 update? The timestamp for log entries in Crashplan log are now UTC/GMT rather than local time. The only timestamp that is correct to local time is the entry for a manual or scheduled stop/start of Crashplan.

    Thanks

    Reply
    1. Walti's avatarWalti

      Yes, the same exact behaviour here…
      I 05/16/15 10:29AM CrashPlan started, version 4.2.0, GUID 6XXXXXXXXXXXXXXX
      I 05/16/15 10:29AM Backup scheduled to always run
      I 05/16/15 10:29AM [Default] Starting backup to CrashPlan Central: 98,476 files (1.10TB) to back up
      I 05/16/15 11:44AM Stopping CrashPlan
      I 05/16/15 10:45AM CrashPlan started, version 4.2.0, GUID 6XXXXXXXXXXXXXXX
      I 05/16/15 10:45AM Backup scheduled to always run
      I 05/16/15 10:45AM [Default] Starting backup to CrashPlan Central: 98,476 files (1.10TB) to back up
      I 05/16/15 12:08PM Stopping CrashPlan
      I 05/16/15 11:08AM CrashPlan started, version 4.2.0, GUID 6XXXXXXXXXXXXXXX
      I 05/16/15 11:09AM Backup scheduled to always run
      Timestamp is UTC (here we are CEST, aka UTC+2) but stopping messages are UTC+1

      Reply
  5. Puja Abbassi (@puja108)'s avatarPuja Abbassi (@puja108)

    There seems to be a problem after upgrading to DS 5.2 (at least on my 214+). CrashPlan seems to be updating but then the upgrade does not work and it tries to repair it. Tried deinstalling and reinstalling, but still the same problem. Here a screenshot of my log (can’t copy paste from there):

    Reply
  6. Simon's avatarSimon

    Hi all,

    Just updated to 5.2-5565 and having problems getting the package to start (and stay running), just seems to keep stopping itself.

    Just me?

    Reply
  7. Simon's avatarSimon

    Damn, sorry, for some reason I thought new comments were at the top and didn’t think to scroll down to the bottom to check. Basically I’m an idiot, please delete both these posts Patters ;)

    Reply
  8. dani's avatardani

    My Crashplan (3.7.0-0030) is not starting anymore (5.2.-5565). Java 8. Log:
    Synology repairing upgrade in /var/packages/CrashPlan/target/upgrade/1425276000420.1431611503789

    Anybody?

    Reply
  9. Benjamin's avatarBenjamin

    Hi all,

    @George, I’m seeing problems after the upgrade to DSM 5.2, too, although I’m not sure whether they are actually related to a CrashPlan Pro update that was automatically downloaded. After reinstalling the package today, this is what I’m seeing in the log:

    Installing upgrade – version 1425276000420
    Update installed – version 1425276000420
    CrashPlan PRO stopped, version 3.7.0, GUID 617701986638803464
    Synology repairing upgrade in /var/packages/CrashPlanPRO/target/upgrade/1452….

    That’s where the package stops and is displayed as “stopped” in the package manager.

    Any ideas on how to work around this problem?

    Cheers, Ben

    Reply
    1. George's avatarGeorge

      Ben, if you haven’t found a solution yet, I used this after Crashplan pushed the 4.2 update to my Synology.

      http://chrisnelson.ca/2015/05/12/fixing-crashplan-4-2-0-on-synology-after-dsm-5-2-update/

      The package manager still says 3.7 (that’s not a problem). You will see an update in Package manager for CP, I would advise not doing this for now, there have been reports of problems. My system is running DSM 5.2 and CP 4.2 without any problems on my 214se as target for backup. I do not backup Synology using Crashplan so have not hit memory issues some have reported.

      Reply
  10. Yappo's avatarYappo

    So like many of you I had a forced upgrade the other day which ALWAYS breaks things.. Ugh!

    Anyway I seem to be able to backup just fine (tested), but when I go into the Restore area I just says I have an incorrect 448-bit key which is total BS. I know my key is correct and I can verify this by going to the web site and doing a restore there with NO problem..

    Anyone else notice this?

    Also, it seems that my backup from friends is no longer functioning either which really cause my friends loving using all my NAS space! haha..

    Reply
  11. Richard's avatarRichard

    Thanks Patters!

    4.2 got pushed down, all I had to do was restart the Package and then install the new 4.2 desktop client. Working like a charm.

    Still running 5.0-4482 as I don’t want to tempt fate

    Reply
  12. b5b8d2's avatarb5b8d2

    Ahhhh! Turns out when the client on your computer gets real out of date with the one on your NAS some things just don’t work right! My computer had client 3.7 and my NAS has been updated to 4.2 and as I found out there was some sort of incompatibility with encryption keys between the versions which prevents restores from working.

    Once I got my computer and NAS on the same version I was able to restore with no issue! So, be sure to keep your versions in sync!

    *WHEW*

    Reply
    1. cfpsystems's avatarcfpsystems

      I have two DS’s that I manage. The first one a 2015xs updated to 4.2 fine. The 1813+ will not. I have tried many combinations and it always installs as 3.7. Any ideas?

      Reply
      1. Singularity's avatarSingularity

        The package from the Repo is 3.7, but you should (at some point) get 4.2 pushed down from Crashplan Central. That doesn’t happen?

  13. santsys's avatarsantsys

    Looks like there is a new version of crashplan that was pushed out and now things wont start on my DS1515+.

    I 05/15/15 05:38PM Upgrades available at central.crashplan.com:443
    I 05/15/15 05:38PM Downloading a new version of CrashPlan.
    I 05/15/15 05:41PM Download of upgrade complete – version 1425276000420.
    I 05/15/15 05:41PM Installing upgrade – version 1425276000420
    I 05/15/15 05:41PM Upgrade installed – version 1425276000420
    I 05/15/15 05:41PM CrashPlan stopped, version 3.7.0, GUID 688464293909233669
    I 05/15/15 09:17PM Synology repairing upgrade in /var/packages/CrashPlan/target/upgrade/1425276000420.1431740507953
    I 05/15/15 09:20PM Synology repairing upgrade in /var/packages/CrashPlan/target/upgrade/1425276000420.1431740507953
    I 05/15/15 09:26PM Synology repairing upgrade in /var/packages/CrashPlan/target/upgrade/1425276000420.1431740507953

    Anyone have any thoughts?? Thanks!

    Reply
  14. santsys's avatarsantsys

    It looks like there is a new version of CrashPlan out. When it updates, the service will nolonger start on my DS1515+ running DSM 5.2. There is no error shown, just the “repairing upgrade” message. Any ideas?

    I 05/15/15 05:38PM Upgrades available at central.crashplan.com:443
    I 05/15/15 05:38PM Downloading a new version of CrashPlan.
    I 05/15/15 05:41PM Download of upgrade complete – version 1425276000420.
    I 05/15/15 05:41PM Installing upgrade – version 1425276000420
    I 05/15/15 05:41PM Upgrade installed – version 1425276000420
    I 05/15/15 05:41PM CrashPlan stopped, version 3.7.0, GUID 688464293909233669
    I 05/15/15 09:17PM Synology repairing upgrade in /var/packages/CrashPlan/target/upgrade/1425276000420.1431740507953
    I 05/15/15 09:20PM Synology repairing upgrade in /var/packages/CrashPlan/target/upgrade/1425276000420.1431740507953
    I 05/15/15 09:26PM Synology repairing upgrade in /var/packages/CrashPlan/target/upgrade/1425276000420.1431740507953

    Reply
  15. jpbogers's avatarjpbogers

    Dear Sir,

    After years of struggle to find an offsite backup for my Synology I found your solution. I installed the Crashplan system and it worked. 63% of almost 5Tb got backed up. Then there was some update (of the synology software)and after that the CrashPlan stopped.
    For me this is vital as the system contains really valuable medical research data. Can you help or direct me to someone who can help. I’m willing to pay for solving this issue!

    Sincerely

    Prof. Dr. JP Bogers
    Belgium

    Reply
  16. Oliver's avatarOliver

    Hi there,

    my Crashplan stopp working. I can not start it anymore.

    I already re-installed java and crashplan.

    Is there a known bug? Is the latest update killing crashplan?

    I´m running it on a DS414.

    Can anyone give me a hint?

    Best regards,
    Oliver

    Reply
  17. Singularity's avatarSingularity

    Up until just the other day I’ve had a couple of friends backing up to me with no problems. But about 6 days ago things just stopped working and I can’t figure it out. In order to originally get it working I had to add firewall rules allowing Code42’s netblock (recently added 2 others as well) in along with my friend’s addresses and none of that has changed so it appears to be something wonky with Crashplan itself cause I’m not seeing anything being blocked at the network level..

    I have DS412+, DSM 5.1, Java 7, CP 4.2 all working great!

    Anyone else running into this?

    Reply
  18. Paolo's avatarPaolo

    Hi,
    I have had CrashPlan working successfully for quite some time.

    After the DSM5.2 update the CrashPlan 4.2 Update was pushed out and stopped CrashPlan working as it did with the 3.7 Update. I followed the process to properly update to 4.2 and it now shows as running on my 412+. I also upgraded the CrashPlan client on my PC to 4.2 and altered the ui.properties files to point to my NAS as before.
    The issue I have now is that I can not get the CrashPlan client to connect to the Synology CrashPlan installation. I have tried upgrading the Java to version 7 and re-installing CrashPlan from scratch.
    Although it shows as running it does not appear to actually be backing up any files, but I can’t see what is happening without the client connected.

    Any help would be most appreciated.

    Reply
  19. MikeO3's avatarMikeO3

    CP stopped working on my NAS device. Appears update is failing. I cannot download CP 3.7 desktop client it appears so I guess the update needs to happen on the NAS device(?)

    Following error in the history.log.0:
    I 05/17/15 07:00AM Synology repairing upgrade in /var/packages/CrashPlan/target/upgrade/1425276000420.1431740505515
    I 05/17/15 07:15AM Synology repairing upgrade in /var/packages/CrashPlan/target/upgrade/1425276000420.1431740505515
    I 05/17/15 07:52AM Synology repairing upgrade in /var/packages/CrashPlan/target/upgrade/1425276000420.1431740505515

    CP client is 4.2 and NAS: CP 3.7.0-0030 DSM: 5.2-5565

    Thanks for any help.

    Reply
  20. RobB's avatarRobB

    I’ve been using CrashPlan on DS713+ for about 2 months and everything was working flawless. Received update to DSM 5.2-5565 a couple days ago and now CrashPlan will not start. In the log I see that CrashPlan received an auto update, but every time I try to start the service I get a new message in the log: Synology repairing upgrade in /var/packages/CrashPlan/target/upgrade/1425276000420.1431904549466

    I am at a loss as to what I can do to get this working again. Any suggestions would be greatly appreciated! Thanks :)

    Reply
  21. Dino's avatarDino

    My crashplan on a synology 1512+ has been running great for a while now. I saw that a few hours ago an upgrade was downloaded from central.crashplan.com:443. the version upgraded to is 1425276000420. now crashplan has stopped and synology repairing upgrade in /var/packages/crashplan/target/upgrade/1425276000420.1431740160722
    thanks

    Reply
    1. Sven's avatarSven

      Ditto. “DSM 5.1-5022 Update 4” which was stable untill recently and “DSM 5.2-5565” on test device suddently became unstable and stopped working. Both give the same result.

      Reply
    2. Azu's avatarAzu

      I have the same Problem, also on a 1512+
      Crashplan stopped working 2 days ago, and can’t be started again. The Log can be found here: http://imgur.com/VxHoLog
      (Whoever at synology decided to create a log window without any possibility to copy the content should be killed…)

      Any ideas..?

      Reply
    3. Eponym's avatarEponym

      I am getting the same issue since crashplan pushed the update to version 3.7.0.
      i have not yet upgraded to DSM 5.2. Running DSM 5.1 on DS213+

      Reply
    4. Scott Jacobs's avatarScott Jacobs

      I have the same issue as well – not sure how to try and start it manually – starting it via the package manager results in that repair message being generated in the history log and CrashPlan itself never gets started.

      Reply
      1. Scott Jacobs's avatarScott Jacobs

        I found out the reason that it kept trying to repair the install – it was because I failed to rename the upgrade.sh to upgrade.sh.log (see previous posts on this).

      2. Scott Jacobs's avatarScott Jacobs

        One other thing – I found that for whatever reason I had to increase the memory to well above 2gb (was set to 1gb) for version 4.2 vs what it was using with previous 3.6 – 3.7 level. Not sure why – but once I set to 3096 – Crashplan stayed up and was able to resume backing up my stuff. Noted that it was using 2.21 gb of memory to do so.

  22. Graham's avatarGraham

    Can I get a link to the current spk for CrashPlan (not PRO). I need to manually load it to my synology as I am having some issues

    Reply
  23. Anwar's avatarAnwar

    It would seem my version has been stuck in the same “repairing upgrade in /var/packages/crashplan/target/upgrade/1425276000420.” loop as Dino.

    The repair goes on for days and days. I have tried uninstalling/ reinstalling both CrashPlan and Java 7 SE several times. (last time I tried a few months ago, 8 did not work well on my Synology DS 211+ )

    I have version DSM 5.2-5565 and it appears since I did the upgrade from the previous version of 5.2 (I upgrade regularly, generally, without issue).

    I’d appreciate any ideas or assistance.

    Thank you.

    Reply
  24. Tom's avatarTom

    Help needed to fix CrashPlan 4.2.0 stoping after DSM 5.2 update
    My setup has worked nicely for some 6 months until the automatic 5.2 Upgrade. I see many are happy with the reccomendend Root/SSH commands solution. However I have no idea how to use SSH or finding my spesific path running Is (no idea what Is is). It there somewhere I can find a more step by step directions for dummies? Or will there be an update on the package from Patters that handles the problem? Very gratefull for any advice!!
    Tom

    Reply
  25. Dale's avatarDale

    Since the update over this last weekend (1425276000420) the service has stopped and refuses to start, and therefore the client PC cannot connect to the backup engine. Reinstallation of the package will make it work temporarily but it will eventually stop. I’ve read about workarounds using SSH but was unsuccessful in getting them to work. Last time I had trouble updating DSM to the latest did the trick, but no luck this time. I am running DSM 5.2-5565 on a Synology DS214+.

    Reply
  26. Dale's avatarDale

    Also, attempting to run the updated 4.2.0 rather than the previous 3.7.0 of Crashplan Pro made no difference.

    Reply
  27. cowboyGeek's avatarcowboyGeek

    Since my 5.2 DSM upgrade and the 4.2.0 update, I’m having problems with all the friends that back up to my Synology. I get “Not ready for backup from . Reason: The destination is not available.” I have issued this command, which fixed this issue in the past:

    chmod -R 777 /volume1/Backups/Friends/

    Backups from my Synology to CrashPlan cloud storage are working fine. Any friends that are still on 3.7.0 can also backup to my Synology with no problem. However, if the friend has 4.2.0, they cannot connect.

    Can someone help?

    Reply
    1. Ryan's avatarRyan

      After upgrading to CP 4.2.0, I also had issues with computer-to-computer and/or friends backing up to my CP. I also received this message in the log: “Not ready for backup from . Reason: The destination is not available.”, and this in the CP application on both the sending machine (the peer computer) and my Synology receiving machine: “Waiting for connection”.

      After experiencing this, after resetting all uPNP settings on firewalls/routers at both ends and this still not working, I decided to directly open and forward ports on my firewall to the machines on each end. Still no dice. After checking @CrashPlanHelp on twitter and seeing that other “normal” CP users were having peer connection issues after upgrading to 4.2.0, I contacted CrashPlan support with a support ticket. I got this response:

      “A server-side fix was deployed yesterday evening to resolve this Computer-to-Computer connectivity issue. Clients should have automatically connected after this fix was deployed. If your connection is not automatically established, please restart the CrashPlan service on both computers by doing the following:

      – Open the CrashPlan app
      – Double-click the logo in the upper right corner
      – Type: ra, restart
      – Press enter

      This restarts the CrashPlan backup engine, which runs in the background. This will also close the CrashPlan desktop app, so you will need to manually reopen it.”

      The next morning after receiving this response from CP Support, I opened the CP app and noticed that the peer backups were working again.

      I replied to the CP Support case and asked if they could provide a more technical explanation as to why something server-side would affect computer-to-computer connectivity. That was yesterday, and I haven’t received a response yet, so we’ll see what they say.

      Reply
      1. Ryan's avatarRyan

        CrashPlan support wrote me back and said that the reason that computer-to-computer backups were not working (see the “waiting for connection” message mentioned above) was due to a problem with the CrashPlan Central Server not correctly handling the handshake between peer computers for computer-to-computer backups. They corrected this issue server side, so this should be working.

        Also, FYI: I followed Chris’ fix here: http://chrisnelson.ca/2015/05/12/fixing-crashplan-4-2-0-on-synology-after-dsm-5-2-update/

        However, I did NOT update the Syno Package to 4.2 after patters updated it. I kept the 3.7 version, and it was CrashPlan that upgraded to 4.2 behind the scenes. I followed Chris’ fix, and after the CrashPlan Central Server fix for computer-to-computer backups, my CrashPlan is working.

        Tip: I wouldn’t install patters’ 4.2-updated CrashPlan Syno Package until all the kinks have been worked out. Many people here in the comments are saying they are having problems after the Syno Package was updated to 4.2, so I’d hold off if you haven’t already upgraded. If you are still running 3.7 (per the Syno Package Manager) and CP is not working, it is probably due to CP pushing an update to 4.2 so try Chris’ fix. Worked for me. :)

  28. Dale's avatarDale

    Thanks I missed Chris’s post the first time around. It did the trick after all once I substituted CrashPlanPRO for Crashplan in each command.

    Reply
  29. Dale's avatarDale

    I noticed that the time in the Crashplan log has jumped several hours ahead to GMT, but otherwise it is working properly.

    Reply
  30. kamster's avatarkamster

    Need some help, I added the correct package source but my NAS does not refresh and pull the current list of packages? I go to the community list in the package center and hit refresh but the crashplan package never shows? Any ideas?

    Reply
  31. Brandon's avatarBrandon

    Any idea if the recent update causes CrashPlan to stop working. We have a few Synology’s that have been experiencing this issue for about a week now. I’ve reinstalled CrashPlan and Java multiple times. CrashPlan works for about 5-seconds and then stops working. Looking in the log, it shows that CrashPlan found and installed an update, then is unable to start. I blocked central.crashplanpro.com in the router/firewall and the CrashPlan app runs and stays running, however, that is the same FQDN that is used for the backups too, so it won’t work as a solution. Any insight that you can provide is appreciated.

    Reply
  32. Pella69's avatarPella69

    Dear All,
    I have a D412+ and I used your package from one year.
    It’s a month that it’s impossible to connect with cloud.
    I read all the comment but nothing had help me.
    I need to solve this problem so please someone tell me what I have to do, what log I have to post or something else that could help to find the problem.
    Thank you

    Reply
  33. Shmuel Goldman's avatarShmuel Goldman

    Please help!!!! can’t get it working after latest upgrade of Crashplan. I tried the work arounds but they don’t help. I tried uninstalling and reinstalling but as soon as crashplan updates to the latest version it crashed.

    I get repeated:
    synology repairing upgrade in /var/packages/CrashPlan/target/upgrade/1425276000420.1431741983868

    Nothing i do is helping.

    Reply
  34. Chris's avatarChris

    I’m not sure if this is the right venue for this, but its worth a shot. I’ve had everything running fine for a while, (I also had to go through the fix Chrisn posted to Thanks for that!) However after making that change I’ve noticed that my service starts and stops constantly now (Looking at some logs it looks like its been doing this for weeks) It always seems to trying to backup the same files but never succeeds. The Log reads like:

    CrashPlan started, version 4.2.0, GUID 4484300117474834
    Backup scheduled to always run
    [Default] Starting backup to CrashPlan Central: 9 files (1.60MB) to back up
    Stopping CrashPlan
    CrashPlan started, version 4.2.0, GUID 4484300117474834
    Backup scheduled to always run
    [Default] Starting backup to CrashPlan Central: 9 files (1.60MB) to back up
    Stopping CrashPlan

    It continues to repeat like this. I’ve attempted to re-install everything, but it always seems to get stuck. Would anyone have any idea on how to troubleshoot this?

    Reply
  35. Adriano's avatarAdriano

    Hi,

    I’ve upgraded to DS 5.2 when it was releases and after that did the “crashplan repair” loop crash upgrade that others have posted earlier, and it was apparently running fine.

    Now that CrashPlan is running, I’ve noticed that it is now constantly crashing when a few files are left to backup. It crashes every minute or so and it has been like this for days.

    In the Main CrashPlan window the current status (before crashing) is:

    “Backup running
    Remaining: 1,706 files (334,2MB)
    Completed: 697,170 files (1,3TB)
    Analyzing: volume1 > docs > @eaDir > @tmp > @tmp” – it never changes from this last line

    Could be caused because of file exclusions (these are Mac shares and I’m trying to avoid uploading junk files)? This is what I have on file exclusions:

    “.*/@eaDir/.*
    .*/@.*
    .DS_Store
    .apdisk
    .*/@tmp/.*”

    Also, I have these advanced settings set:

    Data de-dup: Minimal
    Compression: Automatic
    Encryption: Enabled
    Watch FS: Disabled
    Backup open files: was enabled and I disabled it just now to see if it changes anything.

    Thanks for any input

    Reply
    1. Adriano's avatarAdriano

      Sorry, this was again causes by memory issues: syno_package.vars wasn’t set and hence the xmx RAM value kept reseting to 1024Mb when restarting the service.

      It’s now working fine, thanks anyway.

      Reply
  36. Michal's avatarMichal

    Again the same problem with stopping CrashPlan after update. My situation:
    DS1512+
    DSM 5.2-5565
    DSM Date 2015/05/11
    CrashPlan 3.7.0-0030

    Crashplan stopped working on May 11th after updating to version 1425276000420
    Repeating “Synology repairing update…” loop since.

    Reply
      1. Vincent Musolino's avatarVincent Musolino

        Worked for me. Pain in the butt but it worked. I wonder how difficult it would be to script the 4 instructions and package them into a small app to download and run directly on the Syno without the ssh hassle :-)

      2. Marten's avatarMarten

        Had the same problem (DS1812+) but I uninstalled crashplan, updated synology and reinstalled, and all was fine. Obviously you need a fresh upgrade of DSM ready but shouldn’t be a big problem?

  37. swin's avatarswin

    My DS213+ is currently running DSM 5.0-4993U4 with crashplan 3.6.3-0027 and all is well. However, I’m starting to get behind on DSM releases so I would like to update to the latest version. Does anyone have crashplan working on the same kit? If so, any help on the upgrade path would be appreciated

    Reply
    1. cfpsystems's avatarcfpsystems

      Question, now that the syno (1813+) package has updated to 4.2, I performed a clean client install and modified the conf to point to the IP Address. The client just sits at the splash screen and does not move from this point. I tried removing the remote host and it launches locally just fine. Any ideas?

      Reply
      1. santsys's avatarsantsys

        I’ve seen this issue when the service wasn’t actually running. The connection was timing out. So i’d check to make sure the service is running and that the correct ports are being used.

    2. Eponym's avatarEponym

      It did update CrashPlan to 4.2.0 on my DS213+ running DSM 5.2. However, CrashPlan will not start.

      Reply
  38. halleys5's avatarhalleys5

    The update to 4.2 in DSM 5.2 was the smoothest ever. Been using your packages for more than a year now. I really appreciate your work on this!

    Reply
  39. Matt's avatarMatt

    Thank you for making this available! One quick question. Is there anyway to reach packages.pcloadletter.co.uk using https? I’m a bit worried about downloading packages over http since they could be modified in transit.

    Reply
    1. patters's avatarpatters Post author

      In Package Center settings, set the Trust Level to “Synology Inc. and Trusted Publishers”. My repository publishes its public key to your NAS automatically. My newer packages (CrashPlan and Java) are signed with my private key so the NAS will check they haven’t been tampered before installing.

      Reply
  40. Alexis's avatarAlexis

    Anything special I need to do I can see the update available and I can run it, but only get the options to upgrade to 3.7 and below.

    Is there anything I need to do to make 4.2 appear as an upgrade option.

    Reply
    1. patters's avatarpatters Post author

      Before you try, you will need to edit /var/packages/CrashPlanPROe/INFO and drop your package version number back down to 0030. Then Package Center will offer the upgrade again when you refresh. That way you won’t have to re-sync all your data.

      Reply
      1. cfpsystems's avatarcfpsystems

        Which Java should be installed with this new package? I tried Patters’ 7 & 8 and the syno one. I am still having stops with the package. Also, anytime I touch the max heap size setting the package will not launch. Has something changed regarding this? I have a lot of sets that add up to a lot of data and I think that the memory has something to do with it.
        Charlie-

  41. Richard's avatarRichard

    Hi Patters, just updated to your latest version on my DS413 and it won’t start. Tried uninstalling then reinstall from scratch but no joy. After the update to DSM 5.2, Crashplan pushed version 4.2 to my DS and I had that working using the “hack” from chrisn discussed at length above. Updated on my DS212 with no problems.

    Reply
    1. Ron's avatarRon

      I have the same issue with my DS213+. I had to revert back to the previous version. You can download the file crashplan3.7.0-merged-0030.spk from http://packages.pcloadletter.co.uk/downloads/ and save that locally on your NAS. After unistalling the 0031 version I could manually install this one and it works again. I hope Patters will fix the issue. :)

      Reply
  42. Alexis's avatarAlexis

    Thanks much appreciated. Tried it on two DS1513+ and a DS1515+ same result. Tried removing the install and even your package source restarting with the same result

    Reply
  43. cowboyGeek's avatarcowboyGeek

    I’m desperate for help on an issue but all my comments are awaiting moderation for days. How can I get them visible so I can get some help?

    Reply

Leave a reply to cfpsystems Cancel reply