Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
I'm doing something similar and although I'm pretty new at this I'm gathering the best setup would be to have heartbeat running over both eth0 and eth1 as well as providing a serial connection. That way if the drbd link goes down, the peer-outdater program can use one of the other heartbeat paths/links to outdate the secondary and keep heartbeat from using it. On Tue, 2007-12-18 at 10:03 -0500, Greg Haase wrote: > I'm playing around with a drbd + mysql setup, and I had some questions > about how the servers should be connected. > > I currently have two virtual machines running, each with two ethernet > ports. On each machine eth0 is Bridged - so it's connected to our > development subnet. The eth1 ports are both on a private network within > VM (VMnet5). I think that's the best way I can simulate a cross-connected > cable between servers on eth1. I have both heartbeat bcast and drbd > working over eth1. > > I've had this working for a while and I've been testing various fail-over > situations. > > The one thing I've noticed is that pretty much all hell breaks loose if I > take down eth1 on either of the servers. While I would admit in a real > situation it is unlikely that anything should happen here, it can be a > point of failure. > > What are the best ways of address this? Is my setup lacking? > > _______________________________________________ > drbd-user mailing list > drbd-user at lists.linbit.com > http://lists.linbit.com/mailman/listinfo/drbd-user