On Wed, Mar 14, 2001 at 07:54:40PM -0500, Alain Turbide wrote:
> The approach I've tested here is using a linux server with a ReiserFS
> partition replicated between 2 nodes using DRBD. Heartbeat runs on both
> systems and will switch the slave node to master in the event of a failure
> in the Master. This scenerio is strictly failover and only one node has
> write access to the mirrored partition at any one time. By using a
> journaling file system, this eliminates running fsck on the slave to mount
> the mirrored drive in read/write. This has been running on a Cyrus
> mailserver. (Our main server is using Hardware Raid 5 though..) So far
> never seen any problems, corruption, etc. Speed is very good with the
> ReiserFS system as far as I can see (even though it's supposed to have a bit
> higher overhead..). Using rsync works as well but it is difficult and
> tricky doing a proper resync when the original master comes back online.
> Here DRBD and Heartbeat take care of this..
>
> Alain
Having looked for a way around the problem myself, the best thing I've been
able to come up with is having the two MTA's store mail in an LDAP server.
But then you run up the problem of how to get mail out, which is kind of
funky.
The largest problem I've had with this is that I need to have two MX's that
both have write access to the mail store, and haven't come across anything that
will help with this.
