Re: [Dovecot] GlusterFs - Any new progress reports?
> > Sure .. but you can break the index files in exactly the same way as > > with NFS. :) > > > That is right :) For us, all the front end exim servers pass their mail to a single final delivery server. It was done so that we didn't have all the front end servers needing to mount the storage. It also means that if we need to stop local delivery for any reason we're only stopping one exim server. The NFS issue is resolved (I think/hope) by having the front end load balancer use persistent connections to the dovecot servers. All I can say is we've used dovecot since it was a little nipper and have never had any issues with indexes. Regards John www.netserve.co.uk
Re: [Dovecot] GlusterFs - Any new progress reports?
Dare I ask...(as it's not exactly clear from the Gluster docs) If I take 5 storage servers to house my /mail can my cluster of 5 front end dovecot servers all mount/read/write to /mail. The reason I ask is the docs seem to suggest I should be doing 5 servers, having 5 partitions, one for each mail server? Any clues? Regards John
Re: [Dovecot] Dovecot and SATA Backend - filesystems
> The "generally don't see any bugs/issues" is the part I'm worried about > (generally isn't comforting). I was covering my on that one. Sods law dictates as soon as I say 'never' we'll discover an issue. > If you use a more traditional filesystem like ext2/ext3/ufs/etc then yes. > But you can use a cluster filesystem to get around this, and run > active-active. I've spent a week looking at the likes of PVFS, GFS, Lustre and a whole host of different systems, including pNFS (NFS 4.1) At the risk of diverting the thread away from the SATA backend, is there any recommendation for a fault tolerant file service. I'm really looking for 3 or 4 boxes to store data/metadata to support 10 Apache and Dovecot servers. The things I don't like are having a single metadata server be a single point of failure. Regards John
[Dovecot] live and backup auth database
Is there a way of setting dovecot to use two mysql authentication databases, either in a live/failover format or a round robin method. Regards John