Re: [Dovecot] High Availability strategies

2009-07-29 Thread Joseba Torre
Thanks a lot for all the answers. We already have high availability on the storage, so we'll go with Timo's proposal, mainly because it's the closer one to our current situation. Thanks! El Sábado 25 Julio 2009 a las 01:58, Timo Sirainen escribió: On Jul 24, 2009, at 5:00 AM, Joseba Torre

Re: [Dovecot] High Availability strategies

2009-07-29 Thread Steffen Kaiser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 27 Jul 2009, Timo Sirainen wrote: BTW. http://dovecot.org/talks/berlin-2009-07-02.pdf has a list of some possible ways to cluster Dovecot. IMO You should place all slides and conference papers online - at least I did not found them on

Re: [Dovecot] High Availability strategies

2009-07-29 Thread Timo Sirainen
On Jul 29, 2009, at 5:39 AM, Steffen Kaiser wrote: On Mon, 27 Jul 2009, Timo Sirainen wrote: BTW. http://dovecot.org/talks/berlin-2009-07-02.pdf has a list of some possible ways to cluster Dovecot. IMO You should place all slides and conference papers online - at least I did not found

Re: [Dovecot] High Availability strategies

2009-07-27 Thread Ed W
I think there is a whitepaper from Dovecot's current main sponsor (before they were called Rackspace) which described their architecture using pairs of servers and DRBD between them. Each server is moderately loaded and active. If one server fails then half the users don't notice and the

Re: [Dovecot] High Availability strategies

2009-07-27 Thread Seth Mattinen
Ed W wrote: I think there is a whitepaper from Dovecot's current main sponsor (before they were called Rackspace) which described their architecture using pairs of servers and DRBD between them. Each server is moderately loaded and active. If one server fails then half the users don't notice

Re: [Dovecot] High Availability strategies

2009-07-27 Thread Timo Sirainen
On Mon, 2009-07-27 at 10:22 -0700, Seth Mattinen wrote: Ed W wrote: I think there is a whitepaper from Dovecot's current main sponsor (before they were called Rackspace) which described their architecture using pairs of servers and DRBD between them. Each server is moderately loaded and

Re: [Dovecot] High Availability strategies

2009-07-27 Thread Timo Sirainen
BTW. http://dovecot.org/talks/berlin-2009-07-02.pdf has a list of some possible ways to cluster Dovecot. signature.asc Description: This is a digitally signed message part

[Dovecot] High Availability strategies

2009-07-24 Thread Joseba Torre
Hi, we have a medium setup (8000 pop and imap users using almost every available client, 800GB of stored mails using maildir on a Celerra NFS server, with index files on local disks, and procmail for local delivery), being served by a Dell PowerEdge 2850 (2GB RAM and dual P4 Xeon 3,2GHz).

Re: [Dovecot] High Availability strategies

2009-07-24 Thread Robert Schetterer
Joseba Torre schrieb: Hi, we have a medium setup (8000 pop and imap users using almost every available client, 800GB of stored mails using maildir on a Celerra NFS server, with index files on local disks, and procmail for local delivery), being served by a Dell PowerEdge 2850 (2GB RAM

Re: [Dovecot] High Availability strategies

2009-07-24 Thread Seth Mattinen
Joseba Torre wrote: Hi, we have a medium setup (8000 pop and imap users using almost every available client, 800GB of stored mails using maildir on a Celerra NFS server, with index files on local disks, and procmail for local delivery), being served by a Dell PowerEdge 2850 (2GB RAM and

Re: [Dovecot] High Availability strategies

2009-07-24 Thread Timo Sirainen
On Jul 24, 2009, at 5:00 AM, Joseba Torre wrote: we have a medium setup (8000 pop and imap users using almost every available client, 800GB of stored mails using maildir on a Celerra NFS server, with index files on local disks, and procmail for local delivery), being served by a Dell PowerEdge

[Dovecot] High availability strategies?

2008-02-05 Thread Ed W
Anyone here trying any high availability strategies for mail servers? (Ralph what do you do?) I am reading up a little on DRBD + OCFS for a master/master setup but this doesn't seem to address how to avoid having a single master proxy process (assuming that we are running on rented equip and