Use DRBD to Provide Rock-Solid MySQL Redundancy

Mar 16, 2009, 22:16 (0 Talkback[s])
(Other stories by Charlie Schluting)

"Before we start, let’s quickly cover the architectural configuration of your two servers, and talk about performance. Firstly, you are going to use two “commodity” servers, which is not to imply slow or generic. You want to dedicate your fastest servers, because this type of configuration comes at a cost; it is doing much more than you may think a primary/secondary failover setup would. Therefore, I/O capabilities are probably the most important aspect. As Florian Haas of LINBIT (the creators of DRBD) points out, you can run two separate instances at once to avoid under-utilizing your secondary server. Each node will be the primary for its main instance, and a secondary for the other node.

"Second, conceptually, you will configure MySQL to live on a DRBD replicated device. Heartbeat will monitor MySQL availability, and in the event a failover is necessary, the secondary server will mount the file system, steal the virtual IP, and start up MySQL."

Complete Story

Related Stories:

• High Availability for MySQL: Considering the Options(Mar 10, 2009)
• Using ATA Over Ethernet (AoE) On Debian Lenny (Initiator And Target)(Mar 16, 2009)
• Xen Cluster Management With Ganeti On Debian Lenny(Mar 06, 2009)
• Three Node Replication Using DRBD 8.3(Feb 27, 2009)
• Installing and Configuring Openfiler with DRBD and Heartbeat(Oct 28, 2008)
• Setting up DRBD in an Open Source SAN: Open Source SANs, part 2(Sep 06, 2008)
• Setting up DRBD in an Open Source SAN(Jul 24, 2008)