Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 27 Jul 2001 09:58:04 -0400
From:      "Drew J. Weaver" <drew.weaver@thenap.com>
To:        'Sascha Lucky Luck' <bofh@online.ie>, Andrew Reid <andrew.reid@plug.cx>
Cc:        freebsd-isp@FreeBSD.ORG
Subject:   RE: FreeBSD Mail Toaster CLUSTER
Message-ID:  <B1A7D9973EBED3119ADD009027DC86492B0CFF@mailman.thenap.com>

next in thread | raw e-mail | index | archive | help
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C116A4.27CEDAC0
Content-Type: text/plain;
	charset="iso-8859-1"

You could have it authenticate through LDAP and have the mail store on one
server and mount shares to the mail store on the two servers.

Mail server 1--------------------------[Samba or other network share
            >  LDAP Server for auth ]   Mail Store
Mail server 2--------------------------[Samba (or other network share

-Drew


-----Original Message-----
From: Sascha Lucky Luck [mailto:bofh@online.ie]
Sent: Friday, July 27, 2001 8:29 AM
To: Andrew Reid
Cc: freebsd-isp@FreeBSD.ORG
Subject: Re: FreeBSD Mail Toaster CLUSTER


Quoting Andrew Reid <andrew.reid@plug.cx>:

> The notion of setting up a secondary MX host is easy enough,
> but it
> doesn't seem to be enough for what I'd like to do.
> 
> For example:
> 
> +-----------------------+                 +---------+
> |                       |---------------->|   MX1   |
> | Load Balancing Device |                 +---------+
> |                       |                 +---------+
> |                       |---------------->|   MX2   |
> +-----------------------+                 +---------+
> 
> If the Load Balancing Device ("LBD") is sharing out
> connections for
> ports 25 and 110 between MX1 and MX2, I want to be sure that
> if one of
> the two machines goes down, everyone can still get their
> mail.
> 
> I've looked at some methods of doing this where, when accounts
> are
> created, they are equally dispersed amongst your MX farm, but
> that means
> that all users on the dead MX will have no mail access.
> 
> How are people going about delivering distributed,
> redundant,
> load-balanced mail? I was thinking that some form of parallel
> delivery
> could be implemented, but that would result in the load of MX1
> and MX2
> being pretty similar (one would think).
> 
> You don't want to have all your eggs in one basket, but at the
> same
> time, you do. You want to be able to get to your mail -all-
> the time,
> not just when the appropriate server is up. If accounts "joe",
> "thelma"
> and "louise" are on MX1, they still need to be able to get to
> their
> mail, even when the server is down.
> 
> Hmm! Suggestions?

The file system where the user accounts live must then be shared
between the different mail servers. We mounted that from a Network
Appliance Filer cluster, so that was pretty safe to begin with. 
User account information needs to either reside on the shared FS or
must be duplicated (eg. rdist) between the machines.
If you are connected to the server that failed you'll have to
reconnect. Otherwise the user will never notice a server failure.

>    - andrew

HTH,
s.

----------------------------------------------------
Get your free email account at http://www.online.ie/

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message

------_=_NextPart_001_01C116A4.27CEDAC0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.45">
<TITLE>RE: FreeBSD Mail Toaster CLUSTER</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>You could have it authenticate through LDAP and have =
the mail store on one server and mount shares to the mail store on the =
two servers.</FONT></P>

<P><FONT SIZE=3D2>Mail server 1--------------------------[Samba or =
other network share</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; &gt;&nbsp; LDAP Server for auth ]&nbsp;&nbsp; Mail Store</FONT>
<BR><FONT SIZE=3D2>Mail server 2--------------------------[Samba (or =
other network share</FONT>
</P>

<P><FONT SIZE=3D2>-Drew</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Sascha Lucky Luck [<A =
HREF=3D"mailto:bofh@online.ie">mailto:bofh@online.ie</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Friday, July 27, 2001 8:29 AM</FONT>
<BR><FONT SIZE=3D2>To: Andrew Reid</FONT>
<BR><FONT SIZE=3D2>Cc: freebsd-isp@FreeBSD.ORG</FONT>
<BR><FONT SIZE=3D2>Subject: Re: FreeBSD Mail Toaster CLUSTER</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Quoting Andrew Reid =
&lt;andrew.reid@plug.cx&gt;:</FONT>
</P>

<P><FONT SIZE=3D2>&gt; The notion of setting up a secondary MX host is =
easy enough,</FONT>
<BR><FONT SIZE=3D2>&gt; but it</FONT>
<BR><FONT SIZE=3D2>&gt; doesn't seem to be enough for what I'd like to =
do.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; For example:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
+-----------------------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; +---------+</FONT>
<BR><FONT SIZE=3D2>&gt; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|----------------&gt;|&nbsp;&nbsp; MX1&nbsp;&nbsp; |</FONT>
<BR><FONT SIZE=3D2>&gt; | Load Balancing Device =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; +---------+</FONT>
<BR><FONT SIZE=3D2>&gt; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; +---------+</FONT>
<BR><FONT SIZE=3D2>&gt; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|----------------&gt;|&nbsp;&nbsp; MX2&nbsp;&nbsp; |</FONT>
<BR><FONT SIZE=3D2>&gt; =
+-----------------------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; +---------+</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; If the Load Balancing Device (&quot;LBD&quot;) =
is sharing out</FONT>
<BR><FONT SIZE=3D2>&gt; connections for</FONT>
<BR><FONT SIZE=3D2>&gt; ports 25 and 110 between MX1 and MX2, I want to =
be sure that</FONT>
<BR><FONT SIZE=3D2>&gt; if one of</FONT>
<BR><FONT SIZE=3D2>&gt; the two machines goes down, everyone can still =
get their</FONT>
<BR><FONT SIZE=3D2>&gt; mail.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I've looked at some methods of doing this =
where, when accounts</FONT>
<BR><FONT SIZE=3D2>&gt; are</FONT>
<BR><FONT SIZE=3D2>&gt; created, they are equally dispersed amongst =
your MX farm, but</FONT>
<BR><FONT SIZE=3D2>&gt; that means</FONT>
<BR><FONT SIZE=3D2>&gt; that all users on the dead MX will have no mail =
access.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; How are people going about delivering =
distributed,</FONT>
<BR><FONT SIZE=3D2>&gt; redundant,</FONT>
<BR><FONT SIZE=3D2>&gt; load-balanced mail? I was thinking that some =
form of parallel</FONT>
<BR><FONT SIZE=3D2>&gt; delivery</FONT>
<BR><FONT SIZE=3D2>&gt; could be implemented, but that would result in =
the load of MX1</FONT>
<BR><FONT SIZE=3D2>&gt; and MX2</FONT>
<BR><FONT SIZE=3D2>&gt; being pretty similar (one would think).</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; You don't want to have all your eggs in one =
basket, but at the</FONT>
<BR><FONT SIZE=3D2>&gt; same</FONT>
<BR><FONT SIZE=3D2>&gt; time, you do. You want to be able to get to =
your mail -all-</FONT>
<BR><FONT SIZE=3D2>&gt; the time,</FONT>
<BR><FONT SIZE=3D2>&gt; not just when the appropriate server is up. If =
accounts &quot;joe&quot;,</FONT>
<BR><FONT SIZE=3D2>&gt; &quot;thelma&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; and &quot;louise&quot; are on MX1, they still =
need to be able to get to</FONT>
<BR><FONT SIZE=3D2>&gt; their</FONT>
<BR><FONT SIZE=3D2>&gt; mail, even when the server is down.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Hmm! Suggestions?</FONT>
</P>

<P><FONT SIZE=3D2>The file system where the user accounts live must =
then be shared</FONT>
<BR><FONT SIZE=3D2>between the different mail servers. We mounted that =
from a Network</FONT>
<BR><FONT SIZE=3D2>Appliance Filer cluster, so that was pretty safe to =
begin with. </FONT>
<BR><FONT SIZE=3D2>User account information needs to either reside on =
the shared FS or</FONT>
<BR><FONT SIZE=3D2>must be duplicated (eg. rdist) between the =
machines.</FONT>
<BR><FONT SIZE=3D2>If you are connected to the server that failed =
you'll have to</FONT>
<BR><FONT SIZE=3D2>reconnect. Otherwise the user will never notice a =
server failure.</FONT>
</P>

<P><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp; - andrew</FONT>
</P>

<P><FONT SIZE=3D2>HTH,</FONT>
<BR><FONT SIZE=3D2>s.</FONT>
</P>

<P><FONT =
SIZE=3D2>----------------------------------------------------</FONT>
<BR><FONT SIZE=3D2>Get your free email account at <A =
HREF=3D"http://www.online.ie/" =
TARGET=3D"_blank">http://www.online.ie/</A></FONT>;
</P>

<P><FONT SIZE=3D2>To Unsubscribe: send mail to =
majordomo@FreeBSD.org</FONT>
<BR><FONT SIZE=3D2>with &quot;unsubscribe freebsd-isp&quot; in the body =
of the message</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C116A4.27CEDAC0--

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B1A7D9973EBED3119ADD009027DC86492B0CFF>