The below allows you to install CrashPlan to your MBL and backup to the cloud. This is tested on the latest firmware update. I have rebuilt and installed this a couple of times now. I am a beginner at Linux and thanks go to NFodiz for demonstrating what is possible!
Updated 21-May-2013 to correct “shares” name where libjtux.so may be stored and posted a link to the working libjtux.so file.
_ Install Java/JRE _
- SSH in to your MBL
- Update the libraries from the command line with “apt-get update” ** If you have additional advice to minimise this action please share it
- Install the JRE from the command line with “apt-get install default-jre”
- Install the JNA library from the command line with “apt-get install libjna-java”
_ Install CrashPlan _
CrashPlan instructions http://support.crashplan.com/doku.php/getting_started/installing_crashplan
Download the CrashPlan for linux from their website http://www.crashplan.com/
Extract the files on your MBL and start the install. I used all the default directories
_ Install updated libjtux.so file _
This is the important step. I have posted a version of the libjtux.so file that is working for me.
Download the libjtux file that works with the MBL’s ARM processor and extract it from the zip - I place it in the root Public folder
Rename the existing libjtux file
From the command line “mv /usr/local/crashplan/libjtux.so /usr/local/crashplan/libjtux.so.backup”
Copy the replacement libjtux.so from your download location. I extracted and stored it in the Public share so simply replace the location below as necessary [/shares/Public/libjtux.so]
From the command line “cp /shares/Public/libjtux.so /usr/local/crashplan/libjtux.so”
_ Start CrashPlan _
From the command line “/usr/local/crashplan/bin/CrashPlanEngine start”
_ Configure CrashPlan _
You can connect from your Windows or other client as a Headless Client as per CrashPlan’s instructions here
You may need to wait a few mins for CrashPlan to start up and the client to connect. You can monitor the process on MBL with top. From the command line “top” and monitor the java process
Backing up to CrashPlan central (the cloud) takes a loooooooooong time. I backed up sets of folders at a time and was able to achieve around 185kps backup speed so yes, you might be initialising your backup for a couple of weeks or several months… For the initial backup I increased the CPU usage to 95% and afterwards reduced it down. Simply follow CrashPlan’s guidance.
If you upgrade your firmware simply follow the instructions to reinstall and then use the “adopt” option from Crashplan to connect to your previous backups.
I’m looking forward to any feedback/comments including the backup speeds you achieved. Good Luck!!