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. Nathan Hill's avatarNathan Hill

    Well crud. Upgrade borked itself again. I got my email that my DS415 hadn’t backed up in over 3 days. Ok, let me go start the package. I installed a DSM update the other day and figured I forgot to make sure Crashplan started up afterwards. Nope it’s the dreaded Crashplan auto-upgrade that never works. dun dun dun

    Anyways, I went through the process here http://chrisnelson.ca/2015/07/02/fixing-crashplan-4-3-0-on-synology/. I get that it’s starting now in the package log, but Crashplan central does’t show that it’s connected and I don’t see the DS415 as online on my other clients that connect to it. Package log doesn’t show that any backup tasks are happening either.

    So I’m stuck. I’ve looked through Crashplan’s own logs and nothing is jumping out at me. I also can’t use the GUI on another machine to try and gleam anything as the other clients haven’t upgraded and version 4.4.1 is still what you get when you download, ugh.

    Uninstalling and reinstalling the package doesn’t work since 4.4.1 is what’s downloaded either.

    I’m showing this version FYI 1435726800450_270

    Reply
  2. Nathan Hill's avatarNathan Hill

    Woops, my bad. My package uninstall/reinstall (I’m assuming) of Crashplan required me to sign in with my Crashplan account again. My OSX GUI was connected earlier. I just figured it wasn’t when I got the login prompt before. I tried again on a whim and boom all my settings are intact. Everything is synchronizing and all is well with the world. At least until the next update.

    Reply
  3. Robbert's avatarRobbert

    What is the best way to check if the engine is properly installed on the Synology and is listining to the correct port(s)? My client either just connects to the engine on that machine or (when disabled) failes to connect..

    Reply
  4. Zach's avatarZach

    I have been using these simple commands to fix the failed upgrade / service not starting issues recently. Be sure to substitute your version of CrashPlan (e.g.: CrashPlanPRO)

    cd “/var/packages/CrashPlan/target/upgrade/”
    ls -l

    unzip -o /var/packages/CrashPlanPRO/target/upgrade/.jar “*.jar” -d /var/packages/CrashPlanPRO/target/lib/
    unzip -o /var/packages/CrashPlanPRO/target/upgrade/.jar “lang/*” -d /var/packages/CrashPlanPRO/target/

    Now, rename the shell script files in the (likely numerous) numbered subdirectories:

    find “/var/packages/CrashPlanPRO/target/upgrade/*” –mindepth 2 -type f -name “*.sh” -exec mv ‘{}’ ‘{}’.old \;

    Reply
    1. mkchronos's avatarmkchronos

      Worked perfect, back online. Explode the jar file, upgrade and rename the shell scripts. Simple, and effective. Very grateful.

      Reply
    2. Jason's avatarJason

      worked for me tho i had to tweak it a little and the double quotes and single quotes did not copy and paste right.

      Reply
      1. Dave in San Diego's avatarDave in San Diego

        Are you logging in as ROOT user? I got the same error when I was logging in as ADMIN. Once I used ROOT, it worked.

  5. Ian's avatarIan

    Latest DSM update Crashplan has stopped working again. DSM 5.2-5644 Update 2

    This is getting a little ridiculous, there is no confidence this won’t break at a moments notice.just got the same error in the log about ‘upgrading in’.

    Reply
      1. Ian's avatarIan

        Search for “0035 06/Nov/15” and follow the instructions on this page. I had forgotten about this.

  6. nilrog's avatarnilrog

    Isn’t the problem with the failures just that the Synology doesn’t have a real bash-shell? The upgrade script requires bash and ash isn’t enough.

    Reply
  7. Eric's avatarEric

    Ok. So I just installed the update today and low and behold Crashplan released another damn update this morning. How can I get this thing to stay up and take the upgrade? New version is apparently: 14357268000450. It the current process to wait for patters to release a new version before it starts working again only to have it broke by the next upgrade?

    Reply
    1. George's avatarGeorge

      I did this, on the Synology via SSH, after stopping CP. Note that my DS has not yet updated to Update 2.

      unzip -o /var/packages/CrashPlan/target/upgrade/1435726800450_270.jar ‘*.jar’ -d /var/packages/CrashPlan/target/lib/
      unzip -o /var/packages/CrashPlan/target/upgrade/1435726800450_270.jar ‘lang/*’ -d /var/packages/CrashPlan/target/

      I then deleted any directories named 1435726800450_270. as well as 1435726800450_270.jar (or you can move jar file out of Crashplan directory structure).

      Reply
      1. zerox20's avatarzerox20

        I have gotten it to start now and work, I just can’t for the life of me get my PC client to connect to it at all. Did the ports changed or ui_info process change or anything? I gotta be missing something obv.

      2. George's avatarGeorge

        In my case (Linux client and I use NAS as target for backup), I restarted (using restart command in client, note this also restarts CP service on client which is necessary) the client and found that it started upgrading client to 4.50. This does take a while, need to be patient. Hope that works for you.

  8. steven's avatarsteven

    Hi,
    I am trying to install the Pro version on my DS716+ I get this error:
    This package is not supported on the platform of Diskstation.

    have I missed something?

    By the way thanks for the amasing work. I have been using it for a long time now (the home version) and would like to move to the pro so I can monitor it from the web (and not having to login remotely everytime).

    continue the good work!
    Steven

    Reply
  9. hyperion's avatarhyperion

    Hi everyone–

    I’m a new user to this system, only installed a few weeks ago on my 1815+. My client (on my Mac) just updated itself to 4.5.0 and now won’t connect to the service any longer. I’m not a power user, should I just wait for the pcloadletter package to be updated? And if so, how long is that likely to take? Thanks to both commenters and the author of this really useful package.

    -hyp

    Reply
  10. zerox20's avatarzerox20

    Digged through a bit more, for some reason my client keeps trying to access my NAS on 4244, vs 4243.

    2015-12-10T05:46:03.975Z – info: Retrying communication with service connect ECONNREFUSED 10.1.10.5:4244 attempt 1
    2015-12-10T05:46:06.009Z – info: Retrying communication with service connect ECONNREFUSED 10.1.10.5:4244 attempt 2
    2015-12-10T05:46:08.043Z – info: Retrying communication with service connect ECONNREFUSED 10.1.10.5:4244 attempt 3
    2015-12-10T05:46:10.060Z – info: Retrying communication with service connect ECONNREFUSED 10.1.10.5:4244 attempt 4
    2015-12-10T05:46:12.065Z – info: Retrying communication with service connect ECONNREFUSED 10.1.10.5:4244 attempt 5
    2015-12-10T05:46:14.068Z – info: Retrying communication with service connect ECONNREFUSED 10.1.10.5:4244 attempt 6

    Only happened after the upgrade, Tried rebooting/reinstalling, still same issue. Thoughts anyone?

    Reply
    1. mkchronos's avatarmkchronos

      Ports shouldn’t have changed, you show them as being the same when you ssh in and take a look at the ui file, right?

      What does your netstat report with:
      netstat -an | grep ‘:424.’

      Reply
  11. Dietmar Spehr's avatarDietmar Spehr

    Deleted the package, reinstalled & restarted. Extracted the Token, inserted it into ui.info.

    Now all my backup sets are away and my restore data is missing also. However the Website of Crashplan still says 3,6 TB so they seem to be somewhere and the upload has started where it stopped and the completed bar shows it is almost done (as was the case before this new disaster…)

    Any ideas?

    BTW I cannot cd into the var directory with terminal and ssh on my Mac. Any ideas?

    Reply
  12. Steven (@stmey)'s avatarSteven (@stmey)

    I am trying to install the CrashPlan Pro on my DS716+ but I get this strange message:
    “This package is not support on the platform of DiskStation”
    I have successfully installed it today on a DS713+ so is it an issue of the newwe model. could you please add the braswell to the list of accepted Architecture?

    thank you

    Reply
  13. Chris's avatarChris

    Hi, I am running CPVERSION = 4.5.0 – 1435726800450 (2015-07-01T05:00:00:450+0000) – Build: 270, it doesn’t show any errors but every 5min, the process restart (Issuing restart command /volume1/@appstore/CrashPlan/bin/restartLinux.sh). I am using DSM 5.2-5644 Update 2, on a 412.

    Reply
    1. Chris's avatarChris

      Resolved my problem. With 4.5.0 it seems 512m of memory is not enough. Change the start-stop script to force 1024. Now working as expected.

      Reply
  14. Jon Etkins's avatarJon Etkins

    I wouldn’t rush out to upgrade to 4.5.0 if I were you. After my primary workstation upgraded from 4.4.1 to 4.5.0 this morning, it seems to have restarted my backups from scratch. It can see that I have ~250GB already on the NAS, but it’s telling me that it has only 2GB completed and 248GB remaining. Initially I thought this must be a compatibility problem with CP on the NAS (still at 4.4.1), but it’s displaying the same bug for my backup to their cloud server so they can’t blame it on the headless NAS destination.

    I’ve opened a ticket with CrashPlan support, and will report back once I hear from them. Apparently they’re flooded this morning, so perhaps this is a widespread problem with 4.5.0.

    Reply
    1. Jon Etkins's avatarJon Etkins

      Belay that comment. Apparently it went through some sort of internal resync process (though the GUI never said it was syncing – it said “Backing up” the whole time) and correctly picked up the existing backups. Phew!

      (Still waiting on a call back from CP support.)

      Reply
  15. Denny's avatarDenny

    To whom it may concern:

    4.5.0 running fine here.

    Of note is that I was (once again) able to conduct the upgrade without having to unload files and the like. I did two things:

    – Log into the Synology and delete all but the last update directory (1435726800450_270.*).
    – Restart the Crashplan service via Package Center. Wait 2-3 minutes.

    On the 3rd restart Crashplan finished it’s update and was ready to go. I copied the new .ui_info file to the UI host and all was good.

    It’s unclear if the first step is actually necessary. Next time, I will try without this.

    Reply
      1. zerox20's avatarzerox20

        Any of you guys have any insight into my port problem I posted above. Are you on Windows machines trying to connect to it? My Synology say I am running 4.5.0 as well.

      1. zerox20's avatarzerox20

        Wow I figured out what I did this whole time and feel stupid. I upgraded and always did it all right I somehow got the crashplan 5.0.1 CLIENT on my PC, when I needed 4.5.0. Wow doofus me?

        Anyway working now! jeez… Just move along…

  16. semperfidelis's avatarsemperfidelis

    You so totally rock! I was planning on figuring out when I was going to find the time for the workaround to get Crashplan working again but just installed the Upgrade that was pushed out and it’s running again.

    Reply
  17. Rich's avatarRich

    does anyone find that they they don’t always break under the new versions that break othesrs? I subscribe to email alerts on this thread and then cringe when I see lots of updates from people breaking. About 1/2 the time I have an issue when others do, but sometimes I don’t. does crashplan only update on restart?

    Reply
  18. Jeff's avatarJeff

    I am getting an error that the installer is unable to download Crashplan_4.5.0. Anyone else having the same issue?

    Reply
  19. rdamazio's avatarrdamazio

    Thanks so much for this package. Thought I’d contribute the patch that I apply to the start-stop script to allow it to use more RAM (running on a Synology with 6GB):

    Change:
    elif [ $RAM -gt 1024 ]; then
    to:
    elif [ $RAM -le 2048 ]; then
    JAVA_MAX_HEAP=1024
    elif [ $RAM -le 3072 ]; then
    JAVA_MAX_HEAP=2048
    elif [ $RAM -ge 4096 ]; then
    JAVA_MAX_HEAP=3072

    More than 3GB seems to be tricky since it’s a 32-bit JVM, but 3GB gets me enough to backup my ~3TB as long as I don’t watch for directory changes in realtime.

    Reply
  20. planetwilson's avatarplanetwilson

    I try and install and it just sits with the loading spinny graphic and never returns. I have tried restarting 3 times and trying again.

    /var/packages/CrashPlan is empty

    Reply
    1. Dale's avatarDale

      I tried to install the update and feared I’d have the same issue. It DID take a while to install the update, but it worked fine.

      Reply
      1. planetwilson's avatarplanetwilson

        Mine just eventually says failed to install and any further attempts to install say an install is already underway.. :(
        I have never had any issues before in getting this to work but I can’t do anything with it now.

  21. Dale's avatarDale

    Anyone else notice that 4.5.0 is more memory hungry than 4.4.1? Using 63% of my available 1GB on my DS214+, when previously it was closer to 35%.

    Reply
      1. Dale's avatarDale

        That’s a bummer. I exaggerated as it seems to be closer to 40% now, but still increased memory usage. On many of these units upgrading RAM is not an option. I’m lucky the backup set here is only about 115GB at this point. I’d never get away with this with my 9.4TB backup set at home.

      2. Chris's avatarChris

        Change the start-stop script to force 1024 memory if it think you should only use 512 It solved the problem for me. 4.5 will not work with only 512.

  22. AAA's avatarAAA

    is the package repository accessible? The non o f the packages were listed in my to my synology package center, so I made a mistake and removed the PCLoadletter but now I cant add the repository back.

    Reply
    1. Canzone's avatarCanzone

      I’ve lost the entire last night over this. After two hours sleep my brain came back to life and I searched another wget version and found one in /volume1/@appstore/DownloadStation/bin. I backed up the /usr/bin one and replaced it with that one from DownloadStation and tried installing again. Took less than 2 minutes. Now CrashPlan is synchronizing my older backup.

      Reply
  23. chris busch's avatarchris busch

    Got 4.5.0-0036 running. had prior versions running fine.
    now I edit .ui_info with my setings and it works fine until I reboot.
    Then its back to the original GUID and 127.0.0.1

    anyone know how to fix that ?

    Reply
  24. Thinny's avatarThinny

    Same issue as planetwilson I am affraid.

    I try and install and it just sits with the loading spinny graphic and never returns.
    /var/packages/CrashPlan is empty

    Anyone else facing this issue?

    Reply
    1. mandrake74's avatarmandrake74

      Same issue here, it looks like the install script is waiting for something but I can’t find a log to figure out what it is looking for. I tried to reboot (sic) and it turned out that I had to reinstall from scratch since the upgrade failed. But I have the same issue, the install is stuck with a
      wget process -even if the file has been downloaded, in /volume1/@tmp/.

      Reply
      1. ML's avatarML

        Same Issue for me…
        And still no solution :-(
        I tried to install Java 8. I was in Java 7 with the previous version of CrashPlan, but this doesn’t change anything., the script is still waiting the wget.
        I also tried to download CrashPlan_4.5.0_Linux.tgz in /public/, but that doesn’t change anything the script still start to download the file and don’t want to use the file in /public. How can force the install script to use the file in /public ?

      2. ccanzone's avatarccanzone

        Hello ML,

        I had the same issue. I saved a backup of /usr/bin/wget and replaced the one there with another that I found in /volume1/@appstore/DownloadStation/bin. Then I started the installation process again through Package Center and it finished in less than two minutes. No issues, no glitches, running smoothly since then.

    2. mandrake74's avatarmandrake74

      Eventually I fixed this issue by changing the wget provided with DSM 5.1 with the one from opt packages (just did a ln -s /opt/bin/wget /bin/wget after having renamed the original one). Then I got an error message saying it could not download the install package but I downloaded it manually and moved it under /volume1/public, then the install trough the package centre worked.
      I had to redo all the stuff with the token etc on the client side though, but the resync worked pretty well.
      Still don’t understand why this happened, maybe due to the fact I’m still in 5.1
      Too bad that CrashPlan still doesn’t support officially the Syno, and again thanks for your work patters.

      Reply
      1. Charles Naslund's avatarCharles Naslund

        I have the same issue as mandrake74 and Thinny with no /var/packages/CrashPlan folder ever being created when attempting to install the CrashPlan package under DSM 5.1-5022. I have a downloaded /volume1/@tmp/CrashPlan_4.5.0_Linux.tgz file but the installer.sh script under /volume1/@tmp/pkginstall/scripts refuses to run. How can i manually install this package?

      2. planetwilson's avatarplanetwilson

        I wonder if that is my issue then, I am still on 5.1 as I am running XPEnology. I will see if I can upgrade today and report back if that fixes it.

  25. BertXL's avatarBertXL

    Since I’ve installed the latest version (with the same issues as always), I don’t see any log information anymore when I click the “View log” link in the package center on my Synology NAS. Does anybody have an idea what could be causing this? The only thing I see is the message “No Data”

    I did not do anything different this time during the upgrade of Crashplan on my server that I did the previous times. I did have to adopt the backup for some reason because the Crashplan client thought the 1.4TB backup was for my laptop…

    Reply
  26. Irene Merkens's avatarIrene Merkens

    Last week I upgraded CrashPlan to version 4.5.0. Since the new version it says “Backup running”, but it’s stuck at Analyzing a file. It’s not uploading any files.

    I have already tried reinstalling Crashplan and played around with memory settings (before I upgraded to version 4.5.0 I was using USR_MAX_HEAP=3072M which was working fine). I have a Synology DS1511+ with 3GB physical memory.

    What should I do?

    Reply
    1. Roger's avatarRoger

      Same here. Everything worked fine until 4.5.0 was installed. Now it is constantly restarting and 3072M is max heap size. If I try anything bigger it won’t even launch.

      Looks like end of the road for this setup now :(

      Reply
  27. Canzone's avatarCanzone

    I’m having the same issue with wget. It gets downloading forever. Manually downloading to the public directory did not work (installer don’t even try that). I tried everything and nothing worked. Anyone knows why the package cannot be wget-ed? I’m worried because I have around 2Tb already backed up and it won’t be cool to loose everything. I tried removing and reinstalling but the wget issue remains (now that I uninstalled I’m terrified about loosing the backup). Could not find the /opt version that madrake74 suggested. Any help will be welcome.

    Reply
    1. mandrake74's avatarmandrake74

      If you are using DSM 5.1 then the issue is definitely wget, if you don’t have optware/ipkg bootstrap installed then maybe you better have to upgrade to 5.2 directly like planetwilson reported. If for whatever reason you want to stay on 5.1 for now like me, then just run ipkg to get the optware version of wget and replace the one provided with DSM.

      Reply
      1. mandrake74's avatarmandrake74

        Scratch this, I just noticed that there is another wget version provided out of the box on DSM 5.1 under DownloadStation -thanks for the tip Canzone, see a few posts above. You don’t even need to use optware, just copy or link the wget binary under /volume1/@appstore/DownloadStation/bin
        I haven’t tried it since I’m using the optware binary but apparently it works.

  28. Baki's avatarBaki

    I’m planning to buy ds215j, does it make sense to install crashplan package there, will it work without trouble? Thanks.

    Reply
    1. Dave's avatarDave

      I wouldn’t bother, I’ve used this for the past 3 years and it constantly needs updating and “fixing”, when my subscription runs out I’m either going to get a better NAS or better cloud backup provider.

      Reply
      1. ChazD's avatarChazD

        I would have to agree with Dave on this one. If you think you can set it up and forget about it then get ready for hours on end of pure disappointment. Its always something. One day its backing up fine and the next its totally worthless. If you are using for business critical data then I would look for a better solution because this is not it. I love my syno nas but this backup is just not worth the headache.

  29. Scott's avatarScott

    Hi. I uninstalled Crashplan to upgrade to 5.2-5644 Update 2. After install Crashplan Pro 4.5.0-0036, which was from an earlier version, Crashplan won’t start. I’ve seen some issues with the application not starting with earlier versions, but not sure if it applies to this version. Any guidance would be appreciated. Thanks.

    Reply
  30. ray's avatarray

    HI, I am running DM 5.2 and I just installed and running correctly for the crashplan, but when I SSH into my Synology and check the .ui file, /var/crashplan inside is all empty. does that mean it didn’t install correct?

    I tried delete and re-install, still got same result.

    thansk!

    Reply
  31. ced's avatarced

    Same issue for me. Crashplan works but stucks to analysing file. Noway to do it working for the moment. Disappointing to see that each Crashplan update makes the synology crashing.

    Reply
  32. Kevin Dunn's avatarKevin Dunn

    Hello all.
    I have somehow managed to change a security setting (or a port forward, or something) on my synology. Crashplan is running,but restarting.
    I’ve checked the logs (service.log) and it’s not a memory issue (I’ve upped the memory to 2G. I can run the crashplan app from my PC and connect to the Server on the Synology, and the CrashPlan website shows the last contact with the Synology was 2 minutes ago. The backup log recognizes that there are files to back up.
    In the services.log file, I _am_ seeing an Exception; I’m not sure if this is an issue or not.. I’ve checked, and my config file has the service port at 4248/4249 (which I don’t remember changing). I’ve tried changing it back to 4242/4243 and restarting with no luck. Does anyone have any insight?

    NapPMP:: Only for site local addresses. routerAddr=/0.0.0.0
    [12.31.15 13:46:11.255 INFO 49_CDCWorker on.net.ConnectionDiscoveryClient] CDC:: Exception creating NAT-PMP port mapping – java.lang.Exception, ConnectionDiscoveryClient[started = true, listenPort = 4248, routerIp = 0.0.0.0, testId = 0, success = false, externalAddress = null, externalPort = -1, externalType = Unknown, status = ConnectionTestStatusEvent[running = true, success = false, remoteAddress = null, externalPort = 14221, type = UPnP], uPnP = UPnP[localAddress = 192.168.1.13, gateway = net.sbbi.upnp.impls.InternetGatewayDevice@16c1147], natPMP = null, owner = PeerLayer@16553530[635869017800179973@0.0.0.0:4248], lastFour = 9973, worker = Worker@24980943[ threadName = CDCWorker, stopped = false, running = true, thread.isDaemon = true, thread.isAlive = true, thread = Thread[W27035549_CDCWorker,5,main]]]

    Reply
  33. Richard's avatarRichard

    Well not sure what’s broken this time but I’m unable to get the application to connect to the Synology. Verified the token value is correct (it had changed in the file). Stopped and restarted the package and I’m still unable to connect.

    Reply
      1. ced's avatarced

        I was stuck and I tried this method. IT WORKS !! Now my Crashplan works again !! (I increased heap size to 3500m too)

  34. tuxerr's avatartuxerr

    I have now stopped using crashplan and switched to a set-up with CloudSync and OneDrive (since I have on 1TB of “free” storage). Running DSM 6.0 beta since the functionality is much better when it comes to CloudSync. CloudSync works with other cloud storage solutions as well like Dropbox. So far it works like a charm “out of the box” and fulfill the needs I have.
    Really appreciated patterns solution but needed to spend less time of reconfigure and fixing issues every time crashplan did an update. But also due to my understanding only intel based synology boxes will be bale to run patterns solution in the future due to changes crashplan will do in there coming versions.

    Reply
    1. Rich's avatarRich

      How is Cloud Sync with versioning? I started with crashplan because I use to write code and wanted to be able to restore a SET of files to to 3 days ago if I screwed up. As long as I have single file versioning I might be okay.

      Reply
      1. Shane's avatarShane

        I can let you know that I also use Google Drive at work and have tried Hubic at home. Neither use versions. Both will only allow sync one way or the other.

        I would suggest that if you use windows you turn on previous versions on your hard drive and setup when snap shots are done.

  35. Jason's avatarJason

    For the second time in a few months the upgrade to Crashplan on my Diskstation has resulted in my backupArchives folder being recreated, losing all my previous archives. I see in the threads that the backup directory should be /volume1/crashplan/backupArchives, but it is defaulting to /volume1/@appstore/CrashPlan/backupArchives instead after the upgrade. Is this something that needs to be set each time an upgrade takes place?

    Reply
  36. Wayne's avatarWayne

    Hello All….

    I would like to confirm that the RS815 NAS with the “MARVELL Armada XP MV78230” CPU will run this Crashplan client.

    Thank you…!!!! :)

    Reply
  37. pauljohnmeyer's avatarpauljohnmeyer

    Hey, it looks like a new patch came out for CrashPlan (4.5.0 –> 4.5.2). Has anybody else been having issues since this has happened? CrashPlan keeps crashing for me and the app interface is saying that my NAS is completely backed up (all 1.6 TB in the course of 10 min) despite the fact that CrashPlan’s website tells me that almost none of it has backed up. Obviously, backing 1.6 TB in 10 min is completely unrealistic.

    Reply
  38. George's avatarGeorge

    CP 4.5.2 has been downloaded to Synology and my clients. Successfully updated Synology as per previous method. After stopping CP,

    unzip -o /var/packages/CrashPlan/target/upgrade/1435726800452_78.jar ‘lang/*’ -d /var/packages/CrashPlan/target/
    unzip -o /var/packages/CrashPlan/target/upgrade/1435726800452_78.jar ‘*.jar’ -d /var/packages/CrashPlan/target/lib/

    Moved jar (so it would not try upgrade again)

    mv 1435726800452_78.jar /volume1/dnload/

    I then deleted the failed upgrade directories with

    rm -r 1435726800452_78.1452*

    Restarted CP and all working

    Reply
  39. HappyUser's avatarHappyUser

    I can only start thanking all of you that contribute here … you really help many of us who benefit from this nice backup solution & our Synology devices. Specially to patters & acn.

    It is a pain and a risk everytime we have a Code42 upgrade, Thank goodness we’ve now learned that following this easy wide by acn at http://crashplan.setepontos.com/fixing-synology-repairing-upgrade-in-issue/ solves the issue (yes for 4.5.2 too). Thanks again guys.

    While I have some technical background I’m far from being an expert with Linux, scripting, etc but … wouldn’t it be possible to have a script that follows acn’s wide as the upgrade fail entry is found in the log … so there could be a cron job running, say dayly, if the entry is found the wide is followed searching for the last entry, deleting, unziping etc ???

    Once again thank you all

    Reply
  40. dbo94100's avatardbo94100

    Hi everyone,
    I write a .net application for Win users that automatically apply updates on synology + udate .ui_info + update ui.properties.
    It’s available at this adress : https://goo.gl/Q6LbZA (Source + binaries)

    Reply
  41. reuven's avatarreuven

    it has been working till now, but recently i reinstalled the operating system and changed the name of the server, and now it no longer works. i went through these steps several times on more than one computer and keep getting the message, “unable to connect to the backup engine”.

    Reply
  42. Joerg W.'s avatarJoerg W.

    After the very last update for Crashplan to version 4.5.0 it no longer starts (Starts and stops within seconds). Same error message in the log file (engine_error.log) regardless of update or complete uninstall/reinstall:

    Exception in thread “Thread-1” java.lang.NullPointerException
    at com.backup42.service.backup.BackupController.stop(BackupController.java:1108)
    at com.code42.backup.BackupManager.tearDown(BackupManager.java:278)
    at com.backup42.service.backup.BackupController.tearDown(BackupController.java:596)
    at com.backup42.service.CPService.cleanup(CPService.java:2050)
    at com.backup42.service.CPService$1.run(CPService.java:424)

    Has anyone else seen this and found a solution?
    There is no upgrade stuck in progress after the fresh install. And after the first try (auto update 4.5.2) I followed the earlier in this blog mentioned solution without success. Now it doesn’t even start as far as getting the update files… stuck on 4.5.0.

    Reply
    1. Joerg W.'s avatarJoerg W.

      I was able to get back on track by uninstalling crashplan, restarting and reinstalling it. after a while the update took place, failed and could be fixed using the above mentioned procedure. Pain in the a… but backing up again. I really wish, CP would become officially supported. But that would attack their own Server Solutions, I guess… Thanx anybody out here for sharing their ways!

      Reply
  43. RHC's avatarRHC

    I had the same “Synology repairing update in” again.

    I solved it by running these steps:

    1. SSH to your DiskStation as root.
    2. “cd /var/packages/CrashPlan/target/upgrade“
    3. “ls -la“
    4. At this point you should see some directories that look something like “1435726800452_78.1452788381212“
    5. “rm -r ./1435726800452_78.1452788381212“
    6. Repeat for all BUT ONE of the directories
    7. Go back and start the CrashPlan Service/App ( I had to start it 2 times before it worked)

    Reply
  44. smudgespot's avatarsmudgespot

    Having a similar issue as Joerg. CrashPlan package 4.5.0-0036 fresh uninstall/reinstall fails to start. The only log entry is in the engine_err.log file of
    Exception in thread “main” java.lang.UnsupportedClassVersionError: Unsupported major.minor version 51.0
    Is this version error in reference to java? I’m using the java 1.6.0_38 embedded as detailed in the main post. Perhaps java 6 isn’t supported with CP 4.5? Is it ok to upgrade the embedded java to 7 or even 8?

    Thanks

    Reply
      1. smudgespot's avatarsmudgespot

        Thanks for the confirmation. I have just upgraded to Java 7 and CrashPlan 4.5.2 and everything appears to be running properly again.

  45. Mark Venn's avatarMark Venn

    As I was daft enough to push the beta of DSM6.0 onto my DS412j, I’ve been unable to use some of the workarounds as I cannot yet figure out the 7z equivalent syntax for the unzip command! That said, for both 4.5.0 and 4.5.2, what worked for me was stopping the package, uninstalling and reinstalling. The upgrade completed in place – after a few minutes – and once .ui_info had been appropriately edited, all was good. I did not lose any of the files which had already been backed up to CrashPlan Central.

    Reply
  46. Dale's avatarDale

    After applying the fix that usually helps with the update, namely unpacking the upgrade files and deleting duplicate folders, I still couldn’t get the backup to work again, but the new 37 package worked great. I also noticed that in the changelog, it lists 36 twice instead of mentioning 37, and also has an incorrect date as January 21 2015 as opposed to 16. Hopefully those typos will be spotted (or noted from this comment) and handled. Other than that minor point, nice job with the latest package!

    Reply
  47. semperfidelis's avatarsemperfidelis

    Thanks for releasing the update so quickly. Updated from the Package Center and it works flawlessly.

    Reply

Leave a reply to mkchronos Cancel reply