-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2/12/07 5:41 AM, Marten Lehmann wrote: > Hello, > > what do you think about moving the mailspool to a central SAN storage > shared via NFS and having several blades to manage the mmapped files > like seen state, quota etc.? So still only one server is responsible for > a certain set of mailboxes, but these SAN boxes have nice backup and > redundancy features which are hard to get with common servers and there > shouldn't be mmap problems as long as all indices remain on the blade on > a separate metadata-partition. Cyrus and NFS don't get along due to locking issues; I believe this is covered in the docs. I tried this about a year ago and it spewed errors at an impressive rate. Instead, you might want to check out the Cyrus IMAP Aggregator Design page, which allows you to distribute mailboxes across multiple servers: http://asg.web.cmu.edu/cyrus/ag.html dn -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFF0HxpyPxGVjntI4IRAlA8AKCFPCJAFuXkoeyTqI4ofTgoPvxIxACg+spS sLbF5pLBdqaF64S9QnJZe9M= =oNKh -----END PGP SIGNATURE----- ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
