Date: Mon, 30 Jul 2001 10:35:53 +0200 (CEST) From: =?iso-8859-1?q?Fabrizio=20Ravazzini?= <freefabri@yahoo.it> To: freebsd-isp@freebsd.org Subject: Re: FreeBSD Mail Toaster CLUSTER Message-ID: <20010730083553.89918.qmail@web20101.mail.yahoo.com> In-Reply-To: <996207686.1405.14.camel@percible.alfred.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
why not this solution:
After some studies of this mailing list...
+-----------------+
+--| Raid Dsk Array |-----+
| | (NFS) | |
| +-----------------+ |
+--|----+ +--|----+
| MX2 | | MX2 |
| |<----VQalive----->| |
+-------+ +-------+
Ip1: 1.2.3.4 Ip2: 5.6.7.8
| |
| |
+-------------+--------------+
|
|
Ip0:10.11.12.13
MX1 & MX2 are two servers with
Qmail-vpopmail-CourierImap-Sqwebmail installed on both
the machines.
The maildirs of the two MX are on the shared(NFS) Raid
Disk Array or another Machine.
Then MX1 & MX2 with two different Ips (Ip1,Ip2) shares
with VQalive (Inter7.com/Vqalive) the same Ip (Ip0).
Briefly the mail service respond to the Ip0 on one of
the two MXs, if one of the two MXs goes down VQAlive
on the other machine takes the Ip0 of the service, so
the mail is still available (Ip0 is in the DNS).
What do you think of my Idea?
--- Andrew Reid <andrew.reid@plug.cx> ha scritto: >
On 26 Jul 2001 11:10:15 +0200, Christoph Sold wrote:
>
> > As DNS & bind tells, just have two mail servers
> accept SMTP for your
> > domain. Assign different names and A records, as
> well as set both as MX
> > for your domain.
> >
> > If one goes down, the other will get the mail
> automatically.
>
> I've been thinking about putting in another
> mailserver for redundancy.
> 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?
>
> - andrew
>
> --
> void signature () {
> cout << "Andrew Reid -- andrew.reid@plug.cx" <<
> endl ;
> cout << "Cell: +61 401 946 813" << endl;
> cout << "Quidquid latine dictum sit, altum viditur"
> << endl;
> }
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-isp" in the body of the
message
______________________________________________________________________
Do You Yahoo!?
Il tuo indirizzo gratis e per sempre @yahoo.it su http://mail.yahoo.it
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?20010730083553.89918.qmail>