replication

[Patrick Boutilier]

On 11/12/2010 03:02 PM, Ron Vachiyer wrote:
> Hello,
>
> I am currently investigating the possibility of adding a second cyrus
> server, the goal being to entirely duplicate the mailspool/userbase and
> have users POP in some sort of balanced means, either DNS load balancing
> or otherwise. We have a pool of inbound MX servers that handle email,
> delivering to Cyrus over lmtp. In the event of a crash, we would want to
> repair/rebuild the dead server and have it re-join the pairing.
>
> I have read on this list's archives that having user interaction on two
> replicated servers is iffy, and I wonder what the point is, or is there
> alternative documentation/methods I should be considering to do this. If
> it is true that popping email off of two servers set up in replication
> is a bad idea, I wonder what the point of it really is?


Master server has a major hardware disaster, you then bring up the slave 
as the master to continue providing service. That is the scenario we are 
using replication for. Oh, and we also run TSM backups on the mail 
stores on the slave, where the load is lower.



>
> Thanks,
>
> R.
>
>
>
> ----
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/