Copyright (c) 2006-2014 MindTouch Inc.
This file and accompanying files are licensed under the MindTouch Master Subscription Agreement (MSA).
At any time, you shall not, directly or indirectly: (i) sublicense, resell, rent, lease, distribute, market, commercialize or otherwise transfer rights or usage to: (a) the Software, (b) any modified version or derivative work of the Software created by you or for you, or (c) MindTouch Open Source (which includes all non-supported versions of MindTouch-developed software), for any purpose including timesharing or service bureau purposes; (ii) remove or alter any copyright, trademark or proprietary notice in the Software; (iii) transfer, use or export the Software in violation of any applicable laws or regulations of any government or governmental agency; (iv) use or run on any of your hardware, or have deployed for use, any production version of MindTouch Open Source; (v) use any of the Support Services, Error corrections, Updates or Upgrades, for the MindTouch Open Source software or for any Server for which Support Services are not then purchased as provided hereunder; or (vi) reverse engineer, decompile or modify any encrypted or encoded portion of the Software.
A complete copy of the MSA is available at http://www.mindtouch.com/msa
If you attempt to start the CrashPlan app and it gets stuck on the CrashPlan splash screen displaying the error, "Unable to connect to backup engine, retry?", this article can help troubleshoot the issue. Please note that this is usually because the CrashPlan service is not running; it is not a network error.
The CrashPlan app consists of two parts: the graphical user interface that the user interacts with and the CrashPlan service that runs in the background. These two pieces communicate over a local network connection that is built into every computer. When the CrashPlan app starts, the CrashPlan service attempts to connect back to itself. If it can't connect, the backup engine won't start.
If you have a large backup selection (more than 1 TB or 1 million files), you may need to allocate more memory to the CrashPlan app. When CrashPlan runs into this memory limit, the CrashPlan service is not able to run, resulting in the "Unable to connect to backup engine" message. If you have a large file selection backing up, refer to our troubleshooting article on this topic to address the issue.
Finally, if you're still having troubles, you can test to make sure that nothing else on the computer is already using ports 4242 and 4243, which CrashPlan needs to run. CrashPlan may not need to use these ports all the time, but it still needs to prepare them for use (open the socket).
The CrashPlan.app file must reside in the Applications folder and must be named CrashPlan.app. If you've moved or renamed CrashPlan.app, you may see the “CrashPlan unable to connect to the local backup engine” error upon starting the CrashPlan app. To resolve this, uninstall and reinstall CrashPlan.
There is a known issue in the 3.6.3 version of the CrashPlan app that impacts systems running Mac OS X with case-sensitive file systems. This issue results in the Unable to connect to the backup engine message upon opening the CrashPlan app. See our troubleshooting guide for to resolve the issue.
The CrashPlan app version 3.4.1 and earlier is not compatible with Java 1.7. On October 16, 2012, Apple released an update to Java 1.6 that could cause your computer to use Java 1.7 by default. This WikiHow article can help you determine which version(s) of Java are installed on your computer.
Is the CrashPlan service enabled? You can verify this from the Microsoft Services menu. To open the Microsoft Services menu:
If the "Unable to connect to backup engine" error returns after each reboot, this is usually caused by another Windows service conflicting with the CrashPlan service at boot. To resolve this, you can delay CrashPlan's startup. To do this: