Trusted, Bureaucrats, Administrators
12,424
edits
Changes
From Amahi Wiki
→Amahi 8/9 (Fedora 21/23)
[[Category:Apps]]
Using CrashPlan on your Amahi HDA will allow you to back up, for free<sup>1</sup>, all your computers into your Amahi HDA<sup>2</sup>.<br/>It will also allow you to become the backup server of friends and family, if you'd like.
To learn more about CrashPlan, you can visit the [http://www.crashplan.com/consumer/features.html CrashPlan website], where features are explained, and where you can watch CrashPlan in action in their [http://b1.crashplan.com/consumer/features-tour.html video tour].
Using CrashPlan requires a (free) CrashPlan account. You'll be able to create a new account from the configuration app itself.
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.
===On the HDA===
nano -w /usr/local/crashplan/conf/my.service.xml
* Search for the “serviceHost” parameter and change it from:
<serviceHost>127.0.0.1</serviceHost>
to this instead:
<serviceHost>0.0.0.0</serviceHost>
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: /etc/initsystemctl restart crashplan.d/service '''ATTENTION the above changes are sometimes undone during crashplan restartupdates, you have to repeat above steps to repair connectivity !!!!!'''
===Desktop Client===
#serviceHost=127.0.0.1
* Change the line to remove the comment character ‘#’ and include the IP address of your CrashPlan serverHDA. For example:
serviceHost=192.168.1.100
You now should be able to administer CrashPlan using your HDA as the local storage location.
==Amahi 8/9/10 (Fedora 21/23/25)==See [https://support.code42.com/CrashPlan/4/Configuring/Using_CrashPlan_On_A_Headless_Computer Using CrashPlan On A Headless Computer] for guidance. =Configure CrashPlan (Ubuntu)==
<p style="color:red">'''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.</p>
The easiest way to configure CrashPlan is to access it from the HDA desktop directly.
<u>Fedora</u>:
<u>Ubuntu</u>:
If you don't have physical access to your HDA, or if you run it headless, try the methods below.
If you have [[VNC]] or [[WebVNC]] setup, you can use that to configure CrashPlan remotely, instead of using the OS-dependent methods described below.
The CrashPlan configuration application will start.
To use X-Forwarding, you don't need X running, or even installed on your HDA.<br/>
All you need is an X server on your client computer, and to SSH into your HDA with X-Forwarding enabled.
You'll need two things to be able to configure CrashPlan from Windows: PuTTY and Xming.
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.
When ready, click on the ''Launch Session'' button.
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:
*[http://www.youtube.com/v/EsHuZJ5gORE?hl=en_US&fs=1 X Windows Forwarding video on YouTube]
* [http://www.math.umn.edu/systems_guide/putty_xwin32.html X Forwarding with Putty on Windows at University of Minnesota]
Open a Terminal (Applications > Utilities > Terminal.app)<br/>
and enter the following commands:
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)<br/>
and enter the following commands:
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.
You can follow the instructions on the CrashPlan wiki on [http://support.crashplan.com/doku.php/how_to/configure_a_headless_client 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.
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.
* 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):{{Code| 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 {{Code| 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):{{Code| 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 server{{Code|sudo systemctl start crashplan.service}}
Should be working now.
[Source: [https://forums.amahi.org/viewtopic.php?f=26&t=4951 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 [https://bugs.amahi.org/issues/2091 Bug # 2091].
