- 1 CrashPlan on Amahi
- 2 Installing CrashPlan
- 3 More about CrashPlan
- 4 CrashPlan Accounts
- 5 Configure CrashPlan
- 6 Configure CrashPlan (Ubuntu)
- 7 On the HDA
- 8 Troubleshooting
CrashPlan on Amahi
Using CrashPlan on your Amahi HDA will allow you to back up, for free1, all your computers into your Amahi HDA2. It will also allow you to become the backup server of friends and family, if you'd like.
1 While CrashPlan is free to personal use, an advanced version, CrashPlan+, is available for a fee, if you'd like to get the features it adds to the free CrashPlan version.
2 Technically, it's also possible to backup your HDA into your other computers if you need that.
To be able to use CrashPlan, you'll need to install the CrashPlan application on your Amahi HDA, configure it as needed, and install the CrashPlan application on all the computers you'd like to backup to your HDA.
Please NoteCrashplan makes very regular writes/reads to the directory it's configured to store backups in. As such, it's best not to point the target directory with in a Greyhole pool, as the number of operations builds beyond a functional level. The backup folder is best placed on a non-pooled disk, or of another type of managed volume or filesystem, such as BTRFS, ZFS, an LVM volume, RAID array, etc.
More about CrashPlan
Using CrashPlan requires a (free) CrashPlan account. You'll be able to create a new account from the configuration app itself.
You'll probably want to use the same account for all computers in your home. That means you'll create the account on the first computer you configure CrashPlan on (it can be your HDA, or any other computer on your home network), and then simply use that same account on all other computers, instead of creating new accounts.
If you'd like to use different accounts, so that each computer (user) is the sole owner of his backed up files, this is also possible. Trying to restore such files from another computer (this is called a guest restore in CrashPlan) will require the user to enter the owner's password.
Amahi 7 (Fedora 19)
On the HDA
Open a terminal window as root and edit the following XML configuration file in your favorite text editor.
nano -w /usr/local/crashplan/conf/my.service.xml
- Search for the “serviceHost” parameter and change it from:
to this instead:
or you can execute the following:
sed -i 's|127.0.0.1|0.0.0.0|' /usr/local/crashplan/conf/my.service.xml
- Save the file and then restart the CrashPlan daemon:
systemctl restart crashplan.service
ATTENTION the above changes are sometimes undone during crashplan updates, you have to repeat above steps to repair connectivity !!!!!
This example will show how to reconfigure the CrashPlan Desktop installation on a Windows PC to talk to the CrashPlan Engine instance running on your HDA.
- Open the folder where you installed CrashPlan on your Windows PC. By default, this is in C:\Program Files\CrashPlan. Inside, you’ll find a folder called “conf” and inside there, a file called “ui.properties”. Open this file using a decent text editor like Notepad++ and look for the following line:
- Change the line to remove the comment character ‘#’ and include the IP address of your HDA. For example:
You now should be able to administer CrashPlan using your HDA as the local storage location.
Amahi 8/9 (Fedora 21/23)
See Using CrashPlan On A Headless Computer for guidance.
Configure CrashPlan (Ubuntu)
NOTE The CrashPlan UI sometimes has issues registering button clicks. If you click a button and it seems to do nothing, hit the ENTER key. That seems to help in such cases.
On the HDA
The easiest way to configure CrashPlan is to access it from the HDA desktop directly.
Launch a Terminal (Applications > System > Terminal).
In the terminal window (must run as root user) enter:
su - CrashPlanDesktop
If you don't have physical access to your HDA, or if you run it headless, try the methods below.
Simply connect to your HDA using VNC (or WebVNC), and launch a Terminal (Applications > System > Terminal).
In the terminal window enter the same commands as noted above depending on the OS you are running on your HDA.
The CrashPlan configuration application will start.
To use X-Forwarding, you don't need X running, or even installed on your HDA.
All you need is an X server on your client computer, and to SSH into your HDA with X-Forwarding enabled.
PuTTY and Xming
You'll need two things to be able to configure CrashPlan from Windows: PuTTY and Xming.
For PuTTY, just download putty.exe from here. You can leave it on your desktop and use it from there.
For Xming, you'll need to download and install two files: the Xming installer, and the fonts installer.
You can accept all the default values for both installs.
Now, you should have a start menu item for Xming. Start it from there. You should now have a black X icon in your system tray.
Next, start PuTTY, and enter your HDA IP address under Host Name (or IP address), enter 22 under Port and select SSH under Connection Type.
Open the Connection > SSH item in the Category tree on the left, and select X11.
Select the checkbox that says Enable X11 forwarding.
Now go back into Session in the Category tree, and give a name for this profile, so you won't have to repeat those steps next time.
Enter a name in the Saved Sessions text box, and hit the Save button on the right.
Next time your start PuTTY, you'll be able to just double-click your profile in the Saved Sessions section to connect to your HDA with X11 forwarding enabled.
Now, connect to your HDA by clicking Open, or double-clicking your profile name in the Saved Sessions select box (on the left of the Load, Save and Delete buttons).
Enter your Fedora username and password when prompted.
FreeXer is an open source attempt to make X11 forwarding easy. It consists of PuTTY and Cygwin with a wrapper that configures both to enable X11 forwarding.
First, download FreeXer here.
Once installed, open the "freeXer Session Editor" and enter a name for the session you're about to start under Session, enter your HDA IP address under Host, select SSH under Protocol, enter your Fedora username under User and password under Password.
Click on the Save button to save the session information. Once you saved the session information, the next time you need it you only need to open the session information file (or load it into the session editor) and you're done.
When ready, click on the Launch Session button.
Once logged in
Enter the following command to start the CrashPlan configuration UI:
Enter the same commands as noted above for the OS you are running on your HDA.
There are many guides available online that explain the steps of X11 forwarding. Here's some, if you need further help:
- X Windows Forwarding video on YouTube
- Using X Forwarding on Windows at Caltech
- X Forwarding with Putty on Windows at University of Minnesota
Mac OS X
Open a Terminal (Applications > Utilities > Terminal.app)
and enter the following commands:
ssh -X hda
Then enter the same commands as outlined above for the OS you are running on the HDA.
Once you're done with the CrashPlan configuration, you can close the CrashPlan app, the X11.app that appeared in your Dock, and Terminal.app
Starting on your X desktop (Gnome, KDE, ...), open a Terminal (Applications >System > Terminal in Fedora)
and enter the following commands:
ssh -X hda
Follow the commands above for the specific OS you are running on your HDA.
Once you're done with the CrashPlan configuration, you can close the CrashPlan app, and the Terminal.
Using a local CrashPlan client
You can follow the instructions on the CrashPlan wiki on how to connect to a headless CrashPlan install.
It requires you to install CrashPlan on your client computer, manually editing a config file, and using SSH port forwarding.
CrashPlan Desktop Java RTE Errors
If you use the CrashPlan desktop on version 3.5.3 you may experience a Java error - when starting the Crashplan desktop the splash image shows for a few seconds, and then vanishes, but the application doesn't open.
It appears that CrashPlan 3.5.3 bundles a buggy version of the "Eclipse Standard Widget Toolkit". To fix, you just need to replace that toolkit with the latest one from the developer.
- Download swt-4.3-gtk-linux-x86.zip and swt-4.3-gtk-linux-x86_64.zip from Eclipse.
- Extract swt.jar from the x86_64 file and rename it as swt-64.jar, and extract swt.jar from the second file. I saved them both to the home directory. (You can do this from terminal from the directory in which you saved the .zip files):
unzip -e swt-4.3-gtk-linux-x86_64.zip swt.jar -d ~ mv ~/swt.jar ~/swt-64.jar unzip -e swt-4.3-gtk-linux-x86.zip swt.jar -d ~
Then you need to copy these to the CrashPlan library. On my HDA CrashPlan was installed to /var/hda/web-apps/crashplan/html. If your installation is different you will need to replace the commands below this your directory.
- Stop the crashplan server
sudo systemctl stop crashplan.service
- Back up the old files and copy in the new ones (change the directory path to your own if it is different and remember to put the /lib at the end):
cd /var/hda/web-apps/crashplan/html/lib mv swt.jar swt.jar.old mv swt-64.jar swt-64.jar.old mv ~/swt.jar swt.jar mv ~/swt-64.jar swt-64.jar
- Restart the crashplan
systemctl start crashplan.service
Should be working now.
[Source: this forum post]
Too many inotify watches
You may see messages in other apps that there is "No space left on device" but you have enough disk space .. it may be that Crashplan is issuing too many inotify watches.
Some processes may report "No space left on device" when this happens. there is a possible work-around for this in Amahi Bug # 2091.