Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Someone previously asked: >Hi there! > >i'm running heartbeat with drbd mirroring. >the heartbeats are being sent by eth1 and ttys0. the drbd devices are >mirrored over eht1, too. >if eth1 breaks, no more data is being mirrored, but the heartbeats still get >over ttys0. is that a problem? >imagine, the server crashes after eth1 was broken. the slave overtakes the >services, but the data isn't up-to-date, because mirroring doesn't work >anymore. >so ive lost some important data. > >is there a possibility to prevent this problem? >i thought about automatically change the mirror device to eth0, when eth1 >fails. > I'm now in the same situation. Hearbeat is on eth0 and I can't go beyond that. Is there any plan to allow multiple independent pathways to synchronize? I don't see anything on the road map page, http://svn.drbd.org/drbd/trunk/ROADMAP. Simple NIC bonding won't help because the NICs in my case are on wholly different networks. -- Maurice Volaski, mvolaski at aecom.yu.edu Computing Support, Rose F. Kennedy Center Albert Einstein College of Medicine of Yeshiva University