Playing with replicated murder

[Michael Loftis]

--On Thursday, March 03, 2005 16:59 +0100 Christoph Moench-Tegeder 
<cmt at burggraben.net> wrote:

> Hi,
> my employer wants to spend some money and buy a cluster filesystem
> for our IMAP servers (not that we currently need it, with only about
> five thousand active users on the largest server).
> The powers that be want to have "high availability" and "load balancing"
> (what load?). This sounds like a replicated murder to me.
> We already do have a SAN (fiberchannel and some spare gigabytes on an EMC)
> and a cluster filesystem (currently we are evaluating Polyserve, has
> anyone had some experience with psfs?).
> I am a little confused over the location of configdirectory, some of its
> contents (like the DB environment, the socket und the proc directorys)
> should be kept per node (I believe), while others (as quota files)
> should be shared between nodes. What about the replicated mailboxes.db?
> What am I missing?

Two Cyrus can not use the spool concurrently at present.  MURDER provides 
only for load distribution.  Replication/failover has to be done seperately 
'somehow'  Basically the only thing you can do is active/passive setup, as 
active/active for a given backend is NOT supported in current MURDER.
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html