From owner-freebsd-questions Sun Feb 10 21:15:53 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mg.hk5.outblaze.com (202-77-181-23.outblaze.com [202.77.181.23]) by hub.freebsd.org (Postfix) with ESMTP id 939D837B419 for ; Sun, 10 Feb 2002 21:15:50 -0800 (PST) Received: from ws2.hk5.outblaze.com (202-123-209-135.outblaze.com [202.123.209.135]) by mg.hk5.outblaze.com (8.11.2/8.11.2) with SMTP id g1B5Fm412198 for ; Mon, 11 Feb 2002 05:15:48 GMT Received: (qmail 29946 invoked by uid 1001); 11 Feb 2002 05:15:48 -0000 Message-ID: <20020211051548.29945.qmail@graffiti.net> Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Mailer: MIME-tools 4.104 (Entity 4.117) Received: from [66.51.217.108] by ws2.hk5.outblaze.com with http for derekbarrett@graffiti.net; Mon, 11 Feb 2002 13:15:48 +0800 From: "Derek Barrett" To: freebsd-questions@freebsd.org Date: Mon, 11 Feb 2002 13:15:48 +0800 Subject: Failover, clustering, and High Availability revisited X-Originating-Ip: 66.51.217.108 X-Originating-Server: ws2.hk5.outblaze.com Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello Everybody, Well since we are using FreeBSD, our servers have the reputation of being, "High Availability" servers already. However, I am researching how to implement a comprehensive failover system on a FreeBSD/Apache/MySQL server. It has been challenging so far. Most of the solutions I have come across so far are either expensive hardware or software packages. Failover and clustering seem to be in their infancy in the BSD environment. Another benefit that I see of having a high availability configuration with FreeBSD, is flexibility, especially when it comes to maintenance. It would be nice to have a backup server that could kick in when say, we needed to take the server down to add a memory module in it. Or when running a software upgrade. Or, when we run a nightly backup, if the backup is replicating the master server, we could just shut down the backup database and run the backup off of it, leaving the primary database running 24/7. My short term goal is: Have 2 FreeBSD Apache/MySQL servers in a master/slave configuration. The backup should only kick in when the master fails. My long term goal is: Having our FreeBSD servers in a single master/multiple slave cluster configuration. In this configuration, all servers will take connections, enabling not only robust fault tolerance, but load balancing as well. I guess my question is, what all is everybody using for a comprehensive FreeBSD High Availability solution? Thanks, Derek My research so far has come up with the following tools. (Note that MySQL has replication built in): Failover: http://failover.othello.ch/ Heartbeat: http://www.samag.com/documents/s=1146/sam0109c/0109c.htm Pen: http://siag.nu/pen/ Balance: http://sourceforge.net/projects/balance/ -- _______________________________________________ Get your free email from http://www.graffiti.net Powered by Outblaze To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message