Hi, On Fri, Dec 07, 2007 at 03:55:44PM -0000, Rafe Slattery wrote: > Because the server pairs are going to end up in different buildings. > Also because of customer enforced fire walling requirements that's not > possible. > Which leads me to another thing I'm going to be playing with. > Quorum. > > With 4 nodes, which are going to be split across different buildings I > need to consider a quorum server. > Is it possible to have one of the heartbeat servers operate also as a > quorum server? > I don't think I can get any extra hardware so I would like one of the 4 > to double as a quorum box. Is that plan a flyer... ?
Don't think so. It would be good to have quorumd running somewhere outside of the two sites. That, however, won't solve the problem of the heartbeat connection failing between the two sites. See http://www.linux-ha.org/SplitSite Thanks, Dejan > Thanks > > Rafe > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Dejan > Muhamedagic > Sent: 06 December 2007 12:31 > To: General Linux-HA mailing list > Subject: Re: [Linux-HA] Setup Q > > Hi, > > On Thu, Dec 06, 2007 at 12:49:17AM -0000, Rafe Slattery wrote: > > thanks for the suggestion... > > It helped ... a bit... but I'm still not quite there... > > Can I get some clarificaton on what location constraints I should use. > > I want an active/passive combo. 1 web to be running web services , 1 > passive. 1 db to run db services, 1 passive. > > Why don't you go with a three node cluster then? You can have one > standby node which could run either db or web in case one of the active > nodes fails. Save a bit on hw, power, maintenance, etc. > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
