Hi,

I'm running a 2-node HA cluster - Xen, Pacemaker, Corosync, DRBD - 
fairly traditional.

But... I'm getting ready to add a new node or two, and I'm starting to 
wonder how one might approach 3-node failover - replicating data across 
three nodes, with two levels of failover for a VM -- which should also 
make it a lot easier to replace hardware and upgrade software without 
sacrificing downtime.

It sort of looks like DRBD stacking can replicate data across three 
nodes, but it looks a little baroque, and it's not at all clear how to 
set up a 3-node failover strategy.  It doesn't look like the various 
configurations provide for the same flexibility in specifying spare 
nodes, akin to the way that md raid configuration gives flexibility in 
the number of active and spare drives in an array.

Any suggestions, pointers, or comments on how to approach this?  Should 
I be looking at some kind of cluster file system instead of DRBD?

Thanks very much,

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In<fnord>  practice, there is.   .... Yogi Berra


_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to