<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Netvouz / falko / tag / ha</title>
<link>http://netvouz.com/falko/tag/ha?feed=rss</link>
<description>falko&#39;s bookmarks tagged &quot;ha&quot; on Netvouz</description>
<item><title>High-Availability Storage With GlusterFS On Debian LennyAutomatic File Replication - Across Two Storage Servers</title>
<link>http://www.howtoforge.com/high-availability-storage-with-glusterfs-on-debian-lenny-automatic-file-replication-across-two-storage-servers</link>
<description>This tutorial shows how to set up a high-availability storage with two storage servers (Debian Lenny) that use GlusterFS. Each storage server will be a mirror of the other storage server, and files will be replicated automatically across both storage servers. The client system (Debian Lenny as well) will be able to access the storage as if it was a local filesystem. GlusterFS is a clustered file-system capable of scaling to several peta-bytes. It aggregates various storage bricks over Infiniband RDMA or TCP/IP interconnect into one large parallel network file system. Storage bricks can be made of any commodity hardware such as x86-64 servers with SATA-II RAID and Infiniband HBA.</description>
<category domain="http://netvouz.com/falko?category=6101149612142001527"></category>
<author>falko</author>
<pubDate>Tue, 09 Jun 2009 11:59:09 GMT</pubDate>
</item><item><title>High-Availability Storage With GlusterFS On Fedora 12 - Automatic File Replication (Mirror) Across Two Storage Servers</title>
<link>http://www.howtoforge.com/high-availability-storage-with-glusterfs-on-fedora-12-automatic-file-replication-mirror-across-two-storage-servers</link>
<description>This tutorial shows how to set up a high-availability storage with two storage servers (Fedora 12) that use GlusterFS. Each storage server will be a mirror of the other storage server, and files will be replicated automatically across both storage servers. The client system (Fedora 12 as well) will be able to access the storage as if it was a local filesystem. GlusterFS is a clustered file-system capable of scaling to several peta-bytes. It aggregates various storage bricks over Infiniband RDMA or TCP/IP interconnect into one large parallel network file system. Storage bricks can be made of any commodity hardware such as x86_64 servers with SATA-II RAID and Infiniband HBA.</description>
<category domain="http://netvouz.com/falko?category=6101149612142001527"></category>
<author>falko</author>
<pubDate>Tue, 02 Mar 2010 13:03:35 GMT</pubDate>
</item><item><title>How To Set Up A Load-Balanced MySQL Cluster With MySQL 5.1</title>
<link>http://www.howtoforge.com/setting-up-a-loadbalanced-mysql-cluster-with-mysql5.1</link>
<description>This tutorial shows how to configure a MySQL 5.1 cluster with five nodes: 1 x management, 2 x storage nodes and 2 x balancer nodes. This cluster is load-balanced by an Ultra Monkey package which provides heartbeat (for checking if the other node is still alive) and ldirectord (to split up the requests to the nodes of the MySQL cluster).</description>
<category domain="http://netvouz.com/falko?category=6101149612142001527"></category>
<author>falko</author>
<pubDate>Tue, 17 Jun 2008 09:52:40 GMT</pubDate>
</item><item><title>How To Set Up A Loadbalanced High-Availability Apache Cluster Based On Ubuntu 8.04 LTS</title>
<link>http://www.howtoforge.com/set-up-a-loadbalanced-ha-apache-cluster-ubuntu8.04</link>
<description>This tutorial shows how to set up a two-node Apache web server cluster that provides high-availability. In front of the Apache cluster we create a load balancer that splits up incoming requests between the two Apache nodes. Because we do not want the load balancer to become another &quot;Single Point Of Failure&quot;, we must provide high-availability for the load balancer, too. Therefore our load balancer will in fact consist out of two load balancer nodes that monitor each other using heartbeat, and if one load balancer fails, the other takes over silently.</description>
<category domain="http://netvouz.com/falko?category=6101149612142001527"></category>
<author>falko</author>
<pubDate>Thu, 12 Jun 2008 11:23:37 GMT</pubDate>
</item><item><title>Installing and Configuring Openfiler with DRBD and Heartbeat</title>
<link>http://www.howtoforge.com/installing-and-configuring-openfiler-with-drbd-and-heartbeat</link>
<description>Openfiler is a high performance operating system tailored for use as a SAN/NAS appliance. This configuration will enable two Openfiler appliances to work in an active/passive high availability scenario.</description>
<category domain="http://netvouz.com/falko?category=6101149612142001527"></category>
<author>falko</author>
<pubDate>Sun, 26 Oct 2008 13:31:26 GMT</pubDate>
</item><item><title>Setting Up A High-Availability Load Balancer (With Failover and Session Support) With HAProxy/Heartbeat On Debian Lenny</title>
<link>http://www.howtoforge.com/setting-up-a-high-availability-load-balancer-with-haproxy-heartbeat-on-debian-lenny</link>
<description>This article explains how to set up a two-node load balancer in an active/passive configuration with HAProxy and heartbeat on Debian Lenny. The load balancer sits between the user and two (or more) backend Apache web servers that hold the same content. Not only does the load balancer distribute the requests to the two backend Apache servers, it also checks the health of the backend servers. If one of them is down, all requests will automatically be redirected to the remaining backend server. In addition to that, the two load balancer nodes monitor each other using heartbeat, and if the master fails, the slave becomes the master, which means the users will not notice any disruption of the service. HAProxy is session-aware, which means you can use it with any</description>
<category domain="http://netvouz.com/falko?category=6101149612142001527"></category>
<author>falko</author>
<pubDate>Tue, 14 Jul 2009 10:00:49 GMT</pubDate>
</item><item><title>Setting Up A High-Availability Load Balancer (With Failover and Session Support) With HAProxy/Heartbeat On Fedora 8</title>
<link>http://www.howtoforge.com/high-availability-load-balancer-haproxy-heartbeat-fedora8</link>
<description>This document describes how to set up a two-node load balancer in an active/passive configuration with HAProxy and heartbeat on Fedora 8. The load balancer acts between the user and two (or more) Apache web servers that hold the same content. The load balancer passes the requests to the web servers and it also checks their health. If one of them is down, all requests will automatically be redirected to the remaining web server(s). In addition to that, the two load balancer nodes monitor each other using heartbeat. If the master fails, the slave becomes the master - users will not notice any disruption of the service. HAProxy is session-aware - you can use it with any web application that makes use of sessions like forums, shopping carts, etc.</description>
<category domain="http://netvouz.com/falko?category=6101149612142001527"></category>
<author>falko</author>
<pubDate>Sun, 02 Mar 2008 12:46:21 GMT</pubDate>
</item><item><title>Setting Up A High-Availability Load Balancer (With Failover and Session Support) With Perlbal/Heartbeat On Debian Etch</title>
<link>http://www.howtoforge.com/setting-up-a-high-availability-load-balancer-with-perlbal-heartbeat-on-debian-etch</link>
<description>This article explains how to set up a two-node load balancer in an active/passive configuration with Perlbal and heartbeat on Debian Etch. The load balancer sits between the user and two (or more) backend Apache web servers that hold the same content. Not only does the load balancer distribute the requests to the two backend Apache servers, it also checks the health of the backend servers. If one of them is down, all requests will automatically be redirected to the remaining backend server. In addition to that, the two load balancer nodes monitor each other using heartbeat, and if the master fails, the slave becomes the master, which means the users will not notice any disruption of the service. Perlbal is session-aware, which means you can use it with any </description>
<category domain="http://netvouz.com/falko?category=6101149612142001527"></category>
<author>falko</author>
<pubDate>Tue, 13 Jan 2009 12:23:37 GMT</pubDate>
</item><item><title>Setting Up A High-Availability Load Balancer With HAProxy/Wackamole/Spread On Debian Etch</title>
<link>http://www.howtoforge.com/setting-up-a-high-availability-load-balancer-with-haproxy-wackamole-spread-on-debian-etch</link>
<description>This article explains how to set up a two-node load balancer in an active/passive configuration with HAProxy, Wackamole, and Spread on Debian Etch. The load balancer sits between the user and two (or more) backend Apache web servers that hold the same content. Not only does the load balancer distribute the requests to the two backend Apache servers, it also checks the health of the backend servers. If one of them is down, all requests will automatically be redirected to the remaining backend server. In addition to that, the two load balancer nodes monitor each other using Wackamole and Spread, and if the master fails, the slave becomes the master, which means the users will not notice any disruption of the service. HAProxy is session-aware, which means you </description>
<category domain="http://netvouz.com/falko?category=6101149612142001527"></category>
<author>falko</author>
<pubDate>Tue, 06 Jan 2009 12:47:12 GMT</pubDate>
</item><item><title>Setting Up Network RAID1 With DRBD On Debian Squeeze</title>
<link>http://www.howtoforge.com/setting-up-network-raid1-with-drbd-on-debian-squeeze</link>
<description>This tutorial shows how to set up network RAID1 with the help of DRBD on two Debian Squeeze systems. DRBD stands for Distributed Replicated Block Device and allows you to mirror block devices over a network. This is useful for high-availability setups (like a HA NFS server) because if one node fails, all data is still available from the other node.</description>
<category domain="http://netvouz.com/falko?category=6101149612142001527"></category>
<author>falko</author>
<pubDate>Tue, 23 Aug 2011 07:44:46 GMT</pubDate>
</item></channel></rss>