Amahi Wiki - User contributions [en]

Amahi 10 Upgrade

2017-05-19T21:24:43Z

Uslackr: grammar & minor edits

{{Warning|
<div style<nowiki>=</nowiki>"color:darkred">The Amahi team strongly recommends [[Amahi_10_Install|installing from scratch]] over the upgrade.<br />
<br />
We have tested the fairly clean upgrade cases (with no/few modifications), on virtual machines. In general, there are too many variables involved to 100% ensure success. You must accept risk that your Amahi Server could break on upgrade.
<br />
We can only provide limited support in the [https://forums.amahi.org forums] and [http://talk.amahi.org IRC], though in some cases only [[commercial support]]. We continue to recommend a new install over an upgrade as the best option.</div>}}

:'''NOTE:'''
:* There is no upgrade path from [[Fedora_14|Fedora 14]] or [[Ubuntu|Ubuntu 12.04 LTS]] to [[Amahi 10]]. This will require a new install. The [[HDA OS Migration Guide]] might be helpful.
:* For [[Fedora_19|Amahi 7]] users, an [[Amahi 8 Upgrade]] and [[Amahi 9 Upgrade]] will be needed before the [[Amahi 10]] upgrade can be accomplished (be advised this is untested).

= Upgrading Amahi 9 to Amahi 10 =
== Preparation ==
We '''recommend you turn on a temporary DHCP server''', (e.g. in your router) since the network may go down for the duration of the actual upgrade.

Execute all commands as <code>root</code> user or precede commands with <code>sudo</code>
* Upgrade will work best if apps are uninstalled
* '''Back up your data as a precaution'''

Let's begin!

* Update everything in the system:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
dnf -y update
</div>
* Reboot to pick up new kernels, etc:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
shutdown -r now
</div>
* Update everything in the system again:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
dnf -y update
</div>
* If there are any updates, do it again. If there are new kernels, reboot:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
shutdown -r now
</div>

== Execution ==
Install the upgrade tool:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
dnf -y install fedup
</div>
Do the live update over the network:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
fedup -y --network 25 --nogpgcheck --allowerasing
</div>

Once the previous fedup command is complete, you will be prompted to run:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
dnf system-upgrade reboot
</div>

The actual upgrade will take place now, so you will not be able to access the server (or possibly the network) until it is complete.

It would be good to have a monitor/keyboard on the system to cover the risk that the upgrade process becomes stuck somehow. This also should let you keep up with progress.

Be aware it may take 15 to 30 minutes at a minimum for the upgrade to complete, depending on your hardware.

== Finalize ==
Once the upgrade is complete, execute the following to disable the firewall:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
systemctl stop firewalld
systemctl disable firewalld
systemctl stop rolekit
systemctl disable rolekit
</div>

You now should be able to access the dashboard at <nowiki>http://hda</nowiki>.

= Troubleshooting =
Visit the [[troubleshooting]] page if you find yourself in trouble.

Go back to [http://docs.amahi.org Amahi Docs] page.

Amahi 8 Upgrade

2016-12-29T04:41:20Z

Uslackr: -y not supported on fedup command. Docs verified

{{MessageBox|
backgroundcolor = #faa|
image =Warning.png|
heading =WARNING|
message = Amahi 8 for Fedora 21<br />Maintenance Support ONLY!
Please use a supported release!<br />}}
{{Warning|
<div style<nowiki>=</nowiki>"color:darkred">The Amahi team strongly recommends [[Amahi_8_Install|installing from scratch]] over the upgrade.<br />
<br />
We have tested the fairly clean upgrade cases (with no/few modifications), on virtual machines. In general there are too many variables involved to 100% ensure success. You must accept risk that your Amahi Server could break on upgrade.
<br />
We can only provide limited support in the [https://forums.amahi.org forums] and [http://talk.amahi.org IRC], though in some cases only [[commercial support]]. We continue to recommend a new install over an upgrade as the best option.</div>}}

:'''NOTE:''' There is no upgrade path from [[Fedora_14|Fedora 14]] or [[Ubuntu|Ubuntu 12.04 LTS]] to [[Amahi_8|Amahi 8]]. This will require a new install. The [[HDA OS Migration Guide]] might be helpful.

= Upgrading Amahi 7 to Amahi 8 =
== Preparation ==
We '''recommend you turn on a temporary DHCP server''', (e.g. in your router) since the network may go down for the duration of the actual upgrade.

All commands are executes as <code>root</code> user or precede commands with <code>sudo</code>
* Works best if apps are uninstalled
* '''NOT ALL''' apps available in Amahi 7 are fully operational for Amahi 8. Check the [https://www.amahi.org/apps App Store] before proceeding.
* Back up your data as a precaution
* Update everything in the system:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
yum -y update
</div>
* Reboot to pick up new kernels, etc:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
reboot
</div>
* Update everything in the system again:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
yum -y update
</div>
* If there are any updates, do it again. If there are new kernels, reboot:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
reboot
</div>

== Execution ==
Install the upgrade tool:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
yum -y install fedup
</div>
Do the live update over the network:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
fedup --network 21 --product=server
</div>

If the upgrade does not let you due to issues with (for example) extra packages added by Amahi-installed apps, you may want to add ''--nogpgcheck'' option, i.e.
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
fedup --network 21 --product=server --nogpgcheck
</div>

You may see warnings similar to the following warning but you can ignore them for now. We will clean it up before the upgrade is complete.
<div style="border: 1px solid #A3B1BF; padding: .8em 1em; background-color: #E6F2FF; margin: 0px 1em;">
<i><pre>WARNING: problems were encountered during transaction test:
broken dependencies
perl-PlRPC-0.2020-13.fc19.noarch requires perl-4:5.16.3-266.fc19.x86_64
ruby-mysql-2.8.2-9.fc19.x86_64 requires ruby-libs-2.0.0.353-16.fc19.x86_64
Continue with the upgrade at your own risk.</pre></i></div><br />

Once the previous fedup command is complete, reboot the server (the command will tell you):
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
shutdown -r now
</div>
The actual upgrade will take place now, so you will not be able to access the server (or possibly the network) until it is complete.

It would be good to have a monitor/keyboard on the system to cover the risk that the upgrade process becomes stuck somehow. This also should let you keep up with progress.

Be aware it may take 15 to 30 minutes at a minimum for the upgrade to complete, depending on your hardware.

Once the upgrade is complete, from the command line execute:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
yum check
</div>
The following message or similar will be displayed:
<div style="border: 1px solid #A3B1BF; padding: .8em 1em; background-color: #E6F2FF; margin: 0px 1em;">
<i><pre>perl-PlRPC-0.2020-13.fc19.noarch has missing requires of perl(:MODULE_COMPAT_5.16.2)
ruby-mysql-2.8.2-9.fc19.x86_64 has missing requires of libruby.so.2.0()(64bit)
Error: check all</pre></i></div><br />

To correct these issues, remove the two bad packages (though this could be dangerous if you had a lot of apps installed (in which case we do not recommend it):
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
yum remove perl-PlRPC-0.2020-13.fc19.noarch ruby-mysql.x86_64
</div>
Ensure all the problems are corrected and execute:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
yum check
</div>
The response should be <code>check all</code> which indicates everything is correct.

Now check the functionality of the Amahi dashboard after you get a DHCP lease from your HDA in your client(s). If the process completed successfully, you are now running Fedora 21 with the latest Amahi platform.

Ref: [https://fedoraproject.org/wiki/FedUp FedUp Wiki]

= Troubleshooting =
Visit the [[troubleshooting]] page if you find yourself in trouble.

= Reference =
Refer to the [[HDA Admin How To]] page for Amahi Server administrator guidance.

Talk:How To: Migrate Storage Pool from Fedora 14 to Ubuntu 12

2014-08-13T01:43:03Z

Uslackr:

A couple edits for clarity
* I removed the header formatting because the text was showing up in the TOC and the mention of a link in the TOC when the link doesn't work was confusing.
* Moves the note regarding /etc/fstab to the pertinent step so its not forgotten

Talk:How To: Migrate Storage Pool from Fedora 14 to Ubuntu 12

2014-08-13T01:14:52Z

Uslackr: Created page with "I removed the header formatting because the text was showing up in the TOC and the mention of a link in the TOC when the link doesn't work was confusing."

I removed the header formatting because the text was showing up in the TOC and the mention of a link in the TOC when the link doesn't work was confusing.

OpenVPN

2012-08-07T12:55:55Z

Uslackr: Grammar

'''IMPORTANT: we're transitioning to not having OpenVPN built in, but rather as an app, the [http://www.amahi.org/apps/openvpn OpenVPN one-click app]'''

Remote VPN access to your Amahi HDA comes pre-configured out of the box. There is nothing to configure in the server.

'''You need to forward one port (1194/UDP) to your HDA's IP''' to enable the VPN.

You will also need qclient software.

Once connected from outside your network, your computer becomes virtually a computer in your home network. All your files and services are as easily accessible as when you are at home.

'''NEW! You can now use your amahi.org [https://www.amahi.org/user control panel] to test your VPN remotely!'''

= Overview =

There are two requirements for Remote Access to work:

* On the client side, you need to be running a client
** We provide one for Windows, pre-configured for Amahi
** We recommend one for the Mac, which requires some manual configuration
** The client for Linux comes with most distros and uses the same settings as the Mac
* Your router needs to forward '''UDP port 1194''' to the IP address of your HDA. The way to do this is through port forwarding, which varies from router to router. Make sure you forward UDP (not TCP)

= OpenVPN Clients For Windows, Mac, Linux, Android, iPhone, ... =

Check the page for [[OpenVPN clients]].

= Resources on Port Forwarding =

* [http://www.portforward.com/english/routers/port_forwarding/routerindex.htm Massive database of port forwarding information by router]
* YouTube Video on Port Forwarding for Linksys Routers: http://www.youtube.com/watch?v=GWPUdW1kIJA

= Bridging VPN and eth0 =

If you'd like your VPN clients to get IP addresses in the same subnet as your HDA, and not in the 10.8.0.0/24 subnet (default), read this page: [[VPN Bridging]].

= Troubleshooting =
* Make sure your HDA's network IP range is different than that of the remote network. (e.g. if your HDA's IP address is 192.168.1.X, you cannot connect to it on a remote network also using 192.168.1.X)

* If you are running your HDA from a Verizon FiOS connection, you may experience strange disconnections. This may be due to the Actiontec router's small NAT table. Please see guides here http://www.verizonfioswiki.com/index.php/Using_Your_Own_Router for instructions on how to use your own router.

* If you have a Vonage V-Portal (or perhaps other voip adapters as well), plug your router into your modem, then the v-portal into your router. Vonage tells you to put the v-portal between the modem and the router, but I was unable to connect to vpn until I moved the adapter behind the router.

* Check out [[VPN_troubleshooting]] for more troubleshooting tips.

= Implementation =

The VPN solution is implemented through the very popular [http://openvpn.net/ OpenVPN] software VPN.

[[Category: Services]]
[[Category: VPN]]

OpenVPN

2012-08-07T12:53:49Z

Uslackr: Spelling

'''IMPORTANT: we're transitioning to not having OpenVPN built in, but rather as an app, the [http://www.amahi.org/apps/openvpn OpenVPN one-click app]'''

Remote VPN access to your Amahi HDA comes pre-configured out of the box. There is nothing to configure in the server.

'''You need to forward one port (1194/UDP) to your HDA's IP''' to enable the VPN.

You will also need a client software.

Once connected from outside your network, your computer becomes virtually a computer in your home network. All your files and services are as easily accessible as when you are at home.

'''NEW! You can now use your amahi.org [https://www.amahi.org/user control panel] to test your VPN remotely!'''

= Overview =

There are two requirements for Remote Access to work:

* On the client side, you need to be running a client
** We provide one for Windows, pre-configured for Amahi
** We recommend one for the Mac, which requires some manual configuration
** The client for Linux comes with most distros and uses the same settings as the Mac
* Your router needs to forward '''UDP port 1194''' to the IP address of your HDA. The way to do this is through port forwarding, which varies from router to router. Make sure you forward UDP (not TCP)

= OpenVPN Clients For Windows, Mac, Linux, Android, iPhone, ... =

Check the page for [[OpenVPN clients]].

= Resources on Port Forwarding =

* [http://www.portforward.com/english/routers/port_forwarding/routerindex.htm Massive database of port forwarding information by router]
* YouTube Video on Port Forwarding for Linksys Routers: http://www.youtube.com/watch?v=GWPUdW1kIJA

= Bridging VPN and eth0 =

If you'd like your VPN clients to get IP addresses in the same subnet as your HDA, and not in the 10.8.0.0/24 subnet (default), read this page: [[VPN Bridging]].

= Troubleshooting =
* Make sure your HDA's network IP range is different than that of the remote network. (e.g. if your HDA's IP address is 192.168.1.X, you cannot connect to it on a remote network also using 192.168.1.X)

* If you are running your HDA from a Verizon FiOS connection, you may experience strange disconnections. This may be due to the Actiontec router's small NAT table. Please see guides here http://www.verizonfioswiki.com/index.php/Using_Your_Own_Router for instructions on how to use your own router.

* If you have a Vonage V-Portal (or perhaps other voip adapters as well), plug your router into your modem, then the v-portal into your router. Vonage tells you to put the v-portal between the modem and the router, but I was unable to connect to vpn until I moved the adapter behind the router.

* Check out [[VPN_troubleshooting]] for more troubleshooting tips.

= Implementation =

The VPN solution is implemented through the very popular [http://openvpn.net/ OpenVPN] software VPN.

[[Category: Services]]
[[Category: VPN]]

Linux-hda commands

2012-04-20T00:54:15Z

Uslackr:

= Linux Basic Commands =
[[Basics|Linux Basic Commands]] most users will need.

= General Linux/HDA Commands =
<table border="1">
<tr>
<th>Command</th>
<th>Action</th>
</tr>
<tr>
<td>service httpd start</td>
<td>restart web server</td>
</tr>
<tr>
<td>yum -y update</td>
<td>automatically update fedora</td>
</tr>
<tr>
<td>rpm -Uvh http://dl.getdropbox.com/u/364883/Amahi/hda-platform-*.*-*.noarch.rpm</td>
<td>updates HDA</td>
</tr>
<tr>
<td>rpm -q hda-platform</td>
<td>check to see what version of HDA you're running</td>
</tr>
</table><br />

= HDA Script Commands =
<table border="1">
<tr>
<th>Command</th>
<th>Action</th>
</tr>
<tr>
<td>first-admin</td>
<td>returns name of first admin user</td>
</tr>
<tr>
<td>[[Reset_Amahi_Password|reset-user-password]]</td>
<td>reset a forgotten user password</td>
</tr>
</table>

'''NOTE:''' Must be run from the '''''/var/hda/platform/html/script''''' directory.

<table border="1">
<tr>
<th>Command</th>
<th>Action</th>
</tr>
<tr>
<td>hda-change-gw</td>
<td>change gateway/router IP address</td>
</tr>
<tr>
<td>hda-change-dns</td>
<td>change DNS provider for HDA</td>
</tr>
<tr>
<td>
hda-install-gem</td>
<td>install a specific Ruby Gem</td>
</tr>
<tr>
<td>hda-create-db-and-user</td>
<td>create MySql user and database</td>
</tr>
<tr>
<td>hda-new-install</td>
<td>manual install for Amahi</td>
</tr>
<tr>
<td>hda-php-zone-change</td>
<td>change time zone</td>
</tr>
<tr>
<td>hda-refresh-shares</td>
<td>refresh HDA shares</td>
</tr>
<tr>
<td>/usr/bin/hda-alias</td>
<td></tr>
<tr><td>/usr/bin/hda-fix-sudoers</td>
<td></tr>
<tr><td>/usr/bin/hda-install</td>
<td>deprecated - use amahi-installer</tr>
<tr><td>/usr/bin/hda-install-file</td>
<td></tr>
<tr><td>/usr/bin/hda-register-apps</td>
<td></tr>
<tr><td>/usr/bin/hda-settings</td>
<td>Dumps current settings</tr>
<tr><td>/usr/bin/hda-update-webapps</td>
<td></tr>
<tr><td>/usr/sbin/hda-add-apache-sudoers</td>
<td></tr>
<tr><td>/usr/sbin/hda-diskmount</td>
<td></tr>
<tr><td>/usr/sbin/hda-gems-install</td>
<td></tr>

</table>

'''NOTE:''' Can be run from anywhere (located in '''/usr/bin''').

= Miscellaneous =
<table border="1">
<tr>
<th>Command</th>
<th>Action</th>
</tr>
<tr>
<td>service amahi-ushare restart</td>
<td>restart ushare after adding new content</td>
</tr>
<tr>
<td>vncserver</td>
<td>Starts the VNCServer</td>
</tr>
<tr>
<td>vncserver -kill :1</td>
<td>Stops the VNCServer</td>
</tr>
<tr>
<td>/etc/init.d/mt-daapd start</td>
<td>Starts mt-daapd</td>
</tr>
<tr>
<td>/etc/init.d/mt-daapd stop</td>
<td>Stops mt-daapd</td>
</tr>
<tr>
<td>e2fsck -c /dev/sdb1</td>
<td>Check hard drive sdb1 for errors</td>
</tr>
<tr>
<td>nscd -i hosts</td>
<td>Clear DNS cache on HDA</td>
</tr>

</table><br />

= Greyhole =
Use just "greyhole" in a Terminal to get the list, since those could change in the future. Currently, they are:<br>
(as of greyhole-0.9.22)<br>
Usage: greyhole [ACTION] [OPTIONS]

Where ACTION is one of:
-?, --help Display this help and exit.
-D, --daemon Start the daemon.
-f, --fsck Schedule a fsck.
-C, --cancel-fsck Cancel all scheduled fsck.
-l, --balance Balance available space on storage pool drives.
-s, --stats Display storage pool statistics.
-i, --iostat I/O statistices for your storage pool drives.
-L, --logs Display new greyhole.log entries as they are logged.
-S, --status Display what the Greyhole daemon is currently doing.
-q, --view-queue Display the current work queue.
-a, --empty-trash Empty the trash.
-b, --debug=filename Debug past file operations.
-t, --thaw[=path] Thaw a frozen directory. Greyhole will start working on
files inside <path>. If you don't supply an option, the list
of frozen directories will be displayed.
-w, --wait-for[=path] Tell Greyhole that the missing drive at <path> will return
soon, and that it shouldn't re-create additional file copies
to replace it. If you don't supply an option, the available
options (paths) will be displayed.
-g, --gone[=path] Tell Greyhole that the missing drive at <path> is gone for
good. Greyhole will start replacing the missing file copies
instantly. If you don't supply an option, the available
options (paths) will be displayed.
-n, --going[=path] Tell Greyhole that you want to remove a drive. Greyhole will
then make sure you don't loose any files, and that the
correct number of file copies are created to replace the
missing drive. If you don't supply an option, the available
options (paths) will be displayed.
-r, --replace[=path] Tell Greyhole that you replaced the drive at <path>.
-X, --fix-symlinks Try to find a good file copy to point to for all broken
symlinks found on your shares.
-p, --delete-metadata<=path>
Delete all metadata files for <path>, which should be a
share name, followed by the path to a file that is gone
from your storage pool.
-U, --remove-share<=share_name>
Move the files currently inside the specified share from the
storage pool into the shared folder (landing zone),
effectively removing the share from Greyhole's storage pool.

For --stats and --view-queue, the available OPTIONS are:
-j, --json Output the result as JSON, instead of human-readable text.

For --fsck, the available OPTIONS are:
-e, --email-report Send an email when fsck completes, to report on what was
checked, and any error that was found.
-y, --dont-walk-metadata-store
Speed up fsck by skipping the scan of the metadata store
directories. Scanning the metadata stores is only required to
re-create symbolic links that might be missing from your
shared directories.
-c, --if-conf-changed Only fsck if greyhole.conf or smb.conf paths changed since
the last fsck.
Used in the daily cron to prevent unneccesary fsck runs.
-d, --dir=path Only scan a specific directory, and all sub-directories.
The specified directory should be a Samba share, a
sub-directory of a Samba share, or any directory on a
storage pool drive.
-o, --find-orphaned-files
Scan for files with no metadata in the storage pool drives.
This will allow you to include existing files on a drive
in your storage pool without having to copy them manually.
-k, --checksums Read ALL files in your storage pool, and check that
file copies are identical. This will identify any problem
you might have with your file-systems.
NOTE: this can take a LONG time to complete, since it will read
everything from all your drives!
-m, --delete-orphaned-metadata
When fsck find metadata files with no file copies, delete those
metadata files. If the file copies re-appear later, you'll need
to run fsck with --find-orphaned-files to have them reappear in
your shares.

Linux-hda commands

2012-04-20T00:35:53Z

Uslackr: Updated for greyhole-0.9.22

= Linux Basic Commands =
[[Basics|Linux Basic Commands]] most users will need.

= General Linux/HDA Commands =
<table border="1">
<tr>
<th>Command</th>
<th>Action</th>
</tr>
<tr>
<td>service httpd start</td>
<td>restart web server</td>
</tr>
<tr>
<td>yum -y update</td>
<td>automatically update fedora</td>
</tr>
<tr>
<td>rpm -Uvh http://dl.getdropbox.com/u/364883/Amahi/hda-platform-*.*-*.noarch.rpm</td>
<td>updates HDA</td>
</tr>
<tr>
<td>rpm -q hda-platform</td>
<td>check to see what version of HDA you're running</td>
</tr>
</table><br />

= HDA Script Commands =
<table border="1">
<tr>
<th>Command</th>
<th>Action</th>
</tr>
<tr>
<td>first-admin</td>
<td>returns name of first admin user</td>
</tr>
<tr>
<td>[[Reset_Amahi_Password|reset-user-password]]</td>
<td>reset a forgotten user password</td>
</tr>
</table>

'''NOTE:''' Must be run from the '''''/var/hda/platform/html/script''''' directory.

<table border="1">
<tr>
<th>Command</th>
<th>Action</th>
</tr>
<tr>
<td>hda-change-gw</td>
<td>change gateway/router IP address</td>
</tr>
<tr>
<td>hda-change-dns</td>
<td>change DNS provider for HDA</td>
</tr>
<tr>
<td>
hda-install-gem</td>
<td>install a specific Ruby Gem</td>
</tr>
<tr>
<td>hda-create-db-and-user</td>
<td>create MySql user and database</td>
</tr>
<tr>
<td>hda-new-install</td>
<td>manual install for Amahi</td>
</tr>
<tr>
<td>hda-php-zone-change</td>
<td>change time zone</td>
</tr>
<tr>
<td>hda-refresh-shares</td>
<td>refresh HDA shares</td>
</tr>
</table>

'''NOTE:''' Can be run from anywhere (located in '''/usr/bin''').

= Miscellaneous =
<table border="1">
<tr>
<th>Command</th>
<th>Action</th>
</tr>
<tr>
<td>service amahi-ushare restart</td>
<td>restart ushare after adding new content</td>
</tr>
<tr>
<td>vncserver</td>
<td>Starts the VNCServer</td>
</tr>
<tr>
<td>vncserver -kill :1</td>
<td>Stops the VNCServer</td>
</tr>
<tr>
<td>/etc/init.d/mt-daapd start</td>
<td>Starts mt-daapd</td>
</tr>
<tr>
<td>/etc/init.d/mt-daapd stop</td>
<td>Stops mt-daapd</td>
</tr>
<tr>
<td>e2fsck -c /dev/sdb1</td>
<td>Check hard drive sdb1 for errors</td>
</tr>
<tr>
<td>nscd -i hosts</td>
<td>Clear DNS cache on HDA</td>
</tr>

</table><br />

= Greyhole =
Use just "greyhole" in a Terminal to get the list, since those could change in the future. Currently, they are:
Usage: greyhole [ACTION] [OPTIONS]

Where ACTION is one of:
-?, --help Display this help and exit.
-D, --daemon Start the daemon.
-f, --fsck Schedule a fsck.
-C, --cancel-fsck Cancel all scheduled fsck.
-l, --balance Balance available space on storage pool drives.
-s, --stats Display storage pool statistics.
-i, --iostat I/O statistices for your storage pool drives.
-L, --logs Display new greyhole.log entries as they are logged.
-S, --status Display what the Greyhole daemon is currently doing.
-q, --view-queue Display the current work queue.
-a, --empty-trash Empty the trash.
-b, --debug=filename Debug past file operations.
-t, --thaw[=path] Thaw a frozen directory. Greyhole will start working on
files inside <path>. If you don't supply an option, the list
of frozen directories will be displayed.
-w, --wait-for[=path] Tell Greyhole that the missing drive at <path> will return
soon, and that it shouldn't re-create additional file copies
to replace it. If you don't supply an option, the available
options (paths) will be displayed.
-g, --gone[=path] Tell Greyhole that the missing drive at <path> is gone for
good. Greyhole will start replacing the missing file copies
instantly. If you don't supply an option, the available
options (paths) will be displayed.
-n, --going[=path] Tell Greyhole that you want to remove a drive. Greyhole will
then make sure you don't loose any files, and that the
correct number of file copies are created to replace the
missing drive. If you don't supply an option, the available
options (paths) will be displayed.
-r, --replace[=path] Tell Greyhole that you replaced the drive at <path>.
-X, --fix-symlinks Try to find a good file copy to point to for all broken
symlinks found on your shares.
-p, --delete-metadata<=path>
Delete all metadata files for <path>, which should be a
share name, followed by the path to a file that is gone
from your storage pool.
-U, --remove-share<=share_name>
Move the files currently inside the specified share from the
storage pool into the shared folder (landing zone),
effectively removing the share from Greyhole's storage pool.

For --stats and --view-queue, the available OPTIONS are:
-j, --json Output the result as JSON, instead of human-readable text.

For --fsck, the available OPTIONS are:
-e, --email-report Send an email when fsck completes, to report on what was
checked, and any error that was found.
-y, --dont-walk-metadata-store
Speed up fsck by skipping the scan of the metadata store
directories. Scanning the metadata stores is only required to
re-create symbolic links that might be missing from your
shared directories.
-c, --if-conf-changed Only fsck if greyhole.conf or smb.conf paths changed since
the last fsck.
Used in the daily cron to prevent unneccesary fsck runs.
-d, --dir=path Only scan a specific directory, and all sub-directories.
The specified directory should be a Samba share, a
sub-directory of a Samba share, or any directory on a
storage pool drive.
-o, --find-orphaned-files
Scan for files with no metadata in the storage pool drives.
This will allow you to include existing files on a drive
in your storage pool without having to copy them manually.
-k, --checksums Read ALL files in your storage pool, and check that
file copies are identical. This will identify any problem
you might have with your file-systems.
NOTE: this can take a LONG time to complete, since it will read
everything from all your drives!
-m, --delete-orphaned-metadata
When fsck find metadata files with no file copies, delete those
metadata files. If the file copies re-appear later, you'll need
to run fsck with --find-orphaned-files to have them reappear in
your shares.

Mount Shares Locally

2011-05-31T15:42:19Z

Uslackr:

Mounting your Samba shares locally is useful when you are using Greyhole, and want to write or in any way work with those files locally. Greyhole data should only be accessed through shares, so mounting those shares locally is an easy way to work with Greyhole data safely.

* Install the mount_shares_locally initd script:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; overflow: scroll">
curl -o /etc/init.d/mount_shares_locally http://dl.dropbox.com/u/3022105/Amahi/mount_shares_locally
chmod +x /etc/init.d/mount_shares_locally
chkconfig --add mount_shares_locally
</div>

* Edit /etc/init.d/mount_shares_locally (as user root) in a text editor, and replace ''your_username'' (on line 12) with your username.

* Create the ''/home/your_username/.smb_credentials'' file. This is a simple text file (use your favorite text editor).
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
username=your_username
password=your_password
domain=HOME
</div>

To test your new mounts, you can execute '''service mount_shares_locally start'''<br/>
You will find the mounted shares in ''/mnt/samba/*''<br/>
'''service mount_shares_locally stop''' will unmount the local shares.<br/>

Note: if you used /etc/rc.local and /etc/fstab to mount shares locally in the past, you can remove what you added in those files now. The above initd script replaces all this.

== Unable to mount localy after upgrading to Amahi6 ==
If you try to run mount using this script after you upgraded to Amahi6 you might get greeted by this type of error.

[root@localhost ~]# /etc/init.d/mount_shares_locally start
Mounting Samba shares locally: /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
[ OK ]

It's easily fixed by installing the missing dependency.

{{Code|yum install cifs-utils}}

Now it should work fine to run

{{Code|/etc/init.d/mount_shares_locally start}}

==Problem with service dependency==
The mount_share_locally script requires the greyhole service be running prior to it starting. To ensure this happens, take to following steps:
* Edit /etc/init.d/mount_shares_locally (as user root) in a text editor
** Add greyhole to the list of Required-Start services and save the changes
{{Code|# Required-Start: $network $local_fs $remote_fs smb mysqld greyhole}}
* Remove the service "chkconfig --del mount_shares_locally"
* Re-add the service "chkconfig --add mount_shares_locally"

Mount Shares Locally

2011-05-31T15:19:37Z

Uslackr:

Mounting your Samba shares locally is useful when you are using Greyhole, and want to write or in any way work with those files locally. Greyhole data should only be accessed through shares, so mounting those shares locally is an easy way to work with Greyhole data safely.

* Install the mount_shares_locally initd script:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; overflow: scroll">
curl -o /etc/init.d/mount_shares_locally http://dl.dropbox.com/u/3022105/Amahi/mount_shares_locally
chmod +x /etc/init.d/mount_shares_locally
chkconfig --add mount_shares_locally
</div>

* Edit /etc/init.d/mount_shares_locally (as user root) in a text editor, and replace ''your_username'' (on line 12) with your username.

* Create the ''/home/your_username/.smb_credentials'' file. This is a simple text file (use your favorite text editor).
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
username=your_username
password=your_password
domain=HOME
</div>

To test your new mounts, you can execute '''service mount_shares_locally start'''<br/>
You will find the mounted shares in ''/mnt/samba/*''<br/>
'''service mount_shares_locally stop''' will unmount the local shares.<br/>

Note: if you used /etc/rc.local and /etc/fstab to mount shares locally in the past, you can remove what you added in those files now. The above initd script replaces all this.

== Unable to mount localy after upgrading to Amahi6 ==
If you try to run mount using this script after you upgraded to Amahi6 you might get greeted by this type of error.

[root@localhost ~]# /etc/init.d/mount_shares_locally start
Mounting Samba shares locally: /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
/etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory
[ OK ]

It's easily fixed by installing the missing dependency.

{{Code|yum install cifs-utils}}

Now it should work fine to run

{{Code|/etc/init.d/mount_shares_locally start}}

==Problem
Note: This script requires the greyhole service be running prior to it starting. To fix this, take to following steps
* Edit /etc/init.d/mount_shares_locally (as user root) in a text editor
** Add greyhole to the list of Required-Start services and save the changes
{{Code|# Required-Start: $network $local_fs $remote_fs smb mysqld greyhole}}
* Remove the service "chkconfig --del mount_shares_locally"
* Re-add the service "chkconfig --add mount_shares_locally"

Ps3mediaserver

2011-04-09T02:18:29Z

Uslackr:

=[http://www.amahi.org/apps/ps3mediaserver PS3 Media Server] on Amahi=
{{WorkInProgress}}
==<span style="color:#800000">by Greg Martin (uslacker)</span>==

==Introduction==
Amahi supports several applications for streaming content over the network using DLNA. PS3 Media Server (PMS) is different in that is was designed to transcode video files on the fly so they can be played by the Sony PS3 as it supports a limited number of video & audio codecs. As PMS matures, it supports a growing number of devices. (Samsung, Sony Bravia, Philips, Realtek, WDTVLive, XBox, WindowsMedia, PopCornHour, XBMC, Android, N900).

==Getting Started==
PS3 Media Server cannot be configured through a web page. While we've tried to create a sane default install, you will find a need to adjust the configuration. To do so, you have two choices. Edit the PMS.conf file manually; or run PMS.sh to start the console app.
* To edit PMS.conf, open /var/hda/web-apps/ps3mediaserver/PMS.conf ussing you favorite editor. The file permissions are set so that anyone in the users group can edit them. Documentation for the various settings will be best found in the PMS forums.
* To use the console app, login to the console of your HDA; open the computer app and browse to /var/hda/web-apps/ps3mediaserver/PMS.sh. Double click to run. If prompted on what action to take, select Run in Terminal. Make any edits; click Save and Click Quit.
* Once you finish making changes, you'll need to restart the service. Open a terminal, su to root and run <tt>service pmsd stop</tt> then <tt>service pmsd start</tt>

== Resources: ==
<B>ps3mediaserver - Project Hosting on Google Code</B><BR>
http://code.google.com/p/ps3mediaserver/<BR><BR>

<B>PS3MediaServer Forums</B><BR>
http://www.ps3mediaserver.org/forum/

Ps3mediaserver

2011-04-09T02:14:30Z

Uslackr: new beta update

=[http://www.amahi.org/apps/ps3mediaserver PS3 Media Server] on Amahi=
{{WorkInProgress}}
==<span style="color:#800000">by Greg Martin (uslacker)</span>==

==Introduction==
Amahi supports several applications for streaming content over the network using DLNA. PS3 Media Server (PMS) is different in that is was designed to transcode video files on the fly so they can be played by the Sony PS3 as it supports a limited number of video & audio codecs. As PMS matures, it supports a growing number of devices.

==Getting Started==
PS3 Media Server cannot be configured through a web page. While we've tried to create a sane default install, you will find a need to adjust the configuration. To do so, you have two choices. Edit the PMS.conf file manually; or run PMS.sh to start the console app.
* To edit PMS.conf, open /var/hda/web-apps/ps3mediaserver/PMS.conf ussing you favorite editor. The file permissions are set so that anyone in the users group can edit them. Documentation for the various settings will be best found in the PMS forums.
* To use the console app, login to the console of your HDA; open the computer app and browse to /var/hda/web-apps/ps3mediaserver/PMS.sh. Double click to run. If prompted on what action to take, select Run in Terminal. Make any edits; click Save and Click Quit.
* Once you finish making changes, you'll need to restart the service. Open a terminal, su to root and run <tt>service pmsd stop</tt> then <tt>service pmsd start</tt>

== Resources: ==
<B>ps3mediaserver - Project Hosting on Google Code</B><BR>
http://code.google.com/p/ps3mediaserver/<BR><BR>

<B>PS3MediaServer Forums</B><BR>
http://www.ps3mediaserver.org/forum/

Ps3mediaserver

2011-03-27T21:45:03Z

Uslackr:

=PS3 Mmedia Server on Amahi=

==<span style="color:#800000"> DRAFT in progress by Greg Martin (uslacker)</span>==

==Introduction==
Amahi supports several applications for streaming content over the network using DLNA. PS3 Media Server (PMS) is different in that is was designed to transcode video files on the fly so they can be played by the Sony PS3 as it supports a limited number of video & audio codecs. As PMS matures, it supports a growing number of devices.

== Resources: ==
<B>ps3mediaserver - Project Hosting on Google Code</B><BR>
http://code.google.com/p/ps3mediaserver/<BR><BR>

Ps3mediaserver

2011-03-27T21:42:41Z

Uslackr:

=PS3 Mmedia Server on Amahi=

==<span style="color:#800000"> DRAFT in progress by Greg Martin (uslacker)</span>==

==Introduction==
Amahi supports several (some say many) applicaiton for streaming content over the network using DLNA. PS3 Media Server (PMS) is different in that is was designed to transcode video files so they can be played by the Sony PS3 as it supports a limited number of video & audio codecs. Over time, PMS grown to support a growing number of devices.

== Resources: ==
<B>PS3 Media Server for dummies / tutorial howto documentation</B><BR>
http://ps3mediaserver.org/forum/viewtopic.php?f=6&t=3507<BR><BR>

<B>Java PS3 Media Server for dummies – chapter 3 installation and basic configuration</B><BR>
http://otmanix.de/english/2009/05/17/java-ps3-media-server-for-dummies-chapter-3-installation-and-basic-configuration/<BR><BR>

<B>ps3mediaserver - Project Hosting on Google Code</B><BR>
http://code.google.com/p/ps3mediaserver/<BR><BR>

[[Category:apps]]

Ps3mediaserver

2011-03-27T21:40:15Z

Uslackr:

=PS3 Mmedia Server on Amahi=

==DRAFT in progress by Greg Martin (uslacker)==

==Introduction==
Amahi supports several (some say many) applicaiton for streaming content over the network using DLNA. PS3 Media Server (PMS) is different in that is was designed to transcode video files so they can be played by the Sony PS3 as it supports a limited number of video & audio codecs. Over time, PMS grown to support a growing number of devices.

== Resources: ==
<B>PS3 Media Server for dummies / tutorial howto documentation</B><BR>
http://ps3mediaserver.org/forum/viewtopic.php?f=6&t=3507<BR><BR>

<B>Java PS3 Media Server for dummies – chapter 3 installation and basic configuration</B><BR>
http://otmanix.de/english/2009/05/17/java-ps3-media-server-for-dummies-chapter-3-installation-and-basic-configuration/<BR><BR>

<B>ps3mediaserver - Project Hosting on Google Code</B><BR>
http://code.google.com/p/ps3mediaserver/<BR><BR>

[[Category:apps]]

Ps3mediaserver

2011-03-27T21:03:43Z

Uslackr:

=PS3 Mmedia Server on Amahi=

==Introduction==
Amahi supports several (some say many) applicaiton for streaming content over the network using DLNA. PS3 Media Server (PMS) is different in that is was designed to transcode video files so they can be played by the Sony PS3 as it supports a limited number of video & audio codecs. Over time, PMS grown to support a growing number of devices.

== Resources: ==
<B>PS3 Media Server for dummies / tutorial howto documentation</B><BR>
http://ps3mediaserver.org/forum/viewtopic.php?f=6&t=3507<BR><BR>

<B>Java PS3 Media Server for dummies – chapter 3 installation and basic configuration</B><BR>
http://otmanix.de/english/2009/05/17/java-ps3-media-server-for-dummies-chapter-3-installation-and-basic-configuration/<BR><BR>

<B>ps3mediaserver - Project Hosting on Google Code</B><BR>
http://code.google.com/p/ps3mediaserver/<BR><BR>

[[Category:apps]]

Main Page

2011-03-06T04:37:04Z

Uslackr:

=Welcome to the Amahi Wiki=
<big>
'''CURRENT STABLE RELEASE:''' [[Amahi 6.0]], on [[Fedora 14]]
</big>

----

__TOC__<br />
This is where Amahi community members can best help other Amahi users. Please add or edit any information in the Wiki that you feel is lacking, missing, or need improvement.

----

* [[Intro]]: Introduction to the Amahi HDA
* [[Requirements]]: What's needed
* [http://www.amahi.org/faq FAQ]: Frequently Asked Questions
* [[Feedback]]: Issues, feedback.

For questions or help do not hesitate to [[contact us]].

= Installation =
* See [http://www.amahi.org/support/instructions Installation instructions] in your control panel at amahi.org
* [[Self-install]]: Alternative, unsupported installation instructions
* [[Amahi on a VM]]: Installing Amahi in a Virtual Machine
* [[Express CD]]: Headless all-in-one Install

=Getting Started=

First you can take a look at the [[Special:PopularPages|Popular Pages]] to see if your topic of interest is there. Otherwise find the major topics below in groups.

'''[[Storage and file sharing]]''' - How to store your music, pictures, movies and other files and share them with the rest of the devices in your network.
* Accessing files from:
#[[SharingToMacOSX|Mac OS X]]
#[[SharingToLinux|Other Linux Systems]]

'''Networking''' - Using your HDA to manage your home network
* [[Networking - Static IPs]]: How to assign static IPs to your network devices.
* [[Punching DNS Holes]]: How to assign IP addresses outside of your network for your home domain.

'''Remote Access''' - Accessing your HDA from anywhere on the network
* Accessing your HDA remotely from:
# [[VPN]]: '''outside''' your network.
# [[VNC]]: '''inside''' your network (e.g. if your HDA is "headless").
* [[FreeNX]]: Accessing your HDA with FreeNX
* SSH based access to your HDA: [[Key-Based SSH Logins]]

= Troubleshooting =
* [[Installation troubleshooting]]
* [[Network troubleshooting]]
* [[Shares troubleshooting]]
* [[VPN troubleshooting]]
* [[Vista Networking Issue]]
* [[Disabling Automatic Updates]]
* [[Data Recovery]]

=Doing More=
* '''[[:Category:Apps|Apps Directory]]:''' These are the help pages for some of the apps in the [http://www.amahi.org/apps/ Apps Gallery]
* [[Adding an HDA networked printer]]: Guide to set up print server on your HDA.
* [[Backups]]: Guides on backup and restore: [[XPBackups|Windows XP]], [[VistaWindows7Backups|Windows Vista and Windows 7]], [[Sbackup|Ubuntu Linux]], and [[Backups#Mac_OS_X|MacOSX]].
* [[Adding a second hard drive to your HDA]]: How to add a additional hard drives.
* [[Greyhole]]: Add drive pooling to your HDA (ie Turn multiple drives into one!)
* [[RAID]] guides for [[RAID 1]] and [[RAID 5]]
* [[DropBox|Add DropBox service]]: Allows a HDA DropBox share folder to automatically synchronize with a DropBox account.
* [[Database_Backup|Automatic Database Backup]]: Automatically have your HDA database backed up daily.
* [[Enable_Outgoing_Emails|Enable Outgoing Mail]]: Use your ISP to send mail from your HDA.
* [[Monitor System Logs via E-mail]]: Sends logs to designated e-mail address daily.

=Using Applications=
For a more detailed list refer to the '''[[:Category:Apps|Apps Directory]]'''
* Remote File Management using [http://www.amahi.org/apps/ajaxplorer AjaxPlorer]
* [[Calendars]]: How to use the calendar server in the HDA, including Outlook and iCal sync.
* [[Dashboard_Design|Dashboard]]: Using the amahi Dashboard

=Getting "Under the Hood"=
* [[Password protection for your HDA setup pages]]: Guide to set up password protection to your HDA pages.
* [[How to Create a new Theme]]
* [[Linux-hda_commands|Linux/HDA Commands]]: Common used command for linux and HDA.
* [[Webapps | Making your own web apps]]: how to make your own web apps, with your code or other's code
* [[Hosting a website | Hosting your own web site]]: how to host your own web site on the web from your Amahi home server
* [[Changing your DNS provider]]
* [[Configuring OpenDNS]]
* [[How_to_use_two_HDA_on_the_same_network| Use two HDAs on same network]]

=Contribute=
* [[Translate Amahi]] to your language
* [http://bugs.amahi.org Create a Bug/Feature/Support ticket!]
* Contribute by:
# [[Contribute|Packaging apps]]
# [[Tester program|Testing apps]]
* [http://www.flickr.com/photos/amahi/sets/72157606815797764/ Amahi Wallpapers]
* [http://www.flickr.com/photos/amahi/sets/72157606828513620/ Amahi Banners]

= Roadmap & Development =
* [[Fedora 14]]: Active Development
* [[Ubuntu]]: Limited Development
* [[CentOS]]: Development Stalled

= Related Links =
* [[Developers]]: How to write HDA apps, questions, API suggestions, etc.
* [[Credits]]: How are we doing all this? We have many OSS projects to thank!

Greyhole

2011-03-06T04:33:33Z

Uslackr:

[[Category:apps]]
<div style="border: 1px solid #A3B1BF; padding: .8em 1em; background-color: #E6F2FF; margin: 0px 1em;">
'''NEW:''' [http://code.google.com/p/greyhole/wiki/MigrateFromWHS Widows Home Server Drive Extender Migration Guide]

'''NEW:''' [[Greyhole troubleshooting]] guide
</div>

== What is Greyhole ==

[http://greyhole.pommepause.com/ Greyhole] is Amahi's [[Storage pooling]] technology. Storage Pooling combines the space of multiple disk drives and makes them look as if they were all part of a single pool of disk space.
Specifically, Greyhole:
* Combines the space from multiple drives into a single volume
* Distributes files across all drives in the pool
* Creates multiple copies of files in admin-specified shares

This feature is installed by default, but requires a few simple steps to begin utilizing the features.

You can add additional drives to your hda and prepare them for use in Greyhole by following [[Adding a second hard drive to your HDA|this tutorial]].

To add a drive to your Greyhole storage pool. Open your HDA dashboard and navigate to the Shares tab. Then click on the Storage Pool sub-category. You will see a page similar to the one below.

== Important Warnings ==
<div style="color:darkred">You should '''never''' change or delete files in the shared directories (''/var/hda/files/*'' by default) directly on the HDA, using the terminal, or the Gnome file browser, for the shares for which you checked the ''Uses pool'' option in the Amahi dashboard. If you want to work with files on Greyhole shares on the HDA, you should [[Mount Shares Locally]].<br/>
You should be safe reading existing files directly, or adding new files directly, as long as don't care that your new files will only be moved into the storage pool during the next check, which runs automatically at midnight (or manually using ''greyhole --fsck''). Until then, your new files will be stored in your shared directories (normally ''/var/hda/files/share_name/'').

Also, touching anything inside the '''gh''' directories that Greyhole creates at the root of your partitions is a recipe for disaster.

We [[Greyhole not on root | strongly discourage you from using the root partition in a drive pool]].
</div><br/><br/>

== First things first ==

You need to go in the Settings tab, and enable '''Advanced Settings'''.<br/>
Without Advanced Settings enabled, you won't see the following page and options.

== For Storage Pool (Partitions) ==

[[File:Storage_Pool_1.png|600px|thumb|left]]

Select the drives you want available for your storage pool.

== Greyhole options ==

The next step is to select the share you want to replicate across the pool.

From the Shares tab, select the Shares sub-catagory. We chose the Pictures share for this tutorial.

[[File:Greyhole_Options_1.png|600px|thumb|left]]

Check the option for "Uses pool" and choose the number of drives to replicate this share. In this instance we have chosen to use all drives available to the greyhole pool.

Note: Greyhole is not a backup solution. If a file is removed, all copies are removed.

== Greyhole advanced options ==

You can further configure Greyhole by manually editing the following file:<br/>
'''/var/hda/platform/html/config/greyhole.yml'''

To see what options are available, and what they do, refer to the [http://greyhole.googlecode.com/svn/trunk/greyhole.example.conf sample greyhole.conf] provided with Greyhole.

greyhole.yml is in in YAML format. Most of it should be easy enough to modify. The only exception would be the sticky_files (and optional sticky_into) options.<br/>
Here's an example of how those should appear:

To specify the following to Greyhole in greyhole.conf:

sticky_files = Music/
sticky_files = Videos/Movies/
stick_into = /mnt/hdd1/gh
stick_into = /mnt/hdd5/gh
sticky_files = Backups/CrashPlan/
stick_into = /mnt/hdd0/gh

one should specify this in the greyhole.yml file, where '''precise indentation matters''':

sticky_files:
- - Music/
- - Videos/Movies/
- - /mnt/hdd1/gh
- /mnt/hdd5/gh
- - Backups/CrashPlan/
- - /mnt/hdd0/gh

For your changes to be effective, you'll need to force Amahi to regenerate the greyhole.conf file. You can do so by editing a share, clicking it's path, and just clicking the Save button without actually changing the path.

== Copying your data into Greyhole shares the first time ==

When you start using Greyhole, you might want to copy or move all your exiting files into your new shares that use the storage pool.

Note: This is not necessary if your files are already in Amahi shares. If they are there, and you enable the ''Uses pool'' option in the Amahi dashboard, the files will start getting moved around into the drives in your storage pool during the night (starting at midnight), when the nightly storage pool check starts.<br/>
The instructions below are for users who have more data to copy into the Greyhole shares than their currently free space in the /var/hda/files/ folder.

One way to do that is to mount the shares that use the Greyhole storage pool, either on the HDA itself, or on a client computer on your local network, and copy your data from their existing location into the mounted shares.
This can be time consuming, but it is the safest way to use Greyhole.

Another way to move your files from their current location into the storage pool is to share their current location using an Amahi share that ''Uses pool'', then let Greyhole nightly check move the files from there into the pool.

Here's a more detailed walkthrough for this method:

# Setup the Greyhole Storage Pool in the Amahi dashboard, Shares > Storage Pool page.
# Go in the Shares > Shares page. In there, make sure you have an existing share for each share you have data for. Create new ones if you need, remove the ones you don't need.
# Edit the ''path'' of each of those shares, and enter the current location of your existing data. For example, the Movies share could have a path = ''/media/External Drive/Movies''
# Enable the ''Uses pool'' option for each of your shares, and select the number of extra copies you'd like, if any.
# Now, you either need to wait for Greyhole'S nightly check to start, or you can start it manually from a terminal, as root, using this command: greyhole --fsck
# Monitor /var/log/greyhole.log to see when the ''fsck'' operation is done.
# Once ''fsck'' is done, your data has now been moved into the Greyhole storage pool (in the drives you selected in Shares > Storage Pool). All that should be left in the previous location of your data (''/media/External Drive/Movies'' from the previous example) should be symbolic links pointing to the new file copies. If the previous location is just empty directories (no symlinks), do not panic. This is normal if your previous location is an NTFS or FAT partition (drive).
# Move all those directories / symlinks from there into the correct folders in /var/hda/files/share_name
# Back in the Amahi dashboard, edit the path of the shares once again, and put back ''/var/hda/files/share_name'' (i.e. the folders where you moved the symbolic links).
# If you used an NTFS or FAT partition for the previous location, you'll need another fsck to create the symlinks where they should be. Either wait for midnight, or launch it manually, from a command line, as root: ''greyhole --fsck''

You're done. All your existing data is now stored in the various drives included in your storage pool, and are accessible via the Samba shares you have defined in the Amahi dashboard.

== Adding a new drive to your HDA and storage pool ==
This wiki page discusses how to add a new drive to your HDA and to your greyhole storage pool
[[Adding_a_second_hard_drive_to_your_HDA]]

== /media ==
Including any drive mounted as /media/Something in your storage pool is usually a bad idea.<br/>
Those mounts are created by the ''gnome-automounter'', which requires you to be logged in into X (Gnome) to become available.<br/>
This will create issues with Greyhole, which expects drives to always be available, and will take action when some of them are missing.

Follow this guide to [[Adding a second hard drive to your HDA|permanently mount your drives]], before you include them in your storage pool.

== Monitoring Greyhole ==
Sometimes you might want to monitor what Greyhole is doing, for example when writing data to your greyhole shares for the first time. Here are a few commands you can type in a terminal to follow along.

'''Scrolling view of total Greyhole operations queue:'''
while [ 1 == 1 ]; do greyhole --view-queue | grep Total; sleep 60; done

'''Scrolling log of what files Greyhole is working on right now:'''
tail -f /var/log/greyhole.log

== Convert Greyhole from SQLite to MySQL ==
Greyhole is at the time of writing using SQLite as the default database for queueing up tasks on Amahi. This is unqie to Amahi as Greyhole was originally designed to use MySQL for this task.

There are some major performance benefits to using MySQL over SQLite when writing large amounts of files. Switching can be especially useful when moving data to greyhole shares for the first time. For now there is a script you can run if you want to switch over. This script has been tested to be safe while greyhole is working but should be used with discresion.

''To Convert to MySQL, run as root:''

/usr/share/greyhole/db_migration-sqlite2mysql.sh

To see what DB engine is Greyhole using, do this:

grep db_engine /etc/greyhole.conf

== Disable Greyhole ==
For those who do not use Greyhole, you can disable it. This is based on the fact you never have used it by enabling 'Uses pool' on any share. Recommend using extreme caution as this could have unpredictable results.

Perform the following steps as user '''root''':

chkconfig greyhole off
rm /etc/monit.d/greyhole.conf
service monit restart
service greyhole stop

'''DO NOT''' attempt to remove the Greyhole package as it is a dependency of the HDA software. Doing so will break your HDA.

= Testing and Reliability =

Check out the [[Greyhole grinder]] to help make Greyhole rock solid.

= Reconnect the Greyhole storage pool after re-install of Fedora / Amahi =

After re-install, recreate all your shares exacty as they were.<br>
Add the shares to the storage pool.<br>
As root, run greyhole --fsck.<br>
This will recreate the symlinks in the landing zone /var/hda/files.<br>

= Greyhole Troubleshooting =

[[Greyhole troubleshooting]] guide

Main Page

2011-03-06T04:22:28Z

Uslackr:

=Welcome to the Amahi Wiki=
<big>
'''CURRENT STABLE RELEASE:''' [[Amahi 6.0]], on [[Fedora 14]]
</big>

----

__TOC__<br />
This is where Amahi community members can best help other Amahi users. Please add or edit any information in the Wiki that you feel is lacking, missing, or need improvement.

----

* [[Intro]]: Introduction to the Amahi HDA
* [[Requirements]]: What's needed
* [http://www.amahi.org/faq FAQ]: Frequently Asked Questions
* [[Feedback]]: Issues, feedback.

For questions or help do not hesitate to [[contact us]].

= Installation =
* See [http://www.amahi.org/support/instructions Installation instructions] in your control panel at amahi.org
* [[Self-install]]: Alternative, unsupported installation instructions
* [[Amahi on a VM]]: Installing Amahi in a Virtual Machine
* [[Express CD]]: Headless all-in-one Install

=Getting Started=

First you can take a look at the [[Special:PopularPages|Popular Pages]] to see if your topic of interest is there. Otherwise find the major topics below in groups.

'''[[Storage and file sharing]]''' - How to store your music, pictures, movies and other files and share them with the rest of the devices in your network.
* Accessing files from:
#[[SharingToMacOSX|Mac OS X]]
#[[SharingToLinux|Other Linux Systems]]

'''Networking''' - Using your HDA to manage your home network
* [[Networking - Static IPs]]: How to assign static IPs to your network devices.
* [[Punching DNS Holes]]: How to assign IP addresses outside of your network for your home domain.

'''Remote Access''' - Accessing your HDA from anywhere on the network
* Accessing your HDA remotely from:
# [[VPN]]: '''outside''' your network.
# [[VNC]]: '''inside''' your network (e.g. if your HDA is "headless").
* [[FreeNX]]: Accessing your HDA with FreeNX
* SSH based access to your HDA: [[Key-Based SSH Logins]]

= Troubleshooting =
* [[Installation troubleshooting]]
* [[Network troubleshooting]]
* [[Shares troubleshooting]]
* [[VPN troubleshooting]]
* [[Vista Networking Issue]]
* [[Disabling Automatic Updates]]
* [[Data Recovery]]

=Doing More=
* '''[[:Category:Apps|Apps Directory]]:''' These are the help pages for some of the apps in the [http://www.amahi.org/apps/ Apps Gallery]
* [[Adding an HDA networked printer]]: Guide to set up print server on your HDA.
* [[Backups]]: Guides on the multiple ways to backup and restore: from [[PBA|full-disk backup]] to incremental backups for [[XPBackups|Windows XP]], [[VistaBackups|Windows Vista]], [[Win7Backups|Windows 7]], [[Sbackup|Ubuntu Linux]], and [[Backups#Mac_OS_X|Macs]].
* [[Adding a second hard drive to your HDA]]: How to add a additional hard drives.
* [[Greyhole]]: Add drive pooling to your HDA (ie Turn multiple drives into one!)
* [[RAID]] guides for [[RAID 1]] and [[RAID 5]]
* [[DropBox|Add DropBox service]]: Allows a HDA DropBox share folder to automatically synchronize with a DropBox account.
* [[Database_Backup|Automatic Database Backup]]: Automatically have your HDA database backed up daily.
* [[Enable_Outgoing_Emails|Enable Outgoing Mail]]: Use your ISP to send mail from your HDA.
* [[Monitor System Logs via E-mail]]: Sends logs to designated e-mail address daily.

=Using Applications=
For a more detailed list refer to the '''[[:Category:Apps|Apps Directory]]'''
* Remote File Management using [http://www.amahi.org/apps/ajaxplorer AjaxPlorer]
* [[Calendars]]: How to use the calendar server in the HDA, including Outlook and iCal sync.
* [[Dashboard_Design|Dashboard]]: Using the amahi Dashboard

=Getting "Under the Hood"=
* [[Password protection for your HDA setup pages]]: Guide to set up password protection to your HDA pages.
* [[How to Create a new Theme]]
* [[Linux-hda_commands|Linux/HDA Commands]]: Common used command for linux and HDA.
* [[Webapps | Making your own web apps]]: how to make your own web apps, with your code or other's code
* [[Hosting a website | Hosting your own web site]]: how to host your own web site on the web from your Amahi home server
* [[Changing your DNS provider]]
* [[Configuring OpenDNS]]
* [[How_to_use_two_HDA_on_the_same_network| Use two HDAs on same network]]

=Contribute=
* [[Translate Amahi]] to your language
* [http://bugs.amahi.org Create a Bug/Feature/Support ticket!]
* Contribute by:
# [[Contribute|Packaging apps]]
# [[Tester program|Testing apps]]
* [http://www.flickr.com/photos/amahi/sets/72157606815797764/ Amahi Wallpapers]
* [http://www.flickr.com/photos/amahi/sets/72157606828513620/ Amahi Banners]

= Roadmap & Development =
* [[Fedora 14]]: Active Development
* [[Ubuntu]]: Limited Development
* [[CentOS]]: Development Stalled

= Related Links =
* [[Developers]]: How to write HDA apps, questions, API suggestions, etc.
* [[Credits]]: How are we doing all this? We have many OSS projects to thank!

Talk:Main Page

2011-03-06T03:25:32Z

Uslackr: Created page with "The Greyhole page should be added in above or below the RAID items on this page"

The Greyhole page should be added in above or below the RAID items on this page

Backups

2011-03-06T03:15:09Z

Uslackr:

Since the Amahi HDA apears as a NAS to you network, it is a natural destination for the backups from your network PCs. All backups are initiated by the client computer on to the HDA.

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

We have documented ways to conduct 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)

=== Third-Party (Free) Backup Software ===
There are a number of great open source or free backup programs out there that you can use free (commercial users should check license details). Here is a partial list (feel free to add others):

{|
!Package
!License/Cost
|-
|[http://www.educ.umu.se/~cobian/cobianbackup.htm Cobian Backup]
|Free, later version no longer open source
|-
|[http://www.runtime.org/driveimage-xml.htm DriveImage XML]
|Free for personal use
|-
|[http://www.areca-backup.org/index.php Areca Backup]
|Open source - GPLv2
|-
|[http://thebackupmonkey.blogspot.com/ Bonkey]
|Open source - Apache 2.0
|-
|[http://www.hiteksoftware.com/jaba/ JaBack]
|Free
|-
|[http://www.nasbackup.com/wiki/Introduction NasBackup]
|Open source - no longer under active devel.
|-
|[http://www.aboutmyip.com/AboutMyXApp/DeltaCopy.jsp DeltaCopy]
|Open source - GPL
|-
|[http://www.allwaysync.com/ Allway Sync]
|Free for non-commercial use; some limits
|-
|[http://www.gfi.com/backup-hm GFI Backup]
|Free for non-commercial use
|-
|[http://backuppc.sourceforge.net/ BackupPC]
|Open source - GPL
|-
|[http://synchronicity.sourceforge.net/ Create Synchronicity]
|Open source - GPL
|-
|}

== Windows 7 and Vista Backups ==

The built in backup tool for Windows 7 and Vista are very similar. Read the section [[VistaWindows7Backups | 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

Install [[AFP]] and Avahi:

* in Applevolume.default add

<code>~/ "$u" allow:UserName rwlist:UserName,@users cnidscheme:cdb<br>
/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

''Update: Recent versions of timemachine do not appear to respect the max size of the sparsebundle and will cheerfully fill up your disk. To fix this, you need a more recent version of netatalk (2.0.5+?), which has an option to tell fibs about the size of the disk, hence limiting timemachine's space consumption. Fedora 14 has netatalk 2.1.4...''

== Full Disk "Bare Metal" Backups ==
Bare metal backups are no longer available as a feature in current Amahi releases on F12 & F14. Note: Older releases used the Personal Backup Appliance, or [[PBA | PBA]], with the collaboration of the PBA leader, Roland Hui. PBA is an application to do hard disk clones, backups and restores but appears to no longer be under development

== Using Symantec Backup Exec ==
=== System Recovery 8.5 ===

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 [http://www.symantec.com/norton/save-restore "Save & Restore"] I'm not overly familiar with this product but it replaces Norton "Ghost" in most markets. 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.

[[Category: Services]]

Windows Backups

2011-03-06T03:09:41Z

Uslackr: moved VistaBackups to VistaWindows7Backups: No need for redundant page

If you use Windows Vista, it comes with a straightforward way to backup your files (not the OS) regularly to the HDA.

To use it, go to the Backup and restore Center (Start -> Control Panel -> Backup & Restore):

[[Image:VistaBackups1.png|border|500px]]

In it, you can configure settings (in "Change settings) to make Vista do backups to your HDA daily, weekly or monthly.

[[Image:VistaBackups2.png|border|500px]]

All you have to specify is that you want to backup to the network, e.g. to

\\hda\backups\[machine]

Where [machine] is your machine name.

The first time it runs it will back up all your files. Subsequent backups are incremental: only what changed since last backup is saved.

[[Image:VistaBackups3.png|border]]

It saves your files in the form of zip files, to they are easy to recover, even without using the vista "Restore Files" program.

VistaBackups

2011-03-06T03:09:41Z

Uslackr: moved VistaBackups to VistaWindows7Backups: No need for redundant page

#REDIRECT [[VistaWindows7Backups]]

Backups

2011-03-06T02:57:02Z

Uslackr:

Since the Amahi HDA apears as a NAS to you network, it is a natural destination for the backups from your network PCs. All backups are initiated by the client computer on to the HDA.

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

We have documented ways to conduct 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)

=== Third-Party (Free) Backup Software ===
There are a number of great open source or free backup programs out there that you can use free (commercial users should check license details). Here is a partial list (feel free to add others):

{|
!Package
!License/Cost
|-
|[http://www.educ.umu.se/~cobian/cobianbackup.htm Cobian Backup]
|Free, later version no longer open source
|-
|[http://www.runtime.org/driveimage-xml.htm DriveImage XML]
|Free for personal use
|-
|[http://www.areca-backup.org/index.php Areca Backup]
|Open source - GPLv2
|-
|[http://thebackupmonkey.blogspot.com/ Bonkey]
|Open source - Apache 2.0
|-
|[http://www.hiteksoftware.com/jaba/ JaBack]
|Free
|-
|[http://www.nasbackup.com/wiki/Introduction NasBackup]
|Open source - no longer under active devel.
|-
|[http://www.aboutmyip.com/AboutMyXApp/DeltaCopy.jsp DeltaCopy]
|Open source - GPL
|-
|[http://www.allwaysync.com/ Allway Sync]
|Free for non-commercial use; some limits
|-
|[http://www.gfi.com/backup-hm GFI Backup]
|Free for non-commercial use
|-
|[http://backuppc.sourceforge.net/ BackupPC]
|Open source - GPL
|-
|[http://synchronicity.sourceforge.net/ Create Synchronicity]
|Open source - GPL
|-
|}

== Windows 7 Backups ==
How to needs to be completed. Go [[Win7Backups|here]] to update the page.

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

Install [[AFP]] and Avahi:

* in Applevolume.default add

<code>~/ "$u" allow:UserName rwlist:UserName,@users cnidscheme:cdb<br>
/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

''Update: Recent versions of timemachine do not appear to respect the max size of the sparsebundle and will cheerfully fill up your disk. To fix this, you need a more recent version of netatalk (2.0.5+?), which has an option to tell fibs about the size of the disk, hence limiting timemachine's space consumption. Fedora 14 has netatalk 2.1.4...''

== Full Disk "Bare Metal" Backups ==
Bare metal backups are no longer available as a feature in current Amahi releases on F12 & F14. Note: Older releases used the Personal Backup Appliance, or [[PBA | PBA]], with the collaboration of the PBA leader, Roland Hui. PBA is an application to do hard disk clones, backups and restores but appears to no longer be under development

== Using Symantec Backup Exec ==
=== System Recovery 8.5 ===

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 [http://www.symantec.com/norton/save-restore "Save & Restore"] I'm not overly familiar with this product but it replaces Norton "Ghost" in most markets. 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.

[[Category: Services]]

Backups

2011-03-06T02:44:33Z

Uslackr: added license info

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 =
Bare metal backups are not available as a feature in current Amahi releases on F12 & F14. Note: Older releases used the Personal Backup Appliance, or [[PBA | PBA]], with the collaboration of the PBA leader, Roland Hui. PBA is an application to do hard disk clones, backups and restores but appears to no longer be under development

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

We have documented ways to conduct 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)

== Third-Party (Free) Backup Software ==
There are a number of great open source or free backup programs out there that you can use absolutely free. Here is a partial list (please add others:
#[http://www.educ.umu.se/~cobian/cobianbackup.htm Cobian Backup] (free, no longer open source)
#[http://www.runtime.org/driveimage-xml.htm DriveImage XML] (Free for personal use)
#[http://www.areca-backup.org/index.php Areca Backup] (Open source - GPLv2
#[http://thebackupmonkey.blogspot.com/ Bonkey] (Open source - Apache 2.0)
#[http://www.hiteksoftware.com/jaba/ JaBack] (Free)
#[http://www.nasbackup.com/wiki/Introduction NasBackup] (Open source - no longer under active devel.)
#[http://www.aboutmyip.com/AboutMyXApp/DeltaCopy.jsp DeltaCopy] (Open source - GPL)
#[http://www.allwaysync.com/ Allway Sync] (Free for non-commercial use; some limits)
#[http://www.gfi.com/backup-hm GFI Backup] (Free for non-commercial use)
#[http://backuppc.sourceforge.net/ BackupPC] (Open source - GPL)
#[http://synchronicity.sourceforge.net/ Create Synchronicity] (Open source - GPL)
{|
!Package
!License/Cost
|-
|[http://www.educ.umu.se/~cobian/cobianbackup.htm Cobian Backup]
|Free, later version no longer open source
|-
|[http://www.runtime.org/driveimage-xml.htm DriveImage XML]
|Free for personal use
|-
|[http://www.areca-backup.org/index.php Areca Backup]
|Open source - GPLv2
|-
|[http://thebackupmonkey.blogspot.com/ Bonkey]
|Open source - Apache 2.0
|-
|[http://www.hiteksoftware.com/jaba/ JaBack]
|Free
|-
|[http://www.nasbackup.com/wiki/Introduction NasBackup]
|Open source - no longer under active devel.
|-
|[http://www.aboutmyip.com/AboutMyXApp/DeltaCopy.jsp DeltaCopy]
|Open source - GPL
|-
|[http://www.allwaysync.com/ Allway Sync]
|Free for non-commercial use; some limits
|-
|[http://www.gfi.com/backup-hm GFI Backup]
|Free for non-commercial use
|-
|[http://backuppc.sourceforge.net/ BackupPC]
|Open source - GPL
|-
|[http://synchronicity.sourceforge.net/ Create Synchronicity]
|Open source - GPL
|-
|}

= Windows 7 Backups =
How to needs to be completed. Go [[Win7Backups|here]] to update the page.

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

Install [[AFP]] and Avahi:

* in Applevolume.default add

<code>~/ "$u" allow:UserName rwlist:UserName,@users cnidscheme:cdb<br>
/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

''Update: Recent versions of timemachine do not appear to respect the max size of the sparsebundle and will cheerfully fill up your disk. To fix this, you need a more recent version of netatalk (2.0.5+?), which has an option to tell fibs about the size of the disk, hence limiting timemachine's space consumption. Fedora 14 has netatalk 2.1.4...''

= 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 [http://www.symantec.com/norton/save-restore "Save & Restore"] I'm not overly familiar with this product but it replaces Norton "Ghost" in most markets. 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.

[[Category: Services]]

Backups

2011-03-06T02:29:15Z

Uslackr:

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 =
Bare metal backups are not available as a feature in current Amahi releases on F12 & F14. Note: Older releases used the Personal Backup Appliance, or [[PBA | PBA]], with the collaboration of the PBA leader, Roland Hui. PBA is an application to do hard disk clones, backups and restores but appears to no longer be under development

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

We have documented ways to conduct 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)

== Third-Party (Free) Backup Software ==
There are a number of great open source or free backup programs out there that you can use absolutely free. Here is a partial list (please add others:
#[http://www.educ.umu.se/~cobian/cobianbackup.htm Cobian Backup] (free, no longer open source)
#[http://www.runtime.org/driveimage-xml.htm DriveImage XML] (Free for personal use)
#[http://www.areca-backup.org/index.php Areca Backup] (Open source - GPLv2
#[http://thebackupmonkey.blogspot.com/ Bonkey] (Open source - Apache 2.0)
#[http://www.hiteksoftware.com/jaba/ JaBack] (Free)
#[http://www.nasbackup.com/wiki/Introduction NasBackup] (Open source - no longer under active devel.)
#[http://www.aboutmyip.com/AboutMyXApp/DeltaCopy.jsp DeltaCopy] (Open source - GPL)
#[http://www.allwaysync.com/ Allway Sync] (Free for non-commercial use; some limits)
#[http://www.gfi.com/backup-hm GFI Backup] (Free for non-commercial use)
#[http://backuppc.sourceforge.net/ BackupPC] (Open source - GPL)
#[http://synchronicity.sourceforge.net/ Create Synchronicity]
#[http://www.uk-dissertation.com/ Dissertations]

= Windows 7 Backups =
How to needs to be completed. Go [[Win7Backups|here]] to update the page.

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

Install [[AFP]] and Avahi:

* in Applevolume.default add

<code>~/ "$u" allow:UserName rwlist:UserName,@users cnidscheme:cdb<br>
/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

''Update: Recent versions of timemachine do not appear to respect the max size of the sparsebundle and will cheerfully fill up your disk. To fix this, you need a more recent version of netatalk (2.0.5+?), which has an option to tell fibs about the size of the disk, hence limiting timemachine's space consumption. Fedora 14 has netatalk 2.1.4...''

= 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 [http://www.symantec.com/norton/save-restore "Save & Restore"] I'm not overly familiar with this product but it replaces Norton "Ghost" in most markets. 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.

[[Category: Services]]

Backups

2011-03-06T02:09:33Z

Uslackr:

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 =
Bare metal backups are not available as a feature in current Amahi releases on F12 & F14. Note: Older releases used the Personal Backup Appliance, or [[PBA | PBA]], with the collaboration of the PBA leader, Roland Hui. PBA is an application to do hard disk clones, backups and restores but appears to no longer be under development

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

We have documented ways to conduct 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)

== Third-Party (Free) Backup Software ==
There are a number of great open source backup programs out there that you can use absolutely free. Here is a partial list (please add others:
#[http://www.educ.umu.se/~cobian/cobianbackup.htm Cobian Backup]
#[http://www.runtime.org/driveimage-xml.htm DriveImage XML]
#[http://www.areca-backup.org/index.php Areca Backup]
#[http://thebackupmonkey.blogspot.com/ Bonkey]
#[http://www.hiteksoftware.com/jaba/ JaBack]
#[http://www.nasbackup.com/wiki/Introduction NasBackup]
#[http://www.aboutmyip.com/AboutMyXApp/DeltaCopy.jsp DeltaCopy]
#[http://www.allwaysync.com/ Allway Sync]
#[http://www.gfi.com/backup-hm GFI Backup]
#[http://backuppc.sourceforge.net/ BackupPC]
#[http://synchronicity.sourceforge.net/ Create Synchronicity]
#[http://www.uk-dissertation.com/ Dissertations]

= Windows 7 Backups =
How to needs to be completed. Go [[Win7Backups|here]] to update the page.

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

Install [[AFP]] and Avahi:

* in Applevolume.default add

<code>~/ "$u" allow:UserName rwlist:UserName,@users cnidscheme:cdb<br>
/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

''Update: Recent versions of timemachine do not appear to respect the max size of the sparsebundle and will cheerfully fill up your disk. To fix this, you need a more recent version of netatalk (2.0.5+?), which has an option to tell fibs about the size of the disk, hence limiting timemachine's space consumption. Fedora 14 has netatalk 2.1.4...''

= 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 [http://www.symantec.com/norton/save-restore "Save & Restore"] I'm not overly familiar with this product but it replaces Norton "Ghost" in most markets. 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.

[[Category: Services]]

Backups

2011-03-06T02:07:33Z

Uslackr:

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 =
Bare metal backups are not available as a feature in current Amahi releases on F12 & F14. Note: Older releases used the Personal Backup Appliance, or [[PBA | PBA]], with the collaboration of the PBA leader, Roland Hui. PBA is an application to do hard disk clones, backups and restores but appears to no longer be under development

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

We have documented ways to conduct 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.

== Third-Party (Free) Backup Software ==
There are a number of great backup programs out there that you can use absolutely free. Here is my list:
#[http://www.educ.umu.se/~cobian/cobianbackup.htm Cobian Backup]
#[http://www.runtime.org/driveimage-xml.htm DriveImage XML]
#[http://www.areca-backup.org/index.php Areca Backup]
#[http://thebackupmonkey.blogspot.com/ Bonkey]
#[http://www.hiteksoftware.com/jaba/ JaBack]
#[http://www.nasbackup.com/wiki/Introduction NasBackup]
#[http://www.aboutmyip.com/AboutMyXApp/DeltaCopy.jsp DeltaCopy]
#[http://www.allwaysync.com/ Allway Sync]
#[http://www.gfi.com/backup-hm GFI Backup]
#[http://backuppc.sourceforge.net/ BackupPC]
#[http://synchronicity.sourceforge.net/ Create Synchronicity]
#[http://www.uk-dissertation.com/ Dissertations]

= Windows 7 Backups =
How to needs to be completed. Go [[Win7Backups|here]] to update the page.

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

Install [[AFP]] and Avahi:

* in Applevolume.default add

<code>~/ "$u" allow:UserName rwlist:UserName,@users cnidscheme:cdb<br>
/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

''Update: Recent versions of timemachine do not appear to respect the max size of the sparsebundle and will cheerfully fill up your disk. To fix this, you need a more recent version of netatalk (2.0.5+?), which has an option to tell fibs about the size of the disk, hence limiting timemachine's space consumption. Fedora 14 has netatalk 2.1.4...''

= 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 [http://www.symantec.com/norton/save-restore "Save & Restore"] I'm not overly familiar with this product but it replaces Norton "Ghost" in most markets. 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.

[[Category: Services]]

Vista Networking Issue

2011-03-04T18:02:13Z

Uslackr:

Sometimes, Vista and Windows 7 don't resolve the host-only Amahi uses
Here's a possible fix that worked for me on Vista/Windows 7

For Windows Vista
# From the menu, select ''Control Panel'' then ''Network Connections''
# Right click your ethernet card (or similar) and select properties
# Select ''Internet Protocol Version 4'' and press the properties button
# Click the "Advanced" button
# Select the DNS tab
# Press the "Append these DNS suffixes (in order)" button
# Add your home server's domain name (eg. home.com)
# Press the required OKs, apply, close ...

For Windows 7
# In Control Panel select ''Network And Sharing Center''
# In the left margin, select 'Change adapter settings''
# Right click your ethernet card (or similar) and select ''properties''
# Select ''Internet Protocol Version 4'' and press the properties button
# Click the ''Advanced'' button
# Select the ''DNS'' tab
# Press the ''Append these DNS suffixes (in order)'' button
# Add your home server's domain name (eg. home.com)
# Press the required OKs, apply, close ...

Vista Networking Issue

2011-03-04T17:59:51Z

Uslackr:

Some times, Vista and Windows 7 don't operate well with short URLs.

Here's a fix that worked for me (Vista/Windows 7 specific)

For Windows Vista
In Control Panel/network connections
# Right click your ethernet card (or similar) and select properties
# Select ''Internet Protocol Version 4'' and press the properties button
# Click the "Advanced" button
# Select the DNS tab
# Press the "Append these DNS suffixes (in order)" button
# Add your home server's domain name (eg. home.com)
# Press the required OKs, apply, close ...

All should work correctly now

For Windows 7
# In Control Panel select ''Network And Sharing Center''
# In the left margin, select 'Change adapter settings''
# Right click your ethernet card (or similar) and select ''properties''
# Select ''Internet Protocol Version 4'' and press the properties button
# Click the ''Advanced'' button
# Select the ''DNS'' tab
# Press the ''Append these DNS suffixes (in order)'' button
# Add your home server's domain name (eg. home.com)
# Press the required OKs, apply, close ...

Network troubleshooting

2011-03-04T17:55:06Z

Uslackr:

<div style="border: 1px solid #B66; padding: .5em 1em; color: #000; background-color: #FEE; margin: 3px 3px 1em 3px;">
'''Rule #1: Do NOT turn off the DHCP server in your router until your HDA has full network connectivity'''
</div>

Your HDA should be capable of browsing all the major sites and http://www.amahi.org before doing anything else.

If you do not have connectivity, you may want to check that the settings that you programmed in amahi.org for your network and router match that of your actual network and the router in it. Amahi assumes a regular, typical home network and the settings there should be done to match what you have. The most common error is that the gateway is not set up properly. We have a page on how to [[Find Your Gateway IP]].

Please note that '''only the first NIC/ethernet card (eth0)''' is supported out of the box. If you have two, please make sure you use eth0 for the LAN where your Amahi HDA resides. There is an unsupported way to support amahi on the [[ETH1|eth1]] device.

If a wireless network connection is all you have available, you may want to experiment with running [[Amahi over wlan0|Amahi_over_wlan0]]. This is not a well tested or recommended approach, though, so expect problems of some kind.

= Identify the problem =

To help you identify a network problem you might have, try using the [http://net.pommepause.com/network_troubleshooter/ Interactive Amahi Network Troubleshooter].
If it fails along the way, it will give you instructions on how to get additional help, and how to provide us with the information we need to help you understand and fix the problem.

= Additional troubleshooting =

If ping hda does not work it might be that you have a problem with DNS journalling.
Especially if /var/named/data/named.run contains a line like<br>
zone home.com/IN: journal rollforward failed: journal out of sync with zone<br>
you must delete /var/named/*/*jnl and issue the command hdactl-hup<br>
Then retry ping hda to see if things are working.

<b>If the Network Troubleshooter above can't help</b>, you can try the steps in the [[More network troubleshooting]] page.

= Non Default Network Set-ups =

If your router does not have an IP of 192.168.1.1, the following command will make the process easy to allow your HDA to work:

su -

[enter root password]

hda-change-gw [gateway IP]

Example if your default gateway (router) has an IP of 192.168.0.1:

hda-change-gw 192.168.0.1

Note: You will need to restart your server after applying the change.

= When all else fails =

In some cases, it could be the client OS causing issues.

One known issue is the [[Vista_Networking_Issue]]

There are some special instructions if you have an [[Airport express]] or an [[Airport express|Airport extreme]]

Find Your Gateway IP

2011-03-04T17:46:21Z

Uslackr:

It's important for you to know the internal IP address of your default gateway, which is normally your router's LAN IP address.

If you have ever had to access your router to configure it, you should know the address. It's what you type in your browser address bar to reach the configuration interface (example: http://192.168.1.1/) and, if not, you can find it with the following steps:

* <b><u>Windows</u>:</b><br /><br />
** Click <b>Start</b> > <b>All Programs</b> > <b>Accessories</b> > <b>Command Prompt</b>.<br /><br />
** When Command Prompt is open, type the following command: <code>ipconfig | findstr /i "Gateway"</code> (You can copy & paste it in the command prompt; just right-click anywhere in the command prompt window and select ''Paste''.)<br /><br />
** You should see something like this:<br /><code>C:\Documents and Settings\administrator>ipconfig | findstr /i "Gateway"<br /> Default Gateway . . . . . . . . . : 192.168.1.1</code><br /><br />
** In this example, your default gateway (router) IP address is <b>192.168.1.1</b>.
<br />

* <b><u>Linux</u>:</b><br /><br />
** You'll need to open a Terminal. Depending on your Linux distribution, it can be located in the menu items at the top, or at the bottom of your screen. In this example, we will use Fedora. Click <b>Applications</b> > <b>System Tools</b> > <b>Terminal</b>.<br /><br />
** When terminal is open, type the following command: <code>ip route | grep default</code><br /><br />
** The output of this should look something like the following:<br /><code>joe$ ip route | grep default<br />default via 192.168.1.1 dev eth0 proto static</code><br /><br />
** In this example, again, <b>192.168.1.1</b> is your default gateway (router) IP address.
<br /><br />

* <b><u>Mac OS X</u>:</b><br /><br />
** Open the Terminal application. Do do this, click <b>Finder</b> > <b>Applications</b> > <b>Utilities</b> > <b>Terminal.app</b>.<br /><br />
** When Terminal.app is open, type the following command: <code>netstat -nr | grep default</code><br /><br />
** This will output the following:<br /><code>joe$ netstat -nr | grep default<br />default 192.168.1.1 UGSc 50 46 en1</code><br /><br />
** In this example, again, <b>192.168.1.1</b> is your default gateway (router) IP address.

Find Your Gateway IP

2011-03-04T17:45:31Z

Uslackr:

It's important for you to know the internal IP address of your default gateway, which is normally your router's LAN IP address.

If you have ever had to access your router to configure it, you should know the address. It's what you type in your browser address bar to reach the configuration interface (example: http://192.168.1.1/) and, if not, you can find it with the following steps:

* <b><u>Windows</u>:</b><br /><br />
** Click <b>Start</b> > <b>All Programs</b> > <b>Accessories</b> > <b>Command Prompt</b>.<br /><br />
** When Command Prompt is open, type the following command: <code>ipconfig | findstr /i "Gateway"</code> (You can copy & paste it in the command prompt; just right-click anywhere in the command prompt window and select ''Paste''.)<br /><br />
** You should see something like this:<br /><code>C:\Documents and Settings\administrator>ipconfig | find "Gateway"<br /> Default Gateway . . . . . . . . . : 192.168.1.1</code><br /><br />
** In this example, your default gateway (router) IP address is <b>192.168.1.1</b>.
<br />

* <b><u>Linux</u>:</b><br /><br />
** You'll need to open a Terminal. Depending on your Linux distribution, it can be located in the menu items at the top, or at the bottom of your screen. In this example, we will use Fedora. Click <b>Applications</b> > <b>System Tools</b> > <b>Terminal</b>.<br /><br />
** When terminal is open, type the following command: <code>ip route | grep default</code><br /><br />
** The output of this should look something like the following:<br /><code>joe$ ip route | grep default<br />default via 192.168.1.1 dev eth0 proto static</code><br /><br />
** In this example, again, <b>192.168.1.1</b> is your default gateway (router) IP address.
<br /><br />

* <b><u>Mac OS X</u>:</b><br /><br />
** Open the Terminal application. Do do this, click <b>Finder</b> > <b>Applications</b> > <b>Utilities</b> > <b>Terminal.app</b>.<br /><br />
** When Terminal.app is open, type the following command: <code>netstat -nr | grep default</code><br /><br />
** This will output the following:<br /><code>joe$ netstat -nr | grep default<br />default 192.168.1.1 UGSc 50 46 en1</code><br /><br />
** In this example, again, <b>192.168.1.1</b> is your default gateway (router) IP address.

Vista Networking Issue

2011-03-04T12:29:48Z

Uslackr: Added reference to Windows 7

Some times, Vista and Windows 7 don't operate well with short URLs.

Here's a fix that worked for me (Vista/Windows 7 specific)

In Control Panel/network connections
# Right click your ethernet card (or similar) and select properties
# Select ''Internet Protocol v4'' and press the properties button
# Click the "Advanced" button
# Select the DNS tab
# Press the "Append these DNS suffixes (in order)" button
# Add your home server's domain name (eg. home.com)
# Press the required OKs, apply, close ...

All should work correctly now ... This should work now

Intro

2011-03-04T03:37:15Z

Uslackr:

The Amahi home server is a GNU/Linux-based, open-source network server, based on Fedora.

* It is meant to be headless, and running 24x7.
* Some people also use it as a desktop, while still serving the rest of the home network.
* It has the following features:
** Centralized storage server
** Bare metal backup server
** Application server
** Media streaming server
** Calendar server
** Wiki server
** Remote access server (for secure remote access to your files) (i.e. VPN).
** Print server
** ... and other types of installable services:
*** Bittorrent server
*** Slideshow generator
*** Recipes database
*** ... and many more in the online [http://www.amahi.org/apps Application Gallery]!

We think there are two "types" of users for our HDAs:

* The technical user (the one who installs and runs it)
* The real user of the home network: spouses, kids, etc.

We have a few features that are directed towards making life easier for one or the other, or both. However, ultimately, the real users are the non-technical users.

The features directed towards the technical user are meant to make his/her life easier when running a home network for the benefit of all the users.

Contribute

2011-03-04T03:30:34Z

Uslackr: removed link to users mailing list

There are a few ways to contribute and get involved and with Amahi!

Here is a list of ideas that the community has been suggesting:

* Contribute to this wiki! That is probably the most direct and quick way to contribute. Your experience helps others install and run their HDA!
* Share your experience in the area or running a server and answer questions in the [http://forums.amahi.org community forums]. If you are an experienced user, others will appreciate your efforts and this will make the project more usable and successful in the long run
* Talk about Amahi! Let people know what Amahi is about, help them install their HDA
* Promote Amahi, such as doing a presentation to your local LUG (Linux User Group), share your presentation with others!
* Blog or tweet about your experience with Amahi
* Make recommendations
* Do reviews or HOWTOs
* Help us create a polished "press kit" of sorts that we can give when magazines and website editors ask us about Amahi
* [[How to Create a new Theme|Create a theme or two]]
* Help us write a "manual" so that it's printable (in pdf and also [http://lulu.com in paper])
* Submit to other sites that may like it! :-)

... remember, it has to be fun and enjoyable for you, take as little time as possible, and help the community!

Aside from the above, there are two major ways to contribute in a more active role.

= Types of Contributor =

We have three types of contributor, from less involved to more involved:

* '''Editor:''' editing the apps "visual" part for English readability, HTML validation, logo/screenshot "shininess" and generally making beta apps look good
* '''Tester''': testing, rating and sending feedback on beta apps
* '''Packager''': packaging apps. no programming required

You can become any (or all) of these three roles by making yourself known to the community in the forums or in the IRC channel and asking to become a contributor!

= Becoming an Application Packager/Contributor =

* This is very easy. Whether you are an expert or you only know the basics of some application installation and configuration, this is a great way to contribute
* Read the [[Application Contributor]] Guide

= Other Ways to Contribute =

What if I want to contribute but don't have the time to package an app?

Well here's a solution: you can find some apps for our developement team to package and we can do that for you. All you have to do is supply a link to the apps homepage and we will jump right on it. [[New_App_Ideas]] to add you app ideas to the list. Any and all apps are ok.

= Contributing Code =

Follow this page to [[contribute code]].

Greyhole

2011-02-10T03:56:27Z

Uslackr:

[[Category:apps]]
<div style="border: 1px solid #A3B1BF; padding: .8em 1em; background-color: #E6F2FF; margin: 0px 1em;">
'''NEW:''' [http://code.google.com/p/greyhole/wiki/MigrateFromWHS Widows Home Server Drive Extender Migration Guide]

'''NEW:''' [[Greyhole troubleshooting]] guide
</div>

== What is Greyhole ==

A new feature in Amahi is [[Storage pooling]] using [http://greyhole.pommepause.com/ Greyhole]. Storage Pooling is a technology to pool disk drives and make them look as if they were all part of a single pool of disk space.

This feature is installed by default, but requires a few simple steps to begin utilizing the features.

You can add additional drives to your hda and prepare them for use in Greyhole by following [[Adding a second hard drive to your HDA|this tutorial]].

To add a drive to your Greyhole storage pool. First open your dashboard and navigate to the Shares tab. Then click on the Storage Pool sub-category. You will see a page similar to the one below.

== Important Warnings ==
<div style="color:darkred">You should '''never''' change or delete files in the shared directories (''/var/hda/files/*'' by default) directly on the HDA, using the terminal, or the Gnome file browser, for the shares for which you checked the ''Uses pool'' option in the Amahi dashboard. If you want to work with files on Greyhole shares on the HDA, you should [[Mount Shares Locally]].<br/>
You should be safe reading existing files directly, or adding new files directly, as long as don't care that your new files will only be moved into the storage pool during the next check, which runs automatically at midnight (or manually using ''greyhole --fsck''). Until then, your new files will be stored in your shared directories (normally ''/var/hda/files/share_name/'').

Also, touching anything inside the '''gh''' directories that Greyhole creates at the root of your partitions is a recipe for disaster.

We [[Greyhole not on root | strongly discourage you from using the root partition in a drive pool]].
</div><br/><br/>

== First things first ==

You need to go in the Settings tab, and enable '''Advanced Settings'''.<br/>
Without Advanced Settings enabled, you won't see the following page and options.

== For Storage Pool (Partitions) ==

[[File:Storage_Pool_1.png|600px|thumb|left]]

Select the drives you want available for your storage pool.

== Greyhole options ==

The next step is to select the share you want to replicate across the pool.

From the Shares tab, select the Shares sub-catagory. We chose the Pictures share for this tutorial.

[[File:Greyhole_Options_1.png|600px|thumb|left]]

Check the option for "Uses pool" and choose the number of drives to replicate this share. In this instance we have chosen to use all drives available to the greyhole pool.

Note: Greyhole is not a backup solution. If a file is removed, all copies are removed.

== Greyhole advanced options ==

You can further configure Greyhole by manually editing the following file:<br/>
'''/var/hda/platform/html/config/greyhole.yml'''

To see what options are available, and what they do, refer to the [http://greyhole.googlecode.com/svn/trunk/greyhole.example.conf sample greyhole.conf] provided with Greyhole.

greyhole.yml is in in YAML format. Most of it should be easy enough to modify. The only exception would be the sticky_files (and optional sticky_into) options.<br/>
Here's an example of how those should appear:

To specify the following to Greyhole in greyhole.conf:

sticky_files = Music/
sticky_files = Videos/Movies/
stick_into = /mnt/hdd1/gh
stick_into = /mnt/hdd5/gh
sticky_files = Backups/CrashPlan/
stick_into = /mnt/hdd0/gh

one should specify this in the greyhole.yml file, where '''precise indentation matters''':

sticky_files:
- - Music/
- - Videos/Movies/
- - /mnt/hdd1/gh
- /mnt/hdd5/gh
- - Backups/CrashPlan/
- - /mnt/hdd0/gh

For your changes to be effective, you'll need to force Amahi to regenerate the greyhole.conf file. You can do so by editing a share, clicking it's path, and just clicking the Save button without actually changing the path.

== Copying your data into Greyhole shares the first time ==

When you start using Greyhole, you might want to copy or move all your exiting files into your new shares that use the storage pool.

Note: This is not necessary if your files are already in Amahi shares. If they are there, and you enable the ''Uses pool'' option in the Amahi dashboard, the files will start getting moved around into the drives in your storage pool during the night (starting at midnight), when the nightly storage pool check starts.<br/>
The instructions below are for users who have more data to copy into the Greyhole shares than their currently free space in the /var/hda/files/ folder.

One way to do that is to mount the shares that use the Greyhole storage pool, either on the HDA itself, or on a client computer on your local network, and copy your data from their existing location into the mounted shares.
This can be time consuming, but it is the safest way to use Greyhole.

Another way to move your files from their current location into the storage pool is to share their current location using an Amahi share that ''Uses pool'', then let Greyhole nightly check move the files from there into the pool.

Here's a more detailed walkthrough for this method:

# Setup the Greyhole Storage Pool in the Amahi dashboard, Shares > Storage Pool page.
# Go in the Shares > Shares page. In there, make sure you have an existing share for each share you have data for. Create new ones if you need, remove the ones you don't need.
# Edit the ''path'' of each of those shares, and enter the current location of your existing data. For example, the Movies share could have a path = ''/media/External Drive/Movies''
# Enable the ''Uses pool'' option for each of your shares, and select the number of extra copies you'd like, if any.
# Now, you either need to wait for Greyhole'S nightly check to start, or you can start it manually from a terminal, as root, using this command: greyhole --fsck
# Monitor /var/log/greyhole.log to see when the ''fsck'' operation is done.
# Once ''fsck'' is done, your data has now been moved into the Greyhole storage pool (in the drives you selected in Shares > Storage Pool). All that should be left in the previous location of your data (''/media/External Drive/Movies'' from the previous example) should be symbolic links pointing to the new file copies. If the previous location is just empty directories (no symlinks), do not panic. This is normal if your previous location is an NTFS or FAT partition (drive).
# Move all those directories / symlinks from there into the correct folders in /var/hda/files/share_name
# Back in the Amahi dashboard, edit the path of the shares once again, and put back ''/var/hda/files/share_name'' (i.e. the folders where you moved the symbolic links).
# If you used an NTFS or FAT partition for the previous location, you'll need another fsck to create the symlinks where they should be. Either wait for midnight, or launch it manually, from a command line, as root: ''greyhole --fsck''

You're done. All your existing data is now stored in the various drives included in your storage pool, and are accessible via the Samba shares you have defined in the Amahi dashboard.

== Adding a new drive to your HDA and storage pool ==
This wiki page discusses how to add a new drive to your HDA and to your greyhole storage pool
[[Adding_a_second_hard_drive_to_your_HDA]]

== /media ==
Including any drive mounted as /media/Something in your storage pool is usually a bad idea.<br/>
Those mounts are created by the ''gnome-automounter'', which requires you to be logged in into X (Gnome) to become available.<br/>
This will create issues with Greyhole, which expects drives to always be available, and will take action when some of them are missing.

Follow this guide to [[Adding a second hard drive to your HDA|permanently mount your drives]], before you include them in your storage pool.

== Monitoring Greyhole ==
Sometimes you might want to monitor what Greyhole is doing, for example when writing data to your greyhole shares for the first time. Here are a few commands you can type in a terminal to follow along.

'''Scrolling view of total Greyhole operations queue:'''
while [ 1 == 1 ]; do greyhole --view-queue | grep Total; sleep 60; done

'''Scrolling log of what files Greyhole is working on right now:'''
tail -f /var/log/greyhole.log

== Convert Greyhole from SQLite to MySQL ==
Greyhole is at the time of writing using SQLite as the default database for queueing up tasks on Amahi. This is unqie to Amahi as Greyhole was originally designed to use MySQL for this task.

There are some major performance benefits to using MySQL over SQLite when writing large amounts of files. Switching can be especially useful when moving data to greyhole shares for the first time. For now there is a script you can run if you want to switch over. This script has been tested to be safe while greyhole is working but should be used with discresion.

''To Convert to MySQL, run as root:''

/usr/share/greyhole/db_migration-sqlite2mysql.sh

To see what DB engine is Greyhole using, do this:

grep db_engine /etc/greyhole.conf

== Disable Greyhole ==
For those who do not use Greyhole, you can disable it. This is based on the fact you never have used it by enabling 'Uses pool' on any share. Recommend using extreme caution as this could have unpredictable results.

Perform the following steps as user '''root''':

chkconfig greyhole off
rm /etc/monit.d/greyhole.conf
service monit restart
service greyhole stop

'''DO NOT''' attempt to remove the Greyhole package as it is a dependency of the HDA software. Doing so will break your HDA.

= Testing and Reliability =

Check out the [[Greyhole grinder]] to help make Greyhole rock solid.

= Greyhole Troubleshooting =

[[Greyhole troubleshooting]] guide

Greyhole

2011-02-10T03:48:42Z

Uslackr: Link to adding a 2nd drive

[[Category:apps]]
<div style="border: 1px solid #A3B1BF; padding: .8em 1em; background-color: #E6F2FF; margin: 0px 1em;">
'''NEW:''' [http://code.google.com/p/greyhole/wiki/MigrateFromWHS Widows Home Server Drive Extender Migration Guide]

'''NEW:''' [[Greyhole troubleshooting]] guide
</div>

== What is Greyhole ==

A new feature in Amahi is [[Storage pooling]] using [http://greyhole.pommepause.com/ Greyhole]. Storage Pooling is a technology to pool disk drives and make them look as if they were all part of a single pool of disk space.

This feature is installed by default, but requires a few simple steps to begin utilizing the features.

You can add additional drives to your hda and prepare them for use in Greyhole by following [[Adding a second hard drive to your HDA|this tutorial]].

To add a drive to your Greyhole storage pool. First open your dashboard and navigate to the Shares tab. Then click on the Storage Pool sub-category. You will see a page similar to the one below.

== Important Warnings ==
<div style="color:darkred">You should '''never''' change or delete files in the shared directories (''/var/hda/files/*'' by default) directly on the HDA, using the terminal, or the Gnome file browser, for the shares for which you checked the ''Uses pool'' option in the Amahi dashboard. If you want to work with files on Greyhole shares on the HDA, you should [[Mount Shares Locally]].<br/>
You should be safe reading existing files directly, or adding new files directly, as long as don't care that your new files will only be moved into the storage pool during the next check, which runs automatically at midnight (or manually using ''greyhole --fsck''). Until then, your new files will be stored in your shared directories (normally ''/var/hda/files/share_name/'').

Also, touching anything inside the '''gh''' directories that Greyhole creates at the root of your partitions is a recipe for disaster.

We [[Greyhole not on root | strongly discourage you from using the root partition in a drive pool]].
</div><br/><br/>

== First things first ==

You need to go in the Settings tab, and enable '''Advanced Settings'''.<br/>
Without Advanced Settings enabled, you won't see the following page and options.

== For Storage Pool (Partitions) ==

[[File:Storage_Pool_1.png|600px|thumb|left]]

Select the drives you want available for your storage pool.

== Greyhole options ==

The next step is to select the share you want to replicate across the pool.

From the Shares tab, select the Shares sub-catagory. We chose the Pictures share for this tutorial.

[[File:Greyhole_Options_1.png|600px|thumb|left]]

Check the option for "Uses pool" and choose the number of drives to replicate this share. In this instance we have chosen to use all drives available to the greyhole pool.

Note: Greyhole is not a backup solution. If a file is removed, all copies are removed.

== Greyhole advanced options ==

You can further configure Greyhole by manually editing the following file:<br/>
'''/var/hda/platform/html/config/greyhole.yml'''

To see what options are available, and what they do, refer to the [http://greyhole.googlecode.com/svn/trunk/greyhole.example.conf sample greyhole.conf] provided with Greyhole.

greyhole.yml is in in YAML format. Most of it should be easy enough to modify. The only exception would be the sticky_files (and optional sticky_into) options.<br/>
Here's an example of how those should appear:

To specify the following to Greyhole in greyhole.conf:

sticky_files = Music/
sticky_files = Videos/Movies/
stick_into = /mnt/hdd1/gh
stick_into = /mnt/hdd5/gh
sticky_files = Backups/CrashPlan/
stick_into = /mnt/hdd0/gh

one should specify this in the greyhole.yml file, where '''precise indentation matters''':

sticky_files:
- - Music/
- - Videos/Movies/
- - /mnt/hdd1/gh
- /mnt/hdd5/gh
- - Backups/CrashPlan/
- - /mnt/hdd0/gh

For your changes to be effective, you'll need to force Amahi to regenerate the greyhole.conf file. You can do so by editing a share, clicking it's path, and just clicking the Save button without actually changing the path.

== Copying your data into Greyhole shares the first time ==

When you start using Greyhole, you might want to copy or move all your exiting files into your new shares that use the storage pool.

Note: This is not necessary if your files are already in Amahi shares. If they are there, and you enable the ''Uses pool'' option in the Amahi dashboard, the files will start getting moved around into the drives in your storage pool during the night (starting at midnight), when the nightly storage pool check starts.<br/>
The instructions below are for users who have more data to copy into the Greyhole shares than their currently free space in the /var/hda/files/ folder.

One way to do that is to mount the shares that use the Greyhole storage pool, either on the HDA itself, or on a client computer on your local network, and copy your data from their existing location into the mounted shares.
This can be time consuming, but it is the safest way to use Greyhole.

Another way to move your files from their current location into the storage pool is to share their current location using an Amahi share that ''Uses pool'', then let Greyhole nightly check move the files from there into the pool.

Here's a more detailed walkthrough for this method:

# Setup the Greyhole Storage Pool in the Amahi dashboard, Shares > Storage Pool page.
# Go in the Shares > Shares page. In there, make sure you have an existing share for each share you have data for. Create new ones if you need, remove the ones you don't need.
# Edit the ''path'' of each of those shares, and enter the current location of your existing data. For example, the Movies share could have a path = ''/media/External Drive/Movies''
# Enable the ''Uses pool'' option for each of your shares, and select the number of extra copies you'd like, if any.
# Now, you either need to wait for Greyhole'S nightly check to start, or you can start it manually from a terminal, as root, using this command: greyhole --fsck
# Monitor /var/log/greyhole.log to see when the ''fsck'' operation is done.
# Once ''fsck'' is done, your data has now been moved into the Greyhole storage pool (in the drives you selected in Shares > Storage Pool). All that should be left in the previous location of your data (''/media/External Drive/Movies'' from the previous example) should be symbolic links pointing to the new file copies. If the previous location is just empty directories (no symlinks), do not panic. This is normal if your previous location is an NTFS or FAT partition (drive).
# Move all those directories / symlinks from there into the correct folders in /var/hda/files/share_name
# Back in the Amahi dashboard, edit the path of the shares once again, and put back ''/var/hda/files/share_name'' (i.e. the folders where you moved the symbolic links).
# If you used an NTFS or FAT partition for the previous location, you'll need another fsck to create the symlinks where they should be. Either wait for midnight, or launch it manually, from a command line, as root: ''greyhole --fsck''

You're done. All your existing data is now stored in the various drives included in your storage pool, and are accessible via the Samba shares you have defined in the Amahi dashboard.

== Adding a new drive to your HDA and storage pool ==

[[Adding_a_second_hard_drive_to_your_HDA]]

== /media ==
Including any drive mounted as /media/Something in your storage pool is usually a bad idea.<br/>
Those mounts are created by the ''gnome-automounter'', which requires you to be logged in into X (Gnome) to become available.<br/>
This will create issues with Greyhole, which expects drives to always be available, and will take action when some of them are missing.

Follow this guide to [[Adding a second hard drive to your HDA|permanently mount your drives]], before you include them in your storage pool.

== Monitoring Greyhole ==
Sometimes you might want to monitor what Greyhole is doing, for example when writing data to your greyhole shares for the first time. Here are a few commands you can type in a terminal to follow along.

'''Scrolling view of total Greyhole operations queue:'''
while [ 1 == 1 ]; do greyhole --view-queue | grep Total; sleep 60; done

'''Scrolling log of what files Greyhole is working on right now:'''
tail -f /var/log/greyhole.log

== Convert Greyhole from SQLite to MySQL ==
Greyhole is at the time of writing using SQLite as the default database for queueing up tasks on Amahi. This is unqie to Amahi as Greyhole was originally designed to use MySQL for this task.

There are some major performance benefits to using MySQL over SQLite when writing large amounts of files. Switching can be especially useful when moving data to greyhole shares for the first time. For now there is a script you can run if you want to switch over. This script has been tested to be safe while greyhole is working but should be used with discresion.

''To Convert to MySQL, run as root:''

/usr/share/greyhole/db_migration-sqlite2mysql.sh

To see what DB engine is Greyhole using, do this:

grep db_engine /etc/greyhole.conf

== Disable Greyhole ==
For those who do not use Greyhole, you can disable it. This is based on the fact you never have used it by enabling 'Uses pool' on any share. Recommend using extreme caution as this could have unpredictable results.

Perform the following steps as user '''root''':

chkconfig greyhole off
rm /etc/monit.d/greyhole.conf
service monit restart
service greyhole stop

'''DO NOT''' attempt to remove the Greyhole package as it is a dependency of the HDA software. Doing so will break your HDA.

= Testing and Reliability =

Check out the [[Greyhole grinder]] to help make Greyhole rock solid.

= Greyhole Troubleshooting =

[[Greyhole troubleshooting]] guide

Talk:VNC

2010-12-03T01:33:08Z

Uslackr: Created page with "This page presents two methods for enabling VNC on a headless server. Does anyone know why I might pick one method over the other?"

This page presents two methods for enabling VNC on a headless server. Does anyone know why I might pick one method over the other?

User:Uslackr

2010-12-02T12:35:38Z

Uslackr:

Real name: Greg Martin

Amahi user since Fall 2010
Server specs: Dell Optiplex GX620; 2Gb RAM, 16oGB root volume; 2x250GB data disks

User:Uslackr

2010-12-02T12:35:03Z

Uslackr: Created page with "Amahi user since Fall 2010 Server specs: Dell Optiplex GX620; 2Gb RAM, 16oGB root volume; 2x250GB data disks"

Amahi user since Fall 2010
Server specs: Dell Optiplex GX620; 2Gb RAM, 16oGB root volume; 2x250GB data disks