Skip to Content.
Sympa Menu

en - [sympa-users] high-availability configurations?

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Miles Fidelman <address@concealed>
  • To: "address@concealed" <address@concealed>
  • Subject: [sympa-users] high-availability configurations?
  • Date: Wed, 14 Mar 2012 11:22:00 -0400


Hi Folks,

I'm currently running a pretty basic high-availability configuration for
our mail server (postfix) and list services (sympa) - they simply run in
a Xen virtual machine, with mirrored disks across two machines (DRBD),
and failover of the VM if something goes wrong (pacemaker).

I'm thinking about migrating the failover host to a 2nd datacenter -
which makes disk mirroring and VM migration a bit trickier, and I really
don't like how brittle all that infrastructure is, so I'm starting to
think about application layer redundancy - two mailservers, two
instances of sympa, at remote locations, multiple DNS records, and
doing something to replicate ques, configurations, databases, archives,
etc. The goal is the same: keep processing traffic if a machine goes
down, and don't lose any data to machine or disk crashes.

Which leads to a question: Are any of you running such a
configuration? If so, can you describe what you're doing? And.. are
there any good references, presentations, etc. that anybody knows about
re. building high-availability, scalable, distributed list processing
infrastructure?

Thank you very much,

Miles Fidelman

--
In theory, there is no difference between theory and practice.
In practice, there is. .... Yogi Berra






Archive powered by MHonArc 2.6.19+.

Top of Page