Amahi Wiki - User contributions [en]

PhpSysInfo

2014-12-07T11:37:11Z

Wvdlee: /* Configure SMART information */

[[Category:Apps]]
{{NeedsUpdate}}
== Getting More Info ==
After the one click install of phpsysinfo in Amahi 6 or 7, you need to do some modifications to get all system information displayed.
==Install lm-sensors ==
=== Fedora ===
open a terminal session and login as root or if you have sudo configured use sudo in front of all commands.

type
su -
at the prompt enter your root password

then type
yum install lm_sensors
sensors-detect

=== Ubuntu ===

sudo apt-get install lm-sensors
sudo sensors-detect

Answer the questions. At the end of sensors-detect, Type "yes" to have sensors-detect insert modules into /etc/modules, or edit /etc/modules yourself service module-init-tools start

See [https://help.ubuntu.com/community/SensorInstallHowto#Install_and_Configure_lm-sensors Install and configure lm-sensors] for additional help.

== Configure Settings ==
first make a backup of your original configuration file

cd /var/hda/web-apps/phpsysinfo/html
cp phpsysinfo.ini phpsysinfo.inibak

if neccessary

yum install nano

modify the configuration file
nano phpsysinfo.ini

optional changes

DEFAULT_LANG="nl"
LOAD_BAR=true
USE_VHOST=true
SENSOR_PROGRAM="LMSensors"
HDD_TEMP="command"
HIDE_FS_TYPES="tmpfs,devtmpfs"

For Ubuntu run also
sudo dpkg-reconfigure hddtemp
and set suid to YES

after saving phpsysinfo.ini phpsysinfo will provide voltage, fan, temperature data and more

=== Configure SMART information ===

yum install smartmontools

in phpsysinfo.ini
PLUGINS="SMART"

DEVICES="/dev/sda,/dev/sdb"

You also need to change the plugin script and give apache permission to use smartctl with the sudo command:

(source http://mewbies.com/how_to_install_phpsysinfo_nix_tutorial.html)

Because the cmd 'smartctl' is only available to root; it will not work for your web server, we need to set some permissions on it and change the command it uses:
First we make a copy of the original
cp /var/hda/web-apps/phpsysinfo/html/plugins/smart/class.smart.inc.php /var/hda/web-apps/phpsysinfo/html/plugins/smart/class.smart.inc.php.bak
nano /var/hda/web-apps/phpsysinfo/html/plugins/smart/class.smart.inc.php
Search for (Ctrl+w) (line 60): --all
It has this:

if ( trim($diskname != "") && (CommonFunctions::executeProgram('smartctl', '--all'.' '.$diskdev.' '.$diskname, $buffer, PSI_DEBUG))) {

Change it to:

if ( trim($diskname != "") && (CommonFunctions::executeProgram('sudo', '/usr/sbin/smartctl --all '.' '.$diskdev.' '.$diskname, $buffer, PSI_DEBUG))) {

Just a note that all we changed was:
'smartctl', '--all'
To:
'sudo', '/usr/sbin/smartctl --all '
Change yours to be the same, including the space: all '
Be sure that line isn't broken into multiple lines. If it is you'll see on your xml.php?plugin=SMART page errors containing: \n
And be sure that /usr/sbin/smartctl is the correct path for your installation of smartctl.

Next we need to add your web server group to sudo to be able to run smartctl cmds:
sudo visudo
Paste in this line under '# User privilege specification', changing your
web server group (apache) to your own. For example I have pasted in:
apache ALL=NOPASSWD: /usr/sbin/smartctl
'''(WARNING you are using the vi-editor, first google "vi commands" for some guidance!)'''

PhpSysInfo

2014-12-07T11:32:14Z

Wvdlee: /* Configure SMART information */

[[Category:Apps]]
{{NeedsUpdate}}
== Getting More Info ==
After the one click install of phpsysinfo in Amahi 6 or 7, you need to do some modifications to get all system information displayed.
==Install lm-sensors ==
=== Fedora ===
open a terminal session and login as root or if you have sudo configured use sudo in front of all commands.

type
su -
at the prompt enter your root password

then type
yum install lm_sensors
sensors-detect

=== Ubuntu ===

sudo apt-get install lm-sensors
sudo sensors-detect

Answer the questions. At the end of sensors-detect, Type "yes" to have sensors-detect insert modules into /etc/modules, or edit /etc/modules yourself service module-init-tools start

See [https://help.ubuntu.com/community/SensorInstallHowto#Install_and_Configure_lm-sensors Install and configure lm-sensors] for additional help.

== Configure Settings ==
first make a backup of your original configuration file

cd /var/hda/web-apps/phpsysinfo/html
cp phpsysinfo.ini phpsysinfo.inibak

if neccessary

yum install nano

modify the configuration file
nano phpsysinfo.ini

optional changes

DEFAULT_LANG="nl"
LOAD_BAR=true
USE_VHOST=true
SENSOR_PROGRAM="LMSensors"
HDD_TEMP="command"
HIDE_FS_TYPES="tmpfs,devtmpfs"

For Ubuntu run also
sudo dpkg-reconfigure hddtemp
and set suid to YES

after saving phpsysinfo.ini phpsysinfo will provide voltage, fan, temperature data and more

=== Configure SMART information ===

yum install smartmontools

in phpsysinfo.ini
PLUGINS="SMART"

DEVICES="/dev/sda,/dev/sdb"

You also need to change the plugin script and give apache permission to use smartctl with the sudo command:

(source http://mewbies.com/how_to_install_phpsysinfo_nix_tutorial.html)

Because the cmd 'smartctl' is only available to root; it will not work for your web server, we need to set some permissions on it and change the command it uses:
First we make a copy of the original
cp /var/hda/web-apps/phpsysinfo/html/plugins/smart/class.smart.inc.php /var/hda/web-apps/phpsysinfo/html/plugins/smart/class.smart.inc.php.bak
nano /var/hda/web-apps/phpsysinfo/html/plugins/smart/class.smart.inc.php
Search for (Ctrl+w) (line 60): --all
It has this:
if (CommonFunctions::executeProgram('smartctl', '--all'.((PSI_PLUGIN_SMART_DEVICE) ? ' --device '.PSI_PLUGIN_SMART_DEVICE : '').' '.$disk, $buffer, PSI_DEBUG)) {
Change it to:
if (CommonFunctions::executeProgram('sudo', '/usr/sbin/smartctl --all '.((PSI_PLUGIN_SMART_DEVICE) ? ' --device '.PSI_PLUGIN_SMART_DEVICE : '').' '.$disk, $buffer, PSI_DEBUG)) {

Just a note that all we changed was:
'smartctl', '--all'
To:
'sudo', '/usr/sbin/smartctl --all '
Change yours to be the same, including the space: all '
Be sure that line isn't broken into multiple lines. If it is you'll see on your xml.php?plugin=SMART page errors containing: \n
And be sure that /usr/sbin/smartctl is the correct path for your installation of smartctl.

Next we need to add your web server group to sudo to be able to run smartctl cmds:
sudo visudo
Paste in this line under '# User privilege specification', changing your
web server group (apache) to your own. For example I have pasted in:
apache ALL=NOPASSWD: /usr/sbin/smartctl
'''(WARNING you are using the vi-editor, first google "vi commands" for some guidance!)'''

PhpSysInfo

2014-12-07T11:26:11Z

Wvdlee: /* Configure SMART information */

[[Category:Apps]]
{{NeedsUpdate}}
== Getting More Info ==
After the one click install of phpsysinfo in Amahi 6 or 7, you need to do some modifications to get all system information displayed.
==Install lm-sensors ==
=== Fedora ===
open a terminal session and login as root or if you have sudo configured use sudo in front of all commands.

type
su -
at the prompt enter your root password

then type
yum install lm_sensors
sensors-detect

=== Ubuntu ===

sudo apt-get install lm-sensors
sudo sensors-detect

Answer the questions. At the end of sensors-detect, Type "yes" to have sensors-detect insert modules into /etc/modules, or edit /etc/modules yourself service module-init-tools start

See [https://help.ubuntu.com/community/SensorInstallHowto#Install_and_Configure_lm-sensors Install and configure lm-sensors] for additional help.

== Configure Settings ==
first make a backup of your original configuration file

cd /var/hda/web-apps/phpsysinfo/html
cp phpsysinfo.ini phpsysinfo.inibak

if neccessary

yum install nano

modify the configuration file
nano phpsysinfo.ini

optional changes

DEFAULT_LANG="nl"
LOAD_BAR=true
USE_VHOST=true
SENSOR_PROGRAM="LMSensors"
HDD_TEMP="command"
HIDE_FS_TYPES="tmpfs,devtmpfs"

For Ubuntu run also
sudo dpkg-reconfigure hddtemp
and set suid to YES

after saving phpsysinfo.ini phpsysinfo will provide voltage, fan, temperature data and more

=== Configure SMART information ===

yum install smartmontools

in phpsysinfo.ini
PLUGINS="SMART"

DEVICES="/dev/sda,/dev/sdb"

You also need to change the plugin script and give apache permission to use smartctl with the sudo command:

(source http://mewbies.com/how_to_install_phpsysinfo_nix_tutorial.html)

Because the cmd 'smartctl' is only available to root; it will not work for your web server, we need to set some permissions on it and change the command it uses:
nano /var/hda/web-apps/phpsysinfo/html/plugins/SMART/class.SMART.inc.php
Search for (Ctrl+w) (line 60): --all
It has this:
if (CommonFunctions::executeProgram('smartctl', '--all'.((PSI_PLUGIN_SMART_DEVICE) ? ' --device '.PSI_PLUGIN_SMART_DEVICE : '').' '.$disk, $buffer, PSI_DEBUG)) {
Change it to:
if (CommonFunctions::executeProgram('sudo', '/usr/sbin/smartctl --all '.((PSI_PLUGIN_SMART_DEVICE) ? ' --device '.PSI_PLUGIN_SMART_DEVICE : '').' '.$disk, $buffer, PSI_DEBUG)) {

Just a note that all we changed was:
'smartctl', '--all'
To:
'sudo', '/usr/sbin/smartctl --all '
Change yours to be the same, including the space: all '
Be sure that line isn't broken into multiple lines. If it is you'll see on your xml.php?plugin=SMART page errors containing: \n
And be sure that /usr/sbin/smartctl is the correct path for your installation of smartctl.

Next we need to add your web server group to sudo to be able to run smartctl cmds:
sudo visudo
Paste in this line under '# User privilege specification', changing your
web server group (apache) to your own. For example I have pasted in:
apache ALL=NOPASSWD: /usr/sbin/smartctl
'''(WARNING you are using the vi-editor, first google "vi commands" for some guidance!)'''

PhpSysInfo

2014-12-07T11:20:08Z

Wvdlee: /* Configure Settings */

[[Category:Apps]]
{{NeedsUpdate}}
== Getting More Info ==
After the one click install of phpsysinfo in Amahi 6 or 7, you need to do some modifications to get all system information displayed.
==Install lm-sensors ==
=== Fedora ===
open a terminal session and login as root or if you have sudo configured use sudo in front of all commands.

type
su -
at the prompt enter your root password

then type
yum install lm_sensors
sensors-detect

=== Ubuntu ===

sudo apt-get install lm-sensors
sudo sensors-detect

Answer the questions. At the end of sensors-detect, Type "yes" to have sensors-detect insert modules into /etc/modules, or edit /etc/modules yourself service module-init-tools start

See [https://help.ubuntu.com/community/SensorInstallHowto#Install_and_Configure_lm-sensors Install and configure lm-sensors] for additional help.

== Configure Settings ==
first make a backup of your original configuration file

cd /var/hda/web-apps/phpsysinfo/html
cp phpsysinfo.ini phpsysinfo.inibak

if neccessary

yum install nano

modify the configuration file
nano phpsysinfo.ini

optional changes

DEFAULT_LANG="nl"
LOAD_BAR=true
USE_VHOST=true
SENSOR_PROGRAM="LMSensors"
HDD_TEMP="command"
HIDE_FS_TYPES="tmpfs,devtmpfs"

For Ubuntu run also
sudo dpkg-reconfigure hddtemp
and set suid to YES

after saving phpsysinfo.ini phpsysinfo will provide voltage, fan, temperature data and more

=== Configure SMART information ===

yum install smartmontools

in phpsysinfo.ini
PLUGINS="SMART"

DEVICES="/dev/sda,/dev/sdb"

You also need to give apache permission to use smartctl with the sudo command:

(source http://mewbies.com/how_to_install_phpsysinfo_nix_tutorial.html)

Because the cmd 'smartctl' is only available to root; it will not work for your web server, we need to set some permissions on it and change the command it uses:
nano /var/hda/web-apps/phpsysinfo/html/plugins/SMART/class.SMART.inc.php
Search for (Ctrl+w) (line 60): --all
It has this:
if (CommonFunctions::executeProgram('smartctl', '--all'.((PSI_PLUGIN_SMART_DEVICE) ? ' --device '.PSI_PLUGIN_SMART_DEVICE : '').' '.$disk, $buffer, PSI_DEBUG)) {
Change it to:
if (CommonFunctions::executeProgram('sudo', '/usr/sbin/smartctl --all '.((PSI_PLUGIN_SMART_DEVICE) ? ' --device '.PSI_PLUGIN_SMART_DEVICE : '').' '.$disk, $buffer, PSI_DEBUG)) {

Just a note that all we changed was:
'smartctl', '--all'
To:
'sudo', '/usr/sbin/smartctl --all '
Change yours to be the same, including the space: all '
Be sure that line isn't broken into multiple lines. If it is you'll see on your xml.php?plugin=SMART page errors containing: \n
And be sure that /usr/sbin/smartctl is the correct path for your installation of smartctl.

Next we need to add your web server group to sudo to be able to run smartctl cmds:
sudo visudo
Paste in this line under '# User privilege specification', changing your
web server group (apache) to your own. For example I have pasted in:
apache ALL=NOPASSWD: /usr/sbin/smartctl
'''(WARNING you are using the vi-editor, first google "vi commands" for some guidance!)'''

Crashplan

2014-11-30T01:22:17Z

Wvdlee: /* On the HDA */

[[Category:Apps]]
==[http://www.amahi.org/apps/crashplan 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 [http://b1.crashplan.com/consumer/features.html#CrashPlan+ 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.

==Installing CrashPlan==

To be able to use CrashPlan, you'll need to install the [http://www.amahi.org/apps/crashplan 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.

<h4>Please Note</h4> Crashplan 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==

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].

==CrashPlan Accounts==

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.

==Configure CrashPlan (Fedora 19)==
===On the HDA===
[[Open_Terminal_as_root|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:
<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:
systemctl restart crashplan.service

'''ATTENTION the above changes are sometimes undone during crashplan updates, you have to repeat above steps to repair connectivity !!!!!'''

===Desktop Client===
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:

#serviceHost=127.0.0.1

* Change the line to remove the comment character ‘#’ and include the IP address of your HDA. For example:

serviceHost=192.168.1.100

You now should be able to administer CrashPlan using your HDA as the local storage location.

===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 [http://download.eclipse.org/eclipse/downloads/drops4/R-4.3-201306052000/#SWT 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: [https://forums.amahi.org/viewtopic.php?f=26&t=4951 this forum post]]

==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:

Fedora:
su -
CrashPlanDesktop

Ubuntu:
sudo CrashPlanDesktop

If you don't have physical access to your HDA, or if you run it headless, try the methods below.

===Using VNC===
If you have [[VNC]] or [[WebVNC]] setup, you can use that to configure CrashPlan remotely, instead of using the OS-dependent methods described 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.

===Using X-Forwarding===
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.

====Windows====
=====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 [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html 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 [https://sourceforge.net/projects/xming/files/Xming/ Xming installer], and the [https://sourceforge.net/projects/xming/files/Xming-fonts/ 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''.

[[Image:Red-S01.png]]

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=====
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 [http://downloads.sourceforge.net/project/freexer/FreeXer/0.2/freeXer-installer.exe 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''.

[[Image:Sess_editor_new.png]]

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.

=====Guides=====
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.cs.caltech.edu/courses/cs11/misc/xwindows.html Using X Forwarding on Windows at Caltech]
* [http://www.math.umn.edu/systems_guide/putty_xwin32.html 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

====Linux====

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 [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.

Crashplan

2014-11-30T01:19:20Z

Wvdlee: /* On the HDA */

[[Category:Apps]]
==[http://www.amahi.org/apps/crashplan 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 [http://b1.crashplan.com/consumer/features.html#CrashPlan+ 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.

==Installing CrashPlan==

To be able to use CrashPlan, you'll need to install the [http://www.amahi.org/apps/crashplan 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.

<h4>Please Note</h4> Crashplan 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==

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].

==CrashPlan Accounts==

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.

==Configure CrashPlan (Fedora 19)==
===On the HDA===
[[Open_Terminal_as_root|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:
<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:
systemctl restart crashplan.service

ATTENTION the above changes are sometimes undone during crashplan updates, you have to repeat above steps to repair connectivity !!!!!

===Desktop Client===
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:

#serviceHost=127.0.0.1

* Change the line to remove the comment character ‘#’ and include the IP address of your HDA. For example:

serviceHost=192.168.1.100

You now should be able to administer CrashPlan using your HDA as the local storage location.

===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 [http://download.eclipse.org/eclipse/downloads/drops4/R-4.3-201306052000/#SWT 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: [https://forums.amahi.org/viewtopic.php?f=26&t=4951 this forum post]]

==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:

Fedora:
su -
CrashPlanDesktop

Ubuntu:
sudo CrashPlanDesktop

If you don't have physical access to your HDA, or if you run it headless, try the methods below.

===Using VNC===
If you have [[VNC]] or [[WebVNC]] setup, you can use that to configure CrashPlan remotely, instead of using the OS-dependent methods described 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.

===Using X-Forwarding===
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.

====Windows====
=====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 [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html 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 [https://sourceforge.net/projects/xming/files/Xming/ Xming installer], and the [https://sourceforge.net/projects/xming/files/Xming-fonts/ 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''.

[[Image:Red-S01.png]]

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=====
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 [http://downloads.sourceforge.net/project/freexer/FreeXer/0.2/freeXer-installer.exe 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''.

[[Image:Sess_editor_new.png]]

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.

=====Guides=====
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.cs.caltech.edu/courses/cs11/misc/xwindows.html Using X Forwarding on Windows at Caltech]
* [http://www.math.umn.edu/systems_guide/putty_xwin32.html 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

====Linux====

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 [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.

PhpSysInfo

2014-11-28T17:33:53Z

Wvdlee: /* Configure phpsysinfo */

PhpSysInfo

2014-11-28T17:33:04Z

Wvdlee: /* Configure phpsysinfo */

PhpSysInfo

2014-11-28T17:27:55Z

Wvdlee: /* Getting More Info */

PhpSysInfo

2014-11-28T17:26:50Z

Wvdlee: /* Configure phpsysinfo */

[[Category:Apps]]
{{NeedsUpdate}}
== Getting More Info ==
After the one click install of phpsysinfo in Amahi 6.0, you need to do some modifications to get all system information displayed.
=== Fedora Install lm-sensors ===
open a terminal session and login as root or if you have sudo configured use sudo in front of all commands.

type
su -
at the prompt enter your root password

then type
yum install lm_sensors
sensors-detect

=== Ubuntu Install lm-sensors [https://help.ubuntu.com/community/SensorInstallHowto#Install_and_Configure_lm-sensors (Additional help)] ===

sudo apt-get install lm-sensors
sudo sensors-detect

Answer the questions. At the end of sensors-detect, Type "yes" to have sensors-detect insert modules into /etc/modules, or edit /etc/modules yourself service module-init-tools start

=== Configure phpsysinfo ===
first make a backup of your original configuration file

cd /var/hda/web-apps/phpsysinfo/html
cp phpsysinfo.ini phpsysinfo.inibak

if neccessary

yum install nano

modify the configuration file
nano phpsysinfo.ini

optional changes

DEFAULT_LANG="nl"
LOAD_BAR=true
USE_VHOST=true
SENSOR_PROGRAM="LMSensors"
HDD_TEMP="command"
HIDE_FS_TYPES="tmpfs,devtmpfs"

For Ubuntu run also
sudo dpkg-reconfigure hddtemp
and set suid to YES

after saving phpsysinfo.ini phpsysinfo will provide voltage, fan, temperature data and more

PhpSysInfo

2014-11-28T17:25:03Z

Wvdlee: /* Configure phpsysinfo */

[[Category:Apps]]
{{NeedsUpdate}}
== Getting More Info ==
After the one click install of phpsysinfo in Amahi 6.0, you need to do some modifications to get all system information displayed.
=== Fedora Install lm-sensors ===
open a terminal session and login as root or if you have sudo configured use sudo in front of all commands.

type
su -
at the prompt enter your root password

then type
yum install lm_sensors
sensors-detect

=== Ubuntu Install lm-sensors [https://help.ubuntu.com/community/SensorInstallHowto#Install_and_Configure_lm-sensors (Additional help)] ===

sudo apt-get install lm-sensors
sudo sensors-detect

Answer the questions. At the end of sensors-detect, Type "yes" to have sensors-detect insert modules into /etc/modules, or edit /etc/modules yourself service module-init-tools start

=== Configure phpsysinfo ===
first make a backup of your original configuration file

cd /var/hda/web-apps/phpsysinfo/html
cp phpsysinfo.ini phpsysinfo.inibak

if neccessary

yum install nano

modify the configuration file
nano phpsysinfo.ini

optional changes

DEFAULT_LANG="nl"
LOAD_BAR=true
USE_VHOST=true
SENSOR_PROGRAM="LMSensors"
HDD_TEMP="command"
HIDE_FS_TYPES="tmpfs,devtmpfs"

For Ubuntu run also
sudo dpkg-reconfigure hddtemp
and set suid to YES

after saving config.php phpsysinfo will provide voltage, fan and temperature data.

PhpSysInfo

2014-11-28T17:24:00Z

Wvdlee: /* Install lm-sensors and configure phpsysinfo (Additional help) */

[[Category:Apps]]
{{NeedsUpdate}}
== Getting More Info ==
After the one click install of phpsysinfo in Amahi 6.0, you need to do some modifications to get all system information displayed.
=== Fedora Install lm-sensors ===
open a terminal session and login as root or if you have sudo configured use sudo in front of all commands.

type
su -
at the prompt enter your root password

then type
yum install lm_sensors
sensors-detect

=== Ubuntu Install lm-sensors [https://help.ubuntu.com/community/SensorInstallHowto#Install_and_Configure_lm-sensors (Additional help)] ===

sudo apt-get install lm-sensors
sudo sensors-detect

Answer the questions. At the end of sensors-detect, Type "yes" to have sensors-detect insert modules into /etc/modules, or edit /etc/modules yourself service module-init-tools start

=== Configure phpsysinfo ===
first make a backup of your original configuration file

cd /var/hda/web-apps/phpsysinfo/html
cp phpsysinfo.ini phpsysinfo.inibak

modify the configuration file
nano phpsysinfo.ini

optional changes

DEFAULT_LANG="nl"
LOAD_BAR=true
USE_VHOST=true
SENSOR_PROGRAM="LMSensors"
HDD_TEMP="command"
HIDE_FS_TYPES="tmpfs,devtmpfs"

For Ubuntu run also
sudo dpkg-reconfigure hddtemp
and set suid to YES

after saving config.php phpsysinfo will provide voltage, fan and temperature data.

PhpSysInfo

2012-07-18T20:02:47Z

Wvdlee: make hddtemp work under ubuntu

[[Category:Apps]]
== Getting More Info ==
After the one click install of phpsysinfo in Amahi 6.0, you need to do some modifications to get all system information displayed.
=== Fedora Install lm-sensors ===
open a terminal session and login as root or if you have sudo configured use sudo in front of all commands.

type
{{Code| su -}}
at the prompt enter your root password

then type
{{Code|yum install lm_sensors
sensors-detect}}
=== Ubuntu Install lm-sensors [https://help.ubuntu.com/community/SensorInstallHowto#Install_and_Configure_lm-sensors (Additional help)] ===

{{Code|sudo apt-get install lm-sensors
sudo sensors-detect}}

Answer the questions. At the end of sensors-detect, Type "yes" to have sensors-detect insert modules into /etc/modules, or edit /etc/modules yourself {{Code|service module-init-tools start}}

{{Code|cd /var/hda/web-apps/phpsysinfo/html
cp config.php config.php_bak}}
to make a backup of your original config file

{{Code|nano config.php}}

Change define('PSI_SENSOR_PROGRAM', ''); to define('PSI_SENSOR_PROGRAM', 'LMSensors'); This tells phpsysinfo to use lm_sensors to obtain and display sensor information.

Other optional changes:
define('PSI_HIDE_MOUNTS', '/boot,/dev/shm'); - hides /boot and /dev/shm in mounted filesystems
define('PSI_HIDE_FS_TYPES', 'tmpfs'); - hides tmpfs filesystems
define('PSI_LOAD_BAR', true);
define('PSI_UPS_PROGRAM', 'Apcupsd'); - use apcupsd to show APC info from APC UPS's
define('PSI_HDD_TEMP', 'command'); - tells PSI to obtain current hdd temp
in Ubuntu run also {{Code|sudo dpkg-reconfigure hddtemp}} and set suid to YES

after saving config.php phpsysinfo will provide voltage, fan and temperature data.

PhpSysInfo

2012-07-07T15:59:12Z

Wvdlee:

[[Category:Apps]]
== Getting More Info ==
After the one click install of phpsysinfo in Amahi 6.0, you need to do some modifications to get all system information displayed.

open a terminal session and login as root or if you have sudo configured use sudo in front of all commands.

type
{{Code| su -}}
at the prompt enter your root password

then type
{{Code|yum install lm_sensors
sensors-detect}}

in Ubuntu:
more info at [https://help.ubuntu.com/community/SensorInstallHowto#Install_and_Configure_lm-sensors ubuntu help on lm-sensors]

{{Code|sudo apt-get install lm-sensors
sudo sensors-detect}}

Answer the questions. At the end of sensors-detect, Type "yes" to have sensors-detect insert modules into /etc/modules, or edit /etc/modules yourself {{Code|service module-init-tools start}}

{{Code|cd /var/hda/web-apps/phpsysinfo/html
cp config.php config.php_bak}}
to make a backup of your original config file

{{Code|nano config.php}}

Change define('PSI_SENSOR_PROGRAM', ''); to define('PSI_SENSOR_PROGRAM', 'LMSensors'); This tells phpsysinfo to use lm_sensors to obtain and display sensor information.

Other optional changes:
define('PSI_HIDE_MOUNTS', '/boot,/dev/shm'); - hides /boot and /dev/shm in mounted filesystems
define('PSI_HIDE_FS_TYPES', 'tmpfs'); - hides tmpfs filesystems
define('PSI_HDD_TEMP', 'tcp'); - tells PSI to obtain current hdd temp
define('PSI_LOAD_BAR', true);
define('PSI_UPS_PROGRAM', 'Apcupsd'); - use apcupsd to show APC info from APC UPS's

after saving config.php phpsysinfo will provide voltage, fan and temperature data.

PhpSysInfo

2012-07-07T15:51:46Z

Wvdlee: ubuntu added

[[Category:Apps]]
== Getting More Info ==
After the one click install of phpsysinfo in Amahi 6.0, you need to do some modifications to get all system information displayed.

open a terminal session and login as root or if you have sudo configured use sudo in front of all commands.

type
{{Code| su -}}
at the prompt enter your root password

then type
{{Code|yum install lm_sensors
sensors-detect}}

in Ubuntu:
more info at [https://help.ubuntu.com/community/SensorInstallHowto#Install_and_Configure_lm-sensors ubuntu help on lm-sensors]

{{Code|sudo apt-get install lm-sensors
sudo sensors-detect}}

Answer the questions. At the end of sensors-detect, Type "yes" to have sensors-detect insert modules into /etc/modules, or edit /etc/modules yourself.

{{Code|cd /var/hda/web-apps/phpsysinfo/html
cp config.php config.php_bak}}
to make a backup of your original config file

{{Code|nano config.php}}

Change define('PSI_SENSOR_PROGRAM', ''); to define('PSI_SENSOR_PROGRAM', 'LMSensors'); This tells phpsysinfo to use lm_sensors to obtain and display sensor information.

Other optional changes:
define('PSI_HIDE_MOUNTS', '/boot,/dev/shm'); - hides /boot and /dev/shm in mounted filesystems
define('PSI_HIDE_FS_TYPES', 'tmpfs'); - hides tmpfs filesystems
define('PSI_HDD_TEMP', 'tcp'); - tells PSI to obtain current hdd temp
define('PSI_LOAD_BAR', true);
define('PSI_UPS_PROGRAM', 'Apcupsd'); - use apcupsd to show APC info from APC UPS's

after saving config.php phpsysinfo will provide voltage, fan and temperature data.

Backups

2010-02-18T19:38:31Z

Wvdlee: adding link to Rsnapshot for backuing up HDA shares

You have several ways to do backups in your HDA. We break them in two: full disk (bare metal) backups, and periodic backups.

They are all initiated by the client computer on to the server.

= Full Disk "Bare Metal" Backups =

Each HDA now includes the Personal Backup Appliance, or PBA, with the collaboration of the PBA leader, Roland Hui.

[[PBA | PBA]] is an application to do hard disk clones, backups and restores.

= Using Symantec Backup Exec System Recovery 8.5 (Norton save & restore) =

Symantec's [http://www.symantec.com/business/backup-exec-system-recovery-desktop-edition] (BESR) allows full system backup and restore (virtual and physical)from any hardware with restore to dissimilar hardware. Conversion from P2V or V2P can also be scheduled. Install BESR on all windows computers connected to HDA and route backup to a folder on the HDA. Remember to set permissions on destination folders. Activate VSS copy so any open files are captured, optional threatcon can be used to trigger a backup if a threat becomes widespread.
Alternatively BESR can be installed on a central windows machine with agents deployed on all other windows and Linux machines and using the new Linux media server agent (replaces RALUS) backup directly on the Linux HDA. This way you maintain a catalogue of all backups and can trigger them from a central console.
BESR is the enterprise windows standard for Backup and restore. Norton the consumer brand of Symantec have "Save & Restore" I'm not overly familiar with this product but it replaces Norton "Ghost" in most markets.[http://www.symantec.com/norton/save-restore] the GUI is exactly the same as BESR.

BESR is only for windows machines connected to the HDA but is a great solution to protecting these machines and allows LIVE single pass backup and granular restore of files, saves doing an image and a file backup. Less space less time. An agent is available to backup Linux but another option is to boot the HDA on the recovery disk and create a cold image of the server.

= Periodic File Backups =

One of the ways to backup systems in your network is to use the operating-system provided backup service.
[[Image:VistaBackups3.png | 150px | Vista Backups | align:right]]

We have documented ways to do periodic backups in various platforms. If you have good suggestions on how to do that, please add them to this section of the wiki! (Or email it to us if you're wiki-shy)

Note: To new users only the "Bare Metal" Backups will show in the [http://wiki.amahi.org/index.php/PBABackups Amahi Personal Backup] webpage all others will not show on this page.

== Vista Backups ==
Here is a quick how to on doing [[VistaBackups | periodic file backups in Windows Vista to your HDA]].

== Windows XP Backups ==

For XP Backups, visit the section for [[XPBackups | Windows XP]]

== Ubuntu Backups ==

How to backup Ubuntu clients using Ubuntu's [[Sbackup | Simple Backup]].

== Fedora Backups ==

To backup Fedora clients, the following are recommended:

* [[fwbackups]], a desktop utility
* [http://rsnapshot.org/ rsnapshot], a solution using rsync, with command line interface
* for backing up your hda shares to usbdrive see [[Rsnapshot]] for an example setup.

== Mac OS X ==
Mac OS X without Time Machine is not officially supported through automated HDA Backups at this time.
You can, however, manually copy files to an HDA shared folder.

=== Backups with SuperDuper! ===

Another backup solution is a program called [[SuperDuper!]], follow the link to see the steps and to find out about SuperDuper!.

=== Backups with SystemRescueCD ===

Backups with [[SystemRescueCD_with_Mac_OS_X | SystemRescueCD]] have been reported that they work, more info can be found by visiting the link.

=== Backups with Time Machine ===

==== SMB (Samba) ====

'''WARNING - Hack ahead!''' For Time Machine smb users only.

There is an unsupported way to enable using Mac OS X Time Machine to backup to your HDA. The [http://vowe.net/archives/008940.html Time Machine hack] is a one liner command to be typed in a terminal in Mac OS X:

<code>defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1</code>

This will offer you the choice to backup to your HDA shares.

It should be noted that mounting a directory from your HDA via NFS let's you use time machine without this hack.

Needless to say, we're not advocating you backup your data like this, since Apple does not support this functionality. There are rumors that data corruption can occur if the size of the backup exceeds 2TB or if a large number of files, on the order of a million, are backed up. Because the exact conditions leading to data corruption are not well quantified, we do not recommend you backup like this.

==== AFP ====

For full time machine support in fedora, avahi(bonjour) and netatalk(afp) need to be installed

[[http://wiki.amahi.org/index.php/AFP]Install AFP and Avahi]

*in Applevolume.default add

<code>~/ "$u" allow:UserName rwlist:UserName,@users cnidscheme:cdb 
/var/hda/files/timemachine allow:UserName rwlist:UserName,@users cnidscheme:cdb options:usedots,upriv</code>

*Change UserName to your username and /var/hda/files/timemachine to your timemachine folder, the first line will also publish your homefolder to your mac but was necessary in my setup to work

*then service avahi-daemon and atalk restart

*the server will show up on your mac connect to the xserve afp server
*on your mac open disk utility
*make a new disk image with the max size on disk possible and name it Computername_ethernetmacadress.sparsebundle
ex.
MacBookProIcey_aa00bb11cc22.sparsebundle

#use Journaled/case sensitive
#name has to be Backup of ComputerName
#and save it to the timemachine share
[[File:Tm-sparsebundle.png‎|caption]]

*timemachine image will grow when you synchronize but never larger than the max size
*time machine will now find your amahi time capsule

[[Category: Services]]

Rsnapshot

2010-02-17T20:28:07Z

Wvdlee: edited a typo

Quick recipe to configure rsnapshot.

These are the critical settings in /etc/rsnapshot.conf:

snapshot_root /mnt/1tb-external/snapshots/
interval daily 14
interval weekly 4
interval monthly 4

This will create a series of directories called daily.0 through daily.13
weekly.0 to weekly.3 ... etc.

=Another example of rsnapshot configuration on amahi 5.1=

In this example automated backups are made to an external usb drive.
Plug in the USB drive, it wil probably mount automatically under /media/yourdisklabel

First login as root in a terminal (putty or ssh root@hda)
and type

:mount

in the output, find which device is your usbdrive, possibly /dev/sdb1

=Format usb disk=
You need to format the disk for rsnapshot to be able to use hard links. FAT formatting does not support this unfortunately.

:umount /media/yourdisklabel

:mkfs -t ext3 -v -L usbdisk /dev/sdb1

THIS WILL ERASE ALL DATA ON /dev/sdb1, MAKE SURE THIS IS YOUR USB DRIVE AND NOT ANOTHER DRIVE

=Install rsnapshot=
:yum install rsnapshot

:mkdir -p /media/usbdisk/.private/.snapshots

:chmod 0700 /media/usbdisk/.private/

:chmod 0755 /media/usbdisk/.private/.snapshots/

=Mount your usbdisk permanently=
To Mount your usbdisk permanently (so the backup will work after a reboot) do the following:

:cp /etc/fstab /etc/fstab_bak

:nano /etc/fstab

Add to this file

:LABEL=usbdisk /media/usbdisk ext3 defaults 0 0

Save the file.

=Modify rsnapshot configuration=
:nano /etc/rsnapshot.conf

make the following modifications to the file rsnapshot.conf
for blank spaces use TABS!

:snapshot_root /media/usbdisk/.private/.snapshots/

:no_create_root 1

:interval hourly 6

:interval daily 7

:interval weekly 4

:interval monthly 12

:verbose 3

:backup /var/hda/files/docs/ localhost/

:backup /var/hda/files/pictures/ localhost/

:backup /var/hda/files/movies/ localhost/

:backup /var/hda/files/music/ localhost/

:backup /var/hda/files/othersharesyoumade localhost/

Save the file

:rsnapshot configtest

this should return: syntax OK

=Email reporting=

for email reporting on your backups:

:cp /usr/share/doc/rsnapshot*/utils/rsnapreport.pl /root

:chmod 744 rsnapreport.pl

=Automate backup with cronjob=

:crontab -l > cronjobs

:nano cronjobs

add to this file for running rsnapshot and a weekly email report on rsnapshot:

:0 */4 * * * /usr/bin/rsnapshot hourly 2>&1 | /root/rsnapreport.pl > /root/rsnapreport

:30 23 * * * /usr/bin/rsnapshot daily

:00 23 * * 1 /usr/bin/rsnapshot weekly

:30 22 1 * * /usr/bin/rsnapshot monthly

:00 22 * * 6 /usr/bin/rsnapshot du >> /root/rsnapreport | nail –r "somereturnadress@provider.com" -s"HDA backup report" -S smtp=smtp.yourprovider.com youremail@provider.com < /root/rsnapreport

Save the file

:crontab cronjobs

Rsnapshot should now be operational.

=Make your backups available on clients (READ ONLY)=

If you want to make the backups accesible from your clients:

Create a //hda/backup share in the HDA webinterface

:chkconfig nfs --level 2345 on

add a read only NFS export:

:nano /etc/exports

add

:/media/usbdisk/.private/.snapshots/ 127.0.0.1(ro,no_root_squash)

Save file

Unfortunately mounting an NFS share in fstab did not work on my machine after a reboot, so I chose an alternative configuration that mounts the share later in the booting process:

:nano /etc/rc.local

Add

:mount -r -t nfs localhost:/media/usbdisk/.private/.snapshots/ /var/hda/files/backup/

save file

[[Category: Apps]]

Backups

2010-02-17T20:16:01Z

Wvdlee: link to Rsnapshot example

You have several ways to do backups in your HDA. We break them in two: full disk (bare metal) backups, and periodic backups.

They are all initiated by the client computer on to the server.

= Full Disk "Bare Metal" Backups =

Each HDA now includes the Personal Backup Appliance, or PBA, with the collaboration of the PBA leader, Roland Hui.

[[PBA | PBA]] is an application to do hard disk clones, backups and restores.

= Using Symantec Backup Exec System Recovery 8.5 (Norton save & restore) =

Symantec's [http://www.symantec.com/business/backup-exec-system-recovery-desktop-edition] (BESR) allows full system backup and restore (virtual and physical)from any hardware with restore to dissimilar hardware. Conversion from P2V or V2P can also be scheduled. Install BESR on all windows computers connected to HDA and route backup to a folder on the HDA. Remember to set permissions on destination folders. Activate VSS copy so any open files are captured, optional threatcon can be used to trigger a backup if a threat becomes widespread.
Alternatively BESR can be installed on a central windows machine with agents deployed on all other windows and Linux machines and using the new Linux media server agent (replaces RALUS) backup directly on the Linux HDA. This way you maintain a catalogue of all backups and can trigger them from a central console.
BESR is the enterprise windows standard for Backup and restore. Norton the consumer brand of Symantec have "Save & Restore" I'm not overly familiar with this product but it replaces Norton "Ghost" in most markets.[http://www.symantec.com/norton/save-restore] the GUI is exactly the same as BESR.

BESR is only for windows machines connected to the HDA but is a great solution to protecting these machines and allows LIVE single pass backup and granular restore of files, saves doing an image and a file backup. Less space less time. An agent is available to backup Linux but another option is to boot the HDA on the recovery disk and create a cold image of the server.

= Periodic File Backups =

One of the ways to backup systems in your network is to use the operating-system provided backup service.
[[Image:VistaBackups3.png | 150px | Vista Backups | align:right]]

We have documented ways to do periodic backups in various platforms. If you have good suggestions on how to do that, please add them to this section of the wiki! (Or email it to us if you're wiki-shy)

Note: To new users only the "Bare Metal" Backups will show in the [http://wiki.amahi.org/index.php/PBABackups Amahi Personal Backup] webpage all others will not show on this page.

== Vista Backups ==
Here is a quick how to on doing [[VistaBackups | periodic file backups in Windows Vista to your HDA]].

== Windows XP Backups ==

For XP Backups, visit the section for [[XPBackups | Windows XP]]

== Ubuntu Backups ==

How to backup Ubuntu clients using Ubuntu's [[Sbackup | Simple Backup]].

== Fedora Backups ==

To backup Fedora clients, the following are recommended:

* [[fwbackups]], a desktop utility
* [http://rsnapshot.org/ rsnapshot], a solution using rsync, with command line interface, for an example setup see [[Rsnapshot]]

== Mac OS X ==
Mac OS X without Time Machine is not officially supported through automated HDA Backups at this time.
You can, however, manually copy files to an HDA shared folder.

=== Backups with SuperDuper! ===

Another backup solution is a program called [[SuperDuper!]], follow the link to see the steps and to find out about SuperDuper!.

=== Backups with SystemRescueCD ===

Backups with [[SystemRescueCD_with_Mac_OS_X | SystemRescueCD]] have been reported that they work, more info can be found by visiting the link.

=== Backups with Time Machine ===

==== SMB (Samba) ====

'''WARNING - Hack ahead!''' For Time Machine smb users only.

There is an unsupported way to enable using Mac OS X Time Machine to backup to your HDA. The [http://vowe.net/archives/008940.html Time Machine hack] is a one liner command to be typed in a terminal in Mac OS X:

<code>defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1</code>

This will offer you the choice to backup to your HDA shares.

It should be noted that mounting a directory from your HDA via NFS let's you use time machine without this hack.

Needless to say, we're not advocating you backup your data like this, since Apple does not support this functionality. There are rumors that data corruption can occur if the size of the backup exceeds 2TB or if a large number of files, on the order of a million, are backed up. Because the exact conditions leading to data corruption are not well quantified, we do not recommend you backup like this.

==== AFP ====

For full time machine support in fedora, avahi(bonjour) and netatalk(afp) need to be installed

[[http://wiki.amahi.org/index.php/AFP]Install AFP and Avahi]

*in Applevolume.default add

<code>~/ "$u" allow:UserName rwlist:UserName,@users cnidscheme:cdb 
/var/hda/files/timemachine allow:UserName rwlist:UserName,@users cnidscheme:cdb options:usedots,upriv</code>

*Change UserName to your username and /var/hda/files/timemachine to your timemachine folder, the first line will also publish your homefolder to your mac but was necessary in my setup to work

*then service avahi-daemon and atalk restart

*the server will show up on your mac connect to the xserve afp server
*on your mac open disk utility
*make a new disk image with the max size on disk possible and name it Computername_ethernetmacadress.sparsebundle
ex.
MacBookProIcey_aa00bb11cc22.sparsebundle

#use Journaled/case sensitive
#name has to be Backup of ComputerName
#and save it to the timemachine share
[[File:Tm-sparsebundle.png‎|caption]]

*timemachine image will grow when you synchronize but never larger than the max size
*time machine will now find your amahi time capsule

[[Category: Services]]

Rsnapshot

2010-02-17T20:03:38Z

Wvdlee:

Quick recipe to configure rsnapshot.

These are the critical settings in /etc/rsnapshot.conf:

snapshot_root /mnt/1tb-external/snapshots/
interval daily 14
interval weekly 4
interval monthly 4

This will create a series of directories called daily.0 through daily.13
weekly.0 to weekly.3 ... etc.

=Another example of rsnapshot configuration on amahi 5.1=

In this example automated backups are made to an external usb drive.
Plug in the USB drive, it wil probably mount automatically under /media/yourdisklabel

First login as root in a terminal (putty or ssh root@hda)
and type

:mount

in the output, find which device is your usbdrive, possibly /dev/sdb1

=Format usb disk=
You need to format the disk for rsnapshot to be able to use hard links. FAT formatting does not support this unfortunately.

:Umount /media/yourdisklabel

:mkfs -t ext3 -v -L usbdisk /dev/sdb1

THIS WILL ERASE ALL DATA ON /dev/sdb1, MAKE SURE THIS IS YOUR USB DRIVE AND NOT ANOTHER DRIVE

=Install rsnapshot=
:yum install rsnapshot

:mkdir -p /media/usbdisk/.private/.snapshots

:chmod 0700 /media/usbdisk/.private/

:chmod 0755 /media/usbdisk/.private/.snapshots/

=Mount your usbdisk permanently=
To Mount your usbdisk permanently (so the backup will work after a reboot) do the following:

:cp /etc/fstab /etc/fstab_bak

:nano /etc/fstab

Add to this file

:LABEL=usbdisk /media/usbdisk ext3 defaults 0 0

Save the file.

=Modify rsnapshot configuration=
:nano /etc/rsnapshot.conf

make the following modifications to the file rsnapshot.conf
for blank spaces use TABS!

:snapshot_root /media/usbdisk/.private/.snapshots/

:no_create_root 1

:interval hourly 6

:interval daily 7

:interval weekly 4

:interval monthly 12

:verbose 3

:backup /var/hda/files/docs/ localhost/

:backup /var/hda/files/pictures/ localhost/

:backup /var/hda/files/movies/ localhost/

:backup /var/hda/files/music/ localhost/

:backup /var/hda/files/othersharesyoumade localhost/

Save the file

:rsnapshot configtest

this should return: syntax OK

=Email reporting=

for email reporting on your backups:

:cp /usr/share/doc/rsnapshot*/utils/rsnapreport.pl /root

:chmod 744 rsnapreport.pl

=Automate backup with cronjob=

:crontab -l > cronjobs

:nano cronjobs

add to this file for running rsnapshot and a weekly email report on rsnapshot:

:0 */4 * * * /usr/bin/rsnapshot hourly 2>&1 | /root/rsnapreport.pl > /root/rsnapreport

:30 23 * * * /usr/bin/rsnapshot daily

:00 23 * * 1 /usr/bin/rsnapshot weekly

:30 22 1 * * /usr/bin/rsnapshot monthly

:00 22 * * 6 /usr/bin/rsnapshot du >> /root/rsnapreport | nail –r "somereturnadress@provider.com" -s"HDA backup report" -S smtp=smtp.yourprovider.com youremail@provider.com < /root/rsnapreport

Save the file

:crontab cronjobs

Rsnapshot should now be operational.

=Make your backups available on clients (READ ONLY)=

If you want to make the backups accesible from your clients:

Create a //hda/backup share in the HDA webinterface

:chkconfig nfs --level 2345 on

add a read only NFS export:

:nano /etc/exports

add

:/media/usbdisk/.private/.snapshots/ 127.0.0.1(ro,no_root_squash)

Save file

Unfortunately mounting an NFS share in fstab did not work on my machine after a reboot, so I chose an alternative configuration that mounts the share later in the booting process:

:nano /etc/rc.local

Add

:mount -r -t nfs localhost:/media/usbdisk/.private/.snapshots/ /var/hda/files/backup/

save file

[[Category: Apps]]

PhpSysInfo

2010-02-17T18:13:09Z

Wvdlee: update of editing config.php so it works under amahi 5.1

[[Category:Apps]]

==PHP SysInfo==

PHP SysInfo is a php script that displays information about the host being accessed. Things like uptime and CPU memory are displayed using phpsysinfo. To run it from your hda:

1. Navigate to the /var/hda/web-apps directory on your hda.

2. Search for a phpsysinfo tarball through a web browser. You can find one at
http://phpsysinfo.sourceforge.net/

3. Download the tarball into the web-apps directory using wget or another method. For example:

'''wget http://downloads.sourceforge.net/phpsysinfo/phpSysInfo-3.0-RC6.tar.gz'''

4. Unpack the phpsysinfo tarball with the tar command:

'''tar -zxvf phpSysInfo-3.0-RC6.tar.gz'''

This will create a phpsysinfo directory and unpack all the files.

5. Remove the tarball since it will no longer be needed

'''rm -rf phpSysInfo-3.0-RC6.tar.gz'''

6. Enter the new phpsysinfo directory: '''cd phpsysinfo'''

7. Next, copy the php new configuration file to config.php using the cp command:

'''cp config.php.new config.php'''

8. Use nano or another editor to modify config.php as desired.

'''nano config.php'''

9. Save and close the config.php file. Go to your hda Web Apps tab in a browser (http://setup then select Web Apps). Click on New Web App.

10. Enter "phpsysinfo" in the Name field. The Root Path field will automatically append the directory name onto the /var/hda/web-apps directory.

11. Click Create. A URL will be created and displayed.

12. PHPSysInfo should now be succesfully installed and running. To verify, click on the URL. If you are presented with your system information, phpsysinfo has been successfully installed.

== Getting More Info ==

After the one click install of phpsysinfo in Amahi 5.1 I needed to do some modifications to get all system information displayed.
For other users, this is what I did.

first open a terminal session and login as root
from another computer
in windows with putty
or in linux: ssh root@hda

type

yum install lm_sensors

sensors-detect

keep pressing enter for default answers.

cd /var/hda/web-apps/phpsysinfo/html

cp config.php config.php_bak

to make a backup of your original config file

nano config.php

I changed the following lines, but of course this is optional.
define('sensorProgram', 'LMSensors');
define('hideMounts', '/boot');
define('hideFstypes', 'tmpfs');
define('hddTemp', 'tcp');
define('loadBar', true);

after saving the config.php phpsysinfo also provides voltage, fan and temperature data.