Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Felix Frank-2 wrote: > > On 01/15/2011 06:24 PM, Pit Bull wrote: >> >> Hi all. >> >> Im using DRBD + Heartbeat on three server's >> >> 1 server + 2 server have device drbd1 >> 3 server have stacked on drbd1 device drbd10 >> >> drbd10 used by Hearbeat for sharing it on virtual ip >> >> config - > >> http://www.howtoforge.com/drbd-8.3-third-node-replication-with-debian-etch >> >> if i down 1 server him trying to send all resources to 3 server, >> but 3 server have some error and can't recive resources. >> >> so my QUESTION is: >> 3 server in that configuration can by sandalone and have all resources of >> cluster? > > Yes. Usually however, you'd want Server2 to become the new peer of > Server3. It is then up to the CRM to decide wether Server2 or Server3 > should be your primary. > > If both Server1 and Server2 fail, there is no reason why DRBD wouldn't > run StandAlone on Server3. > > Regards, > Felix > _______________________________________________ > drbd-user mailing list > drbd-user at lists.linbit.com > http://lists.linbit.com/mailman/listinfo/drbd-user > > Wait a minute, how Server 3 can by Standalone, and have resources of cluster (shared ip providet by hearbeat) if him not writed in Heartbeat conf. " vi /etc/ha.d/ha.cf debugfile /var/log/ha-debug logfile /var/log/ha-log logfacility local0 keepalive 1 deadtime 10 warntime 5 initdead 60 udpport 694 ucast eth0 192.168.1.10 ucast eth0 192.168.1.20 auto_failback off node alpha node bravo" (!!! no line "node foxtrot" in this file) im based on this http://www.howtoforge.com/drbd-8.3-third-node-replication-with-debian-etch -- View this message in context: http://old.nabble.com/DRBD-%2B-Heartbeat-three-servers-tp30676124p30702931.html Sent from the DRBD - User mailing list archive at Nabble.com.