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. david's avatardavid

    I have a ds 212 that I have installed the regular crash plan. I already have crash plan installed and backing up my macbook air. If I do this step:

    Once the engine is running, you can manage it by installing CrashPlan on another computer, and editing the file conf/ui.properties on that computer so that this line:
    #serviceHost=127.0.0.1
    is uncommented (by removing the hash symbol) and set to the IP address of your NAS, e.g.:
    serviceHost=192.168.1.210

    Will crash plan start backing up the Nas and stop backing up the macbook air or will it allow me to backup both?

    Reply
    1. patters's avatarpatters Post author

      You can do both. The backup engine and the management client are completely separate, you’re just viewing the engine’s settings with it.

      Reply
  2. hammer's avatarhammer

    Thanks for a great package for the Synology!

    I’m running a DS209 (ARM CPU with 256MB memory) and have been investigating the hibernation problems when running CrashPlan 3.2.1 and I’ve found a solution that works for me.

    I hope others will try this out and report back their findings.

    I only backup to “CrashPlan Central” (Cloud) and have inbound backup disabled. My hard drives hibernate after 20 minutes of idle.

    I’ve made the following changes

    1. Symlink “log/app.log to “/tmp” (tmpfs filesystem so the file will probably only be written to RAM) as the application occasionally updates “log/app.log” even when CrashPlan is doing nothing.
    Run the following commands:
       rm /volume1/@appstore/CrashPlan/log/app.log
       ln -s /tmp/CrashPlan_app.log /volume1/@appstore/CrashPlan/log/app.log 
       chown -h crashplan:users /volume1/@appstore/CrashPlan/log/app.log
    2. Edit “/volume1/@appstore/CrashPlan/conf/service.log.properties” to prevent “log/service.log.0” to be written constantly with a lot of unneeded messages. Set all existing log-levels to WARN or OFF (see below).
    3. On all backup sets: Disable “Advanced settings (Configure)” -> “Watch file system in real time”.
    4. Mount volumes using noatime (http://forum.synology.com/wiki/index.php/Spindown_issues).

    An alternative to 1. is to symlink “log/app.log” to “/dev/null” (ln -s /dev/null /volume1/@appstore/CrashPlan/log/app.log) but this creates error messages in the “log/service.log.0”. The errors can be muted by adding “log4j.logger.com.code42.logging.AppLogWriter = OFF” to “conf/service.log.properties”.

    Here’s my complete “conf/service.log.properties”:

    #############################
    # Backup log.properties
    # Code 42 Software, Inc. 2005
    #############################
    log4j.rootLogger=WARN

    # Package Level modifications
    log4j.logger.com.backup42.service.ui.UIServer.level = WARN
    log4j.logger.com.backup42.service.ui.UIClientExitedCheck.level = OFF

    log4j.logger.com.code42.backup.level = WARN
    log4j.logger.com.code42.peer.level = WARN
    log4j.logger.com.code42.peer.PeerConnector.level = WARN
    log4j.logger.com.code42.peer.NATContinuation.level = WARN
    log4j.logger.com.code42.os.level = WARN
    log4j.logger.com.code42.io.level = WARN
    log4j.logger.com.code42.event.level = WARN
    log4j.logger.com.code42.messaging.level = WARN
    log4j.logger.com.code42.nio.level = WARN
    log4j.logger.com.code42.win32.level = WARN

    #Only if symlinking app.log to /dev/null
    #log4j.logger.com.code42.logging.AppLogWriter = OFF

    Reply
  3. johnyyc25's avatarjohnyyc25

    So is it safe to upgrade to DSM 4.1 now? Last time I upgraded I had to downgrade back to 4.0 in order for CrashPlan to run.

    Also great work patters!

    Reply
  4. Michael Maillot (@Mmaillot)'s avatarMichael Maillot (@Mmaillot)

    Hi Patters,

    I have been using Crashplan on Synology NAS first on my 207+ then on my 212+ successfully for a few months now.
    I am currently experiencing an issue and have been trying to fix it thanks to other users comments on this article, but unfortunately I have not been successful.

    NAS: 212+, DSM 4.1.2636
    CP: latest version to date, 3.2.016
    Java : 7, latest version to date, 1.7_06-12
    The issue :
    – until last week, my backups to CP Central from NAS went perfectly fine – more than 350Gb of data sent (mainly TimaMachine “bands”)
    – I wanted to add a new folder to be backed up (excluded up to now)
    – result :
    + the backup keeps being stuck to “backup running” status
    + yet, CP does not upload any data to CP central. So is stuck to the same file
    + more strange: CP stops every 6 minutes or so, thus the client is disconnected every 6 minutes. During those 6 minutes, Java takes all the CPU resources it can (almost 100%)

    I temporarily removed back the folder I wanted to add to the backup -> OK.
    Since then, a few TimeMachine “bands” have been added in the backed up folder and have the same issue again.

    It tried to uninstall / reinstall CP package several times, same with Java, but I still have the issue.
    I also opened a ticket on crashplan.com, but as I expected I had the “not supported” answer by the customer service agent.

    I looked at the logs, but found nothing that can help a noob like me. I tried to find some Java errors that might point at the heap size issue you mentioned earlier, but there is nothing explicit about it in the logs.

    The only error I get in the service.log is the following one “com.code42.io.DataFileClosedException: BplusTreeIndexFile is closed!”. But it does not appear every 6 minutes, so I am not sure this is the root cause of the issue I have.

    Does anyone else has such an issue?

    Michael.

    Reply
      1. John B's avatarJohn B

        I’d make sure to restore any invaluable data to another computer as a complete loss of your backups is a possible worst-case scenario.
        Then I’d try adopting your old data using a clean install.

        Also, you should go through their support documents and see if anything is relevant for you.
        For example, I’d make a note of the GUID before starting:
        http://support.crashplan.com/doku.php/client/manual_commands
        and read up on adoping:
        http://support.crashplan.com/doku.php/recipe/adopting_another_computer

        Then I’d uninstall CP (including your computer), uninstall Java, remove any left-over CP files, reboot and make sure your NAS still works as it should.

        Then perform a new install using the steps above ending with the adoption of your old backup data.

  5. Chris's avatarChris

    Thank you for the great work with this Synology Crashplan package. This does exactly what I was looking for. I’ve been relying on it for a few months now and it works flawlessly.

    Reply
  6. MIke's avatarMIke

    Hi, I’m slightly confused. Should I install the CrashPlan Proe Client or CrashPlan Pro? Assuming I want to backup my DS412+ to using the CrashPlan+ Unlimited plan.
    Thanks

    Reply
      1. MIke's avatarMIke

        Thanks for the reply. I figured it out. For some reason the CrashPlan+ icon didn’t appear initially, just the Pro and the Proe. But it’s all working now, so I’ll use the affiliate link above the buy CP as it’s just what I was looking for.

  7. JS's avatarJS

    Hello: I have Crashplan installed on a NAS server and I connect to it through a Windows 7 client. To my surprise, when I add the folders I want to index for the backup, the count/size is wrong, it shows 1file/0mb rather than the reasl size/space. I tried to reset/reinstall/remove/etc… everything but the problem still remains and it is now always related to the same folder. I am wondering whether it has something to be with “fs.inotify.max_user_watches” or “ulimit” or ….
    Thanks in advance for your help.

    Reply
  8. Bart's avatarBart

    Hi Patters!

    I am trying to start Crashplan via a cronjob. It seems not to work. When I am using CLI directly, this will result in the following:

    DiskStation> /var/packages/CrashPlan/scripts/start-stop-status stop
    /var/packages/CrashPlan/scripts/start-stop-status: source: line 17: can’t open ‘/install.vars’

    Is this even possible to do this directly into Cli? And if, whats the error message about?

    I hope you can help me with this? Thans in advance.

    Reply
    1. patters's avatarpatters Post author

      That should just work, version 015 or later of my package introduced a fix for this, and it definitely works with cron on my syno. Are you running the latest version?

      Reply
      1. Bart's avatarBart

        Yes You are very right! Missed an update deu to repository URL change. Thank you very very much!

  9. Marten's avatarMarten

    OK so an update just ruined my crashplan on synology.

    It seems crashplan downloaded 1349845200340.jar into a directory called ‘upgrade’
    then unpacked it to 1349845200340.1352421877038
    And then tried to install it, but that failed. According to upgrade.log:

    /volume1/@appstore/CrashPlan/upgrade/1349845200340.1352421877038 # less upgrade.log
    ======================================================
    Thr Nov 8 16:44:37 PST 2012 : /volume1/@appstore/CrashPlan/upgrade/1349845200340.1352421877038/upgrade2.sh
    Thr Nov 8 16:44:37 PST 2012 : Current CrashPlan Backup Engine:
    Thr Nov 8 16:44:37 PST 2012 : Delete existing SLF4J jars if they exist…
    Thr Nov 8 16:44:37 PST 2012 : Removing old jar files…
    Thr Nov 8 16:44:37 PST 2012 : Moving existing native libs from lib to app dir…
    mv: invalid option — v
    BusyBox v1.16.1 (2012-05-10 02:47:50 CST) multi-call binary.

    Usage: mv [OPTIONS] SOURCE DEST
    or: mv [OPTIONS] SOURCE… DIRECTORY

    Rename SOURCE to DEST, or move SOURCE(s) to DIRECTORY

    Options:
    -f Don’t prompt before overwriting
    -i Interactive, prompt before overwrite

    basically mv -v doesn’t work on busybox. Maybe with ipkg I could’ve installed a better move but I didn’t.

    Suggestions?

    Reply
    1. Mansoor Seikh's avatarMansoor Seikh

      I was having same issue. Even tried reinstalling but that didn’t work. Then I copied the missing file “com.backup42.desktop.jar” to /volume1/@appstore/CrashPlan/lib from my desktop copy of Crashplan while CrashPlan was attempting to restart and then it worked. Its just a temporary solution because if I try to restart, it will go back to upgrade script and will delete this file again. As of now, my crashplan is working.

      Reply
    2. Dan's avatarDan

      Hi, I have exactly the same problem. I have also tried uninstalling and reinstalling and have had no more luck. Please let me know if there is a workaround or fix.

      Reply
    3. Kai's avatarKai

      Well, i can confirm that the upgrade kills crashplan on my 1512+.
      Sadly my Linux-Knowledge ends after a bit of cd, chmod and cat so i can’t help you and myself. :(

      Reply
    4. Richard's avatarRichard

      Same here! Crashplan downloaded an update, then will not start saying its trying to repair the upgrade. Uninstalled the package and reinstalled, but this seemed to download the old version of Crashplan, which then immediately downloaded and installed the upgrade, which again failed!! HELP!!!

      Reply
      1. Leigh Harrison's avatarLeigh Harrison

        This appears to be the same problem I’m experiencing on my DS112 running DSM3.2. CrashPlan’s been 100% reliable until now. However …

        My NAS has just downloaded and installed upgrade 1349845200340 and tells me I now have CrashPlan version 3.2.008 installed. CrashPlan hasn’t started and won’t start when I attempt to run it from the Package Centre.

        The final entry in the Package Centre’s activity log is “CrashPlan stopped”.

      2. Allan's avatarAllan

        Same experience for me. Was experimenting crashplan to crashplan backup, when I suddenly had strange errors and a nonresponsive crashplan on my synology. Noticed it had stopped running, and wouldn’t start again. Removed package and reinstalled. All looked good for a minute or so but then again. Stopped running. Refered to this page and now I see i’m not the only guy in this boat.
        Thanks for a great package, hopefully a fix or suggestions is avaiable soon. Thanks!

    5. Adam's avatarAdam

      Add me to the list of ppl who’s CrashPlan stopped working. Same thing, downloaded an update automatically on Nov 8th and now CrashPlan won’t start on the NAS.

      Looking forward to a solution :-)

      Reply
  10. Gijs's avatarGijs

    I have installed crashplan and Java 7 on my DS109 nas, I restarted the package and changed: conf/ui.properties as mentioned. When i start the crasplan program on my pc, it tells me that it cant connect to the backup machine.
    I’ve tried restarting and reinstalling but nothing works. I might just have missed some small setting but i cant figure what.
    Can somebody help me with this?

    Reply
    1. Gijs's avatarGijs

      I tried it again with the new package but it still doesnt work. I get the same message when i start the crashplan software on my computer.

      Reply
      1. Gijs's avatarGijs

        After the new version came out yesterday, i deinstalled the package from my NAS and installed the new version. I I waited a few minutes and restarted the package and then tried to connect it from my pc. It then show the crashplan splash-screen, and after a while it show the message: Cant connect to backup machine, try again? Yes/no

      2. Gijs's avatarGijs

        I have tried to connect the package with ssh tunneling with putty, and that didn’t work either. I could log in, but when i tried to confirm with telnet, i didn’t get a successful connection. I tried it also with my firewall off but that didn’t work out either. Its obvious that i am not very familiar with this matter, but I thought i could figure it out by following the instructions. That is probably where the problem lies, but i retraced my steps and retried it multiple times but i can figure it out.
        Help is very welcome.

  11. Jake's avatarJake

    Thanks for the great package! I believe I have experienced a similar problem to the one from Marten.

    Crashplan was not running this morning, and I did a little exploring, upon my attempt to reinstall, CP was working, allowed me to enter the login screen on my PC, and then it showed a line of red text reading something like “installing new updates”. When that was complete, CP would not run on my diskstation anymore.

    I am running the latest DSM on a DS413

    Thanks for any help or suggestions!

    Reply
  12. Mansoor Seikh's avatarMansoor Seikh

    I was having same issue. Even tried reinstalling but that didn’t work. Then I copied the missing file “com.backup42.desktop.jar” to /volume1/@appstore/CrashPlan/lib from my desktop copy of Crashplan while CrashPlan was attempting to restart and then it worked. Its just a temporary solution because if I try to restart, it will go back to upgrade script and will delete this file again. As of now, my crashplan is working.

    Reply
  13. Grahame's avatarGrahame

    I had the same problem and appear to have fixed it by modifying the upgrade.sh file in /volume1/@appstore/CrashPlan/upgrade/1349845200340.1352421877038

    At the top of the file is a section with the rm and mv commands. I changed these to:

    RM=”rm -f”
    MV=”mv -f”

    Thne chmod+x on upgrade.sh and run it as root.

    It ran through and then looped with errors about wrong parameters on ps. That appears to be just from attempting to restart it after the upgrade is done, so I killed the script and then manually restarted CrashPlan from the package center.

    Reply
  14. Sebastian's avatarSebastian

    Hi.
    thx for the work.
    After running for 2weeks i have a serious problem

    Crashplan Service dosent start any longer.
    The Log at Pakacke Center writes:
    Synology repairing upgrade in /volume1/@appstore/CrashPlan/upgrade/1349845200340.1352423914711

    I restartet. It doesent help.
    I tried the start script via ssh

    With this console output:
    rm: can’t remove ‘/volume1/@appstore/CrashPlan/CrashPlanEngine.pid’: No such file or directory

    Please help.
    It is a good idear to uninstall and install again? I need 2 weeks for 200GBs backup ;-)

    Reply
    1. Marten's avatarMarten

      Ah, I think I see the problem.

      /volume1/@appstore/CrashPlan/upgrade/1349845200340.1352421877038/upgrade.sh (is this the exact same path for everyone?)

      contains:

      #!/bin/sh
      MV=”mv -fv”

      #1 runs ‘busybox’ and overrides my actually installed coreutils-mv

      Since I’m lazy I prefer patters to fix it in his (I presume he has.. ) test setup rather than experiment with my own live setup and perhaps break it more.

      But, if you can’t wait, I think either changing line 1:
      #!/bin/sh
      to
      #!/opt/bin/bash

      Or changing line 2
      MV=”mv -fv”
      to
      MV=”mv”

      And then calling upgrade.sh will fix it.

      Reply
      1. Marcus's avatarMarcus

        For me the path is different and looking at the script I can see that MV is already set to “mv -f”.

        On my end the uprade fails with another error: It says it can’t dinf a jar file:

        Sat Nov 10 13:45:20 Europe/Amsterdam 2012 : Restarting CrashPlan Backup Engine…trying again 10
        Sat Nov 10 13:45:20 Europe/Amsterdam 2012 : Sourcing ../../install.vars…
        Sat Nov 10 13:45:20 Europe/Amsterdam 2012 : Stopping using ../../bin/CrashPlanEngine…
        Could not find JAR file ../../bin/../lib/com.backup42.desktop.jar
        Sat Nov 10 13:45:20 Europe/Amsterdam 2012 : Sleeping 10 seconds…
        Sat Nov 10 13:45:30 Europe/Amsterdam 2012 : Starting using ../../bin/CrashPlanEngine…
        Could not find JAR file ../../bin/../lib/com.backup42.desktop.jar
        Sat Nov 10 13:45:30 Europe/Amsterdam 2012 : New CrashPlan Backup Engine:
        Sat Nov 10 13:45:30 Europe/Amsterdam 2012 : Exiting upgrade script

      2. James's avatarJames

        I tried changing it like that earlier, and it didn’t fix it for me… the script ran but then crashplan wouldn’t start. Haven’t investigated further

  15. Mike's avatarMike

    I had an issue when the synology found a new crashplan update was available and tried to auto update to it. It wasn’t able to get past the repair install step. After trying to reboot, uninstall, reinstall, it kept failing to start.

    Can you update the package to so it will download the most current update (http://download.crashplan.com/installs/linux/install/CrashPlan/CrashPlan_3.4.1_Linux.tgz). I was able to download it, rename it to what your package was looking for, 3.2.1, and put it in the public folder. That reinstall worked, and since it was already up to date, the update didn’t fail.

    Also, is there any way to prevent the auto-update??? I have used your package on a few production synology servers and after each auto-update, the service stops and doesn’t auto restart.

    Thanks,
    Mike

    Reply
      1. mikestreb's avatarmikestreb

        Thanks Patters! Update seems to have fixed the issues I have encountered on both of the 1512+ I am running with Crashplan.

        Is there anyway to have the Synology email me when crashplan auto updates, so I can check on it?

        Thanks for the fast update and the fantastic package!
        Mike

      2. patters's avatarpatters Post author

        Not really – there’s no way of knowing when an update gets pushed by Code 42. However, you’ll get the CrashPlan Backup status email after a few days with a warning that the backup has been failing, so you wouldn’t miss it.

  16. Stephane's avatarStephane

    Ok, this is good for me. Thanks Patters.
    I do not understand that the updates for synology do not take place through the repository rather than automatically without mastery of the user.
    Do you know or disables the update? I tried to change the value in ui.properties (url, upgrade=false…) but without success.

    Reply
  17. ronald's avatarronald

    I have the same problem on my Synology 212+
    I can not start crashplan anymore.
    Is there a solution to fix it, I am a newbee

    Reply
  18. patters's avatarpatters Post author

    Ok, I’ve done some careful testing and I’ve spotted the problem. My exisiting start-stop-status.sh script is correctly fixing up the rm, mv and ps syntax in Code 42’s update script, but it wasn’t renaming that script once executed. After the upgrade the service binding in conf/my.service.xml resets to the loopback adapter (127.0.0.1). The package needs another restart before that binding is reset to 0.0.0.0 to allow remote CrashPlan console connections, but start-stop-status.sh was launching the upgrade script again, wiping out the JAR file and breaking the package. Just a little more testing and I’ll publish the new version.

    Reply
    1. Marten's avatarMarten

      Should one just uninstall-reinstall crashplan to fix this? (when you publish your new version)?
      Thanks for your work ;)

      Reply
  19. patters's avatarpatters Post author

    Future updates should work ok now too, but the package will need a manual restart following upgrade before you can connect the Desktop CrashPlan client. I’ll update the notes…

    Reply
    1. aTc's avataraTc

      Thanks a million for this latest update. I had *just* installed your package a day and a half for the first time, and was worried when it stopped working so soon. I thought I’d found a questionable package. But not only is it working again, you fixed it remarkably quick. Must have just been really coincidental timing. I plan to give it a few more days to make sure it continues to work, but then I have every intention of donating to your cause. Thanks!!

      Reply
  20. leighelse's avatarleighelse

    It’s good to hear there’s a fix for this issue. What do I need to do to apply it?

    Should I uninstall and reinstall your CrashPlan package on my NAS? Or should I try the various edits suggested in the above comments?

    I’ve looked through the comments and the notes on this page but I can’t find any instructions, just the tantalising comment that there is now a fix.

    Reply
      1. leighelse's avatarleighelse

        No, the Package Centre doesn’t offer an update at this point.

        I’m happy to uninstall/reinstall if that would resolve it. And I’m happy to wait if the update needs time to propagate or be detected.

        Thanks for addressing the issue so quickly anyway.

      2. leighelse's avatarleighelse

        Interestingly when I now click “Run” for the CrashPlan package, I’m greeted with a error message that says “Another package is being configured or installed. Please try again later”.

        If this is still the response in an hour or two, might it be advantageous to restart the NAS?

      3. leighelse's avatarleighelse

        A reboot did remove the “package being configured or installed” message, but didn’t provide an update button. I uninstalled but found the package didn’t reappear in my “Other sources”.

        Only then did I figure out that your download URL has changed since I first installed CrashPlan on the NAS. After editing the URL and reinstalling CrashPlan, it runs, stops, restarts … the whole box of tricks.

        Thanks for your help.

      4. patters's avatarpatters Post author

        Yeah sorry about the repo move. I had wanted to make it clear by publishing a dummy package with a note to update the URL, but the old webhost blocked my account unfortunately. Glad you’re back up and running.

      5. Marten's avatarMarten

        It did. I used to be at .comlu or something.

        But, after updating (succesfully) it didn’t actually work yet. Do note I haven’t updated my Java yet, so will try updating ejre.1.6… but just as a small data point

  21. Charles's avatarCharles

    Thanks for making update 17 available. My crashplan stopped working after the latest update to either dsm or crashplan. I updated Java and Crashplan, but nothing worked. After a day of being lost as to what to do next, I saw the update button for your package. Thanks for doing a great job maintaining it for those of who are less technical, but still need Crashplan for our Synology NAS.

    Reply
  22. Nogger's avatarNogger

    Hi Pattern,

    thanks a lot for your quick help.
    Since nearly 3 weeks CrashPlan was running on my DS213+ and it worked perfect until the upgrade….no it is running again with your help. Thanks a lot!

    I just made a donation, because your help is always welcome and I also will subcribe to CrashPlan at end of my trial through your ” this affiliate link”.

    Regards
    Nogger

    Reply
  23. Ephesian's avatarEphesian

    Thanks for the package! My only problem is SLOW upload speeds. I am on a 50/25 Mbps Fios line, and uploads to Crashplan are only 1.5 Mbps (I have otherwise seen the NAS upload at up to 35 Mbps). On my DS212 (underpowered, I know) I have all sending rate limits set to “none” and a max CPU utilization set to 80% in both away and present modes. The “java” process uses up to ~90% CPU and uses 92.3 MB RAM. Total RAM utilization is 84% of 256 MB (215 MB) but the resource monitor numbers don’t seem to add up to that. The other packages I have running are Logitech Media Server, Antivirus Essential, and VPN Server.

    Is this normal? Any way to increase the speed? Is it a CrashPlan problem or a Synology problem?…

    Reply
  24. CrashNewbie's avatarCrashNewbie

    Hi,

    I have installed the Client on my DS 1512+ and it works fine.

    But when I want to upload in the Cloud from my DS to the CrashPlan Cloud the folder shows me only 5 KB and 5 Files?!

    Can you tell me what is wrong?!

    Thanks for your help

    Reply
  25. Gaunts Ghost's avatarGaunts Ghost

    Hi

    I am running this on a DS212j.
    When the program is backing up it uses around 90% of the processor and around 75MB RAM. It uploads also at about 1,5 Mbps regardless of my 10 Mbps connection.

    All of that I can live but but it does worry me a tad, that the RAM usage is the same even if the backup is not running. Is it possible to build in a way to start/stop the package into the program?
    I tried limiting the time that Crashplan should be running but there doesn’t seem to be a difference in the RAM usage.

    I would also like to say thank you for making this great package, it’s greatly appreciated. Please do not consider my comments as a criticism, but rather as feedback.

    Reply
    1. patters's avatarpatters Post author

      That speed is in line with what you cam expect from CrashPlan, regardless of your connection. For scheduling the start/stop read the section about using cron on this page.

      Reply
      1. Gaunts Ghost's avatarGaunts Ghost

        Great, thanks for the hint.
        So I will add:
        55 2 * * * root /var/packages/CrashPlan/scripts/start-stop-status start
        0 4 * * * root /var/packages/CrashPlan/scripts/start-stop-status stop
        with the config file editor.
        What if I want the time to be PM, would that be 00 13 * * *?

        I would still need to restart cron with ssh right? That cannot be done any other way?

      2. Marcus's avatarMarcus

        I usually have something of around 2 Mbit/s. Sometimes it goes up to 4 oder 6, but it doesn’t sustain that speed unfortunately. After running for a while the upload drops down to a crawl which can only be fixed by restarting CrashPlan. As someone else observed this as well?

  26. CrashNewbie's avatarCrashNewbie

    I have a Question:

    The default location for saving friends’ backups is set to /volume1/crashplan/backupArchives (where /volume1 is you primary storage volume) to eliminate the chance of them being destroyed accidentally by uninstalling the package.

    I found this Backups from my Friends in this location, but Why I can’t save these Folder in my ClashPlan Central?!

    When I select the Folder on my Nas – Backup -> Files -> Select , I see only 5 Files / 1 KB.

    Why that is so?! I hope someone can helps me. Regards

    Reply
  27. Cavedweller's avatarCavedweller

    I think its working on my DS212, but Two Questions:

    1) If I use Crashplan UI to view headless engine on my DS212, and create a couple of backup sets and put them on a schedule, once I disconnect Crashplan UI from the NAS headless engine, will the sets & schedules remain and continue to run as such on the NAS? (I guess I’m not sure why one would need to use Cron for editing schedule if it can be done via the UI?)

    2) I am trying to connect my Crashplan program to the NAS engine remotely, from outside the network, but not having any luck. Do I need to forward any ports (22, 4243) in the router? I am not sure which user name I need to use for ssh when forwarding port 4200 in terminal with “ssh -L 4200:localhost:4243 yourusername@NAS IP” and what about the password for that user name?

    Thanks to anyone who can help!

    Reply
  28. IneedHelp's avatarIneedHelp

    Hi,

    has someone tried to send the Friends Backups to CrashPlan Central?!

    I have some friends how Backups his Clients to my DS1512+ This works fine. I can see the Backups on my NAS.

    When I try send the Backups to CrashPlan Central, I can’t select it. I see the files when I checkBox the hidden Files option, but these files I can’t send to CrashPlan Central.

    So what’s going wrong?! Maybe someone can helps me.

    Best regars

    Reply
  29. IneedHelp's avatarIneedHelp

    One More Question. I must install the Synology NAS GPL Source or DSM 4.1 Tool Chains. Or I don’t need this?!

    Reply
  30. CrashNewbie's avatarCrashNewbie

    Today I have received this Answer from CrashPlan:

    CrashPlan automatically excludes other CrashPlan backups, so you won’t be able to use CrashPlan to backup the Macbook Air to the NAS and then send those backups from the NAS to CrashPlan Central. You would need to use some other method to transfer the files from the MBA to the NAS directly, then have those files in the NAS’s file selection.

    So these means that I can’t Save my Clients on my NAS and then I send the Backups to CrashPlan Center Cloud?!

    Or is this working by someone?!

    Regards and thanks for your help

    Reply
    1. Grant's avatarGrant

      I believe crashplan does this so you don’t just mbuy a single user license then back up all computer to one computer to upload to crashplan cloud. Basically they aren’t going to make it easy to circumvent their multi-computer license.

      Reply
    2. Jake's avatarJake

      The reason you cannot use other CrashPlan backups is because you could backup numerous computers to a central location and then backup all that data to crashplan, bascially getting around their different paid plan levels. I would not expect crashplan to support a workaround built into their own software which would remove the need to buy a license to backup multiple computers. I am not sure if higher levels of crashplan membership allow for this, but the way I get around it (to backup two of my personal computers) is to sync your files to your diskstation with a program such as synctoy, cobian backup, or the numerous other file sync/backup programs.

      Hope this helped!

      Reply
      1. CrashNewbie's avatarCrashNewbie

        Thanks for your reply. I think like you, but here someone write these:

        I’m backup my clients also with CrashPlan, but not in the CrashPlan data center, but on the NAS (in the CrashPlan client to configure this, just the backup to another computer, in this case my Synology (this makes it so then the backup in the Cloud). So you don’t need a CrashPlan Family account for multiple computers and also saves you money.

        This i have found here: http://hoffmanns-cloud.de/synology/backupkonzept/

        And now I am a little bit confused. But this would be very nice. But I think that this is not possible.

    3. patters's avatarpatters Post author

      To allow that would fundamentally undermine CrashPlan’s revenue model so it’s hardly surprising. Just have your friends buy CrashPlan+.

      Reply
      1. richard's avatarrichard

        Indeed, use a multi user license, or let your friends get a license of their own. It’s not the money that will be the bottleneck i think??
        And for the extra/cross backups let them use your nas and you use theirs.

        If it is to backup an extra folder of documents on your desktop or something, you maybe can mount that folder from your nas to the desktop and backup that folder as a local nas volume.
        It works, but has a lot of overhead and every time you reboot the desktop you need to remount the folder.

      2. Erik's avatarErik

        I have all my documents and important stuff on my Mac in my Cloud Station folder. Then on the NAS I back up the Cloud Station folders to CrashPlan. Very simple and very effective.

  31. Mercury's avatarMercury

    Great work – have successfully installed and am running Crashplan back up engine from my PC onto the Synology NAS.
    Just one question – I’m looking at Filestation on Synology (via DSM), and wondering where the actual backup file is created / stored?

    Reply
  32. Duane's avatarDuane

    Thanks for the work. I have a new / weird issue. When I click on change button in the client to change the folders being backed up it stays stuck on loading in the change file Selection window. I have restarted everything to no aviail…..thoughts?

    Reply
      1. petera180's avatarpetera180

        Hi

        I had exactly the same problem although I was running the same version of Crashplan (3.4.1)on both PC and NAS.

        Crashplan’s helpdesk were as helpful as they could be, but I could not relate the advice they gave to my installation (I’m no Linux expert!) and they ended by stating, “We don’t support Crashplan installed on a NAS.”

        However, Nogger’s great advice set me on the right track. I uninstalled Crashplan on my PC; downloaded the latest version from Crashplan’s site and installed it – and all is well.

        It seems that Crashplan’s built-in self-update routine somehow does not do quite the same update job as a completely fresh installation.

  33. Maik's avatarMaik

    I’m trying to install CrashPlan from the Package Center, but it seems to hang during the installation. When I check my processes, I see a ‘wget’ downloading a file from the CrashPlan-website, but this process is sleeping. I guess this is the reason the installation hangs?
    Is there anything I can do about this?

    Reply
    1. Maik's avatarMaik

      I managed to install it by downloading the file myself and putting it into the public-share.
      But now I don’t see any files in the ‘Change File Selection’ dialog on the Windows 7 Client.. What could be wrong here?

      Reply
  34. Adam's avatarAdam

    I upgraded the Synology CrashPlan package from 3.2.1 to 3.4.1 today. Thanks for your hard work porting 3.4.1 over to the Synology platform so quickly! I truly appreciate it! During the install, I noticed that the user crashplan was deleted and then re-created. Is this typical behavior?

    Of course, when the crashplan user was deleted, it deleted /volume1/crashplan/backupArchives folder. My remote machines have now begun the process of pushing data back to my Synology. Would you advise moving the inbound backup folder out of /volume1/crashplan/ so this doesn’t happen again in the future?

    Reply
    1. patters's avatarpatters Post author

      That path is not trashed, either by uninstalling or upgrading. That’s the whole point of using that folder and not the crashplan user’s home directory which is /var/services/homes/crashplan.

      Reply
      1. Adam's avatarAdam

        A ha! I found the problem. For some reason, my backupArchives directory is in /volume1/@appstore/CrashPlan instead of /volume1/crashplan. Not sure how that happened, but I’m changing it now.

      2. patters's avatarpatters Post author

        Hmmm. It’s possible the upgrade from 3.2.1 to 3.4.1 caused the xml config to be reset back to defaults. I didn’t really want to over-ride it in case the end user had customized it. I guess I’ll have to make the script check the value, and if it’s within /volume1/@appstore/CrashPlan then force it back to /volume1/crashplan, else leave it alone.

  35. GuitarManDave's avatarGuitarManDave

    At Crashplan support’s suggestion I’m trying to increase the heap size allocated to the Crashplan java process by changing the default Xmx=192m value in @appstore/CrashPlan/bin/run.conf.

    The problem is that as soon as I restart the package the contents of this file is overwritten and for the life of me I can’t figure out what script is overwriting it or how to prevent it.

    Please help!
    Thanks

    Reply
  36. chreggy's avatarchreggy

    Hi everybody !
    I finally finished the PowerPC e500v2 guide and I can announce that SPK PACKAGES are available for this hardware !

    Many hours of time and a good inspiration from pcloadletter install.sh to finalize the packages.

    If you want, you can link my web site.

    Reply
  37. May10's avatarMay10

    Hello,

    I had my CrasPlan working but since the update, the process is not listenning.. When i do netstat i don’t see it. But the process is in the “launched” state on Synology and i see it in the process list. My logs files are empty.. any idea ?

    Thanks a lot !

    Reply
    1. scontreras's avatarscontreras

      I am having exactly the same issue, except that for me the process doesn’t even seem to run on the NAS. When I try to run it via the DSM Package Center I get the message “Wait a few seconds, then stop and restart to allow desktop client connections.” But the package never starts. Logs are empty.

      Any ideas?

      Reply
  38. mikestreb's avatarmikestreb

    Have a weird issue that isn’t the end of the world if I can’t figure out, but it is bugging me. I have two 1512+’s. One has just a single RAID volume and the other has two volumes (1 is RAID and 2 is a single disk I use for Time Backup). On the one with two volumes, I installed crashplan on Volume1. Now I am trying to backup a couple folders from the single-volume 1512 to the two-volume 1512. For whatever reason, it made the ‘location to backup friends files’ volume2/crashplan/backupArchives instead of on volume1. Not a big deal, but I would rather the backups be on the RAID volume and not the single disk volume. Any way to easily change that without having to create another share folder? Should I just create those folders in volume1 using ssh? Would I need to setup any permissions if I did that? Any chance of this screwing things up? Thanks again for all of your help. Mike

    Reply
    1. patters's avatarpatters Post author

      I think the Syno will create the @tmp folder on the drive with the most free space. My scripts use that to located the drive too, and so it won’t be easy to change unfortunately.

      Reply
      1. mikestreb's avatarmikestreb

        Both of the volumes have an @tmp folder. Volume1 has 3.5+ TB of free space while Volume2 (where it is putting the backupArchives) only has 1.5TB free. I tried to SSH in and just create the folder in Vol1, but I think the permissions are wrong for that to work. Crashplan said something along the lines of ‘backup location not available’.

  39. Stefaan's avatarStefaan

    Hi,

    Thanks for the great package. As many of the other users I have had issues since upgrading to DSM 4.1. However, I am not able to resolve them with any of the suggested ways in the comments. WHen I hit run, I can’t get the package to start. I looked in the logs: nothing in there. Was wondering, does CP need it’s own user in DSM? I seem to remember I saw one there in the past. When I look now there is none anymore. Any help greatly appreciated.

    Reply

Leave a reply to Chris Cancel reply