HA topology and replication techniques

I have been doing a lot of reading on Replication and High Availability, but still cannot determine which pathway I should choose. I would appreciate any comments you may have.    

I think I've narrowed it down to two approaches:  

1. MySQL HA Cluster with Heartbeat (Master/Master)
2. MySQL Replication with DRBD

My primary goal

High availability  

Other goals

                Would be nice to scale to a load balancing setup, if

Storage & Hardware

                Each server has its own hardware and storage unit

100G of database storage (current single server has 35-40G of data)  

Application requirements

                We use MyISAM tables and LAMP style web applications.

 

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related lists.mysql.com Links announce benchmarks bugs certification cluster commits dotnet gui-tools internals java maxdb myodbc mysql mysqldoc packagers perl plusplus replication win32 Request more information about Pantek

Other information

                We will have a 3rd server at a remote location (out of

Main concerns

1. I can replicate the data to the other nodes, but I want to ensure that the web applications can write to those nodes and the it replicate to the "master" when it comes back on line.
2. I understand that some data may be lost during the actual failover. Data loss is not a primary concern, but database corruption is.

Any thoughts on which method I should choose? How to professional web hosting companies do it? I'm really tempted to just decided with a coin toss!  

-Todd                                                   Received on Tue Jul 3 16:46:00 2007