CrashPlan is a nice piece of backup software that allows you to choose any number of backup sources ( Documents, Photos, Music, everything on your computer ), and back them up to any number of backup destinations ( USB drive, CrahPlan’s servers, a friend’s computer, or any computer of yours that can run the CrahPlan desktop software ). This level of flexibility, and initially free offering is what drew me to CrashPlan for my home backup needs. I like it so much, I purchased the Pro plan, and would recommend it to others.
This post will show you an easy way to configure the CrashPlan desktop software on a Linux server that has no graphical interface ( text-only or headless ), so that it can be used as a backup destination for your other CrashPlan instances.
The CrashPlan support site has a document that provides instructions on how to configure a headless Linux client, and I think I found an even easier way to accomplish the same thing.
After you download, install, and start the CrashPlan client for your Linux server you will find that CrashPlan is listening on two ports. The first, port 4242, is where the CrashPlan engine is listening for backup requests, the second, port 4243, is where the CrashPlan graphical interface is expecting to connect to, so that you can configure the engine part of the software.
The problem at this point is that on your text-only Linux server you have no way of running the graphical CrashPlan software to configure the engine side of things. What you want to do is point the graphical interface client on your Windows, Mac, or Linux workstation at your server, and do the configuration over the network.
On your Linux server find the following CrashPlan configuration file ( this is the default ):
and change the following section:
and restart the CrashPlan service on your Linux server. What you will now find is that CrashPlan is listening on all interfaces for both its network ports. Modify your server firewall rules to allow connections to both these ports ( TCP 4242 and 4243 ) from your home machine.
On your home machine you are going to tell the CrashPlan desktop software to connect to this remote server for configuration instead of the local machine. First shutdown CrashPlan on your home machine, then locate and edit the following file:
and change this line:
where “10.0.0.5″ is the IP address of remote Linux server.
Now startup the CrashPlan desktop on your home machine and you will be connected to the remote instance of CrashPlan on your Linux server.