<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0">
</HEAD>
<BODY>
<B>Sujet</B>: Re: cyrus replication : master to replica and replica to master<BR>
<B>Date</B>: Thu, 22 Oct 2009 15:20:09 +1100me<BR>
<BR>
<PRE>
> Well - it's theoretically possible. But I don't know anyone who's done
> it, and it has the potential to get ugly if you're delivering to the
> same mailboxes at each end. There's nothing I can see that would
> actually stop it working.
>I think Bron failed to put sufficiently large warning signs here :)
>The difference between "in theory this would work" and the practice of
>actually doing it are huge. Basically it works only if you are 100% sure
>that only one side is ever being accessed at a time. eg. IMAP/POP/LMTP/etc.
>If somehow you get an LTMP deliver to different ends, then one side will end
>up overwriting the other.
>In other words, DON'T DO THIS.
>Rob
Thanks rob
i'm very surprised that there is not really official point from cyrus-imap dev team against using cyrus in cluster active/active mode
Since serverals years the messaging service become very important and the clustering system is the right way to provide a real fail over system
After googlize i had read that the only best method is to using drbd but there no really wikis and documentations about implementing this kind of structure.
I would like to restart this topic and discuss.
David
</PRE>
</BODY>
</HTML>