CrashPlan Linux release 2015
readme
 
Thank you for trying Code42 CrashPlan! Please send all support questions related to our Linux release to our Customer Champions at: support@crashplan.com. This document is for folks that are comfortable with the Linux command line. You don't have to be an expert, but if the idea of typing green text into a black window scares you, close this window now!
 
System Requirements:
RedHat 6.7 x64 kernel 2.6.32-573 or later
Ubuntu 14.04 x64 kernel 3.13 or later
 
Installation:
Unzip our installer in the location of your choosing. This is the installer only. When you run the installer you choose where to install the actual application.
cd /mypreferred/installer/location
tar -zxf CrashPlan_version-Linux.tgz
 
Wondering where your preferred install location should be? Install it where your other optional software goes. The default is in /opt/ or /usr/local/.
 
What is this stuff I just unzipped?
There are two parts to CrashPlan:
 
CrashPlanEngine
CrashPlanDesktop
 
The Engine is the service that does the actual work of backing up. If it's not running, you're not backing up.
 
The Desktop is a GUI that allows you to configure the engine, display status, and restore data.
 
Install!
It is important to install CrashPlanEngine using an account that has access to the files you want to back up. Are you only intending to backup your own directory? Then installing the software with your permissions is fine. Want to back up someone else's directory or system files? Make sure to install the engine as root.
 
First, go to the directory where you untarred the installer:
cd /mypreferred/installer/location
 
Then, install the software with the permissions you prefer:
 
Installing engine with your permissions:
./install.sh 
 
Installing engine with root permissions:
sudo ./install.sh
 
The installer asks questions about where to install the software and the executables. If you like the default suggestions, just hit Enter to accept them. If you prefer other choices, type in your own.
 
Once the installation is complete, the engine runs in the background, and you should be good to go.
 
Your first backup:
The GUI runs with your permissions so go ahead and start it up after installing:
/usr/local/bin/CrashPlanDesktop
 
That's it! Create an account in CrashPlan, configure backup file selection, and push start. You're all set. Please note you can quit the GUI at any time. It's not actually doing the backup, it's only doing the configuration.
 
Captain's Log:
All kinds of useful information is in the crashplan/log folder. Files ending in .0 are newest, .1 oldest. Entries older than .0 or .1 get deleted.
history.log Summary log of what CrashPlanEngine has been up to.
service.log A detailed log of CrashPlanEngine's activities.
backup_files.log A list of files backed up, and when they're backed up.
restore_files.log A list of files restored, and any problems encountered.
 
FAQ:
 
Is it a bad idea to run the CrashPlanEngine as root?
There are basic risks associated with it. These are the same as any service running as root. Because the engine uses java, it's immune to buffer overflows, a common exploit for C code. Any desktop client connecting has "permission" to select any file and back it up. Thus, you should "require" authentication each time the GUI is run. This is in the Settings > Security part of the CrashPlan GUI.
 
What default ports does CrashPlan use?
OUTBOUND TCP 443 outbound to talk to our servers. (Account creation, dynamic dns, etc.)
LISTENING TCP 4242 when talking to another CrashPlan instance for backup. If port 4242 is in use by another application, CrashPlan will select another port.
LISTENING TCP 4243 on localhost only. This is what the CrashPlanDesktop uses to talk to the CrashPlanBackupEngine. (4283 for CrashPlanPRO clients)

Note: If these ports are already in use on your system, CrashPlan will use a different port for inbound and outbound traffic.
 
What if I don't want to depend on your server?
Run our CrashPlan PROe Server product. It's free and available at https://www.code42.com/trial/
 
Why doesn't it do XYZ?
Because you haven't sent an e-mail to support@crashplan.com requesting feature XYZ
 
What about my other questions?
Send us an e-mail at support@crashplan.com