The CrashPlan support site details a slightly more complicated method of tunneling traffic from the client (CrashPlan Desktop) to the daemon (CrashPlan Engine) through an SSH tunnel.

More ideas can be found on these websites: Note that the authentication token (located in /var/lib/crashplan/.ui_info) on the local and remote servers must match. (Again, the executable is named CrashPlanDesktop.) On the client: ssh -N -L 4243:localhost:4243.

Start the CrashPlan daemon on the server.

Thus, an easy way of configuring the CrashPlan daemon on a headless server is to create an SSH tunnel:

On CrashPlan v4.x and below, the client and daemon communicate on port 4243 by default. If you have problems, check /opt/crashplan/log/ui_error.log. The headless machine's windows will appear on the local X11 server. The CrashPlan daemon's configuration files (in /opt/crashplan/conf) are in an obscure XML format, and they are meant to be edited programmatically by the CrashPlan client.ĬrashPlan 5 introduced a new client which unfortunately dropped support for configuring a remote server with a local client, so you will need to use X11 forwarding.Įnsure that X11Forwarding is set to yes in the headless server's /etc/ssh/sshd_config and from another machine running X11, SSH to the headless machine with -Y, and from the remote shell run CrashPlanDesktop. Running CrashPlan on a headless server is not officially supported. To make CrashPlan automatically start upon system startup, enable the systemd unit.

Backing up to the cloud servers requires a monthly subscription.īefore accessing CrashPlan's graphical user interface, you should start the rvice unit.ĬrashPlan can be configured entirely through its graphical user interface. CrashPlan is a backup program that backs up data to remote servers, other computers, or hard drives.

Dri crashplan