We (my company) uses DRBD (http://drbd.cubit.at/) with heartbeat and cyrus quite successfully. To distribute load we use multiple heartbeat/drbd backend clusters. Each cluster is comprised of 2 machines connected together via gigabit ethernet cards and serial links. Postfix references ldap (for you mysql) to determine which backend cluster the user's mailbox resides on. Perdition or Cyrus Murder can be used to proxy the user logging in to check mail to the correct backend machine. This solution provides unlimited scalability and pretty good redunancy.
DRBD is a good innexpensive solution. Its proved to be fast and pretty reliable. I would recommend it if you are on a budget. If you have unlimited cash, a kimberlite / SAN cluster might be another good option (havent tried it, but have heard good things). Lee Quoting Michael Loftis <[EMAIL PROTECTED]>: > > > --On Tuesday, May 25, 2004 14:39 -0700 Kevin Baker <[EMAIL PROTECTED]> > wrote: > > > > Thought? This is obviously just a sketch... but I haven't > > seen a this done before as far as the failover solution > > with rsync and thought it might work pretty well. > > rsync sucks for large numbers of files/directories. It has to build an > in-memory tree before it even starts syncing. > > what would be 'nice' to see is something built inside of cyrus to handle > multiple backends but that's a pretty complicated bit of beast. (no i'm > not volunteering ;) ) > > > -- > GPG/PGP --> 0xE736BD7E 5144 6A2D 977A 6651 DFBE 1462 E351 88B9 E736 BD7E > --- > 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 > --- 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
