Doing a trial of Crashplan as a potential offsite backup solution for Casa Lembo, but initially got stuck with a non-functioning client gui. Fix follows.
Like some other software out there, Crashplan ships a generic Java client for Linux featuring a shell script installer. This is fine as far as it goes, but unfortunately the swt-64.jar doesn’t play nice in gtk based desktop environments like Gnome 3.
The fix is simple: download the 64-bit swt.jar for gtk from the Eclipse project and copy it over $CRASHPLAN_HOME/lib/swt-64.jar ($CRASHPLAN_HOME being the directory where the product is installed, in my case /opt/crashplan).
The only other wrinkle I found was that you need to specify /etc/rc.d/rc5.d as the directory where the crashplan init script should link to instead of the default /etc/rc5.d, otherwise the installer will fail to write the init script to /etc/init.d (yes, it still uses the System V style init system — but lots of other stuff does too).
I’m currently testing the Crashplan service on my headless backup server, administering it from a remote workstation whose /opt/crashplan/conf/ui.properties has had the serviceHost variable re-configured from 127.0.0.1 to the ip address of my server (on the server I set the value of serviceHost in conf/my.service.xml to 0.0.0.0 so remote clients can connect to it). I’ve designated /data/backup as the default directory for backups from remote clients.
In my initial test I’m pushing up less than 6 GB of data up to the cloud, which the service has estimated will take 3 hours. I’ve scheduled the backup to commence in the early morning hours when nothing should be happening on the host.