Am Mittwoch, 8. Februar 2017, 17:24:19 CET schrieb Egoitz Aurrekoetxea via Info-cyrus: > I think it should be very similar to using a local filesystem... Does > anyone can tell some experience in this config?.. I know one older "smaller" cyrus setup with i.e. 100 IMAP/POP-Users which has it's complete spool and db (!) on NFSv3 over a Fast Ethernet Switch what works quite OK (as long as we do not want to place a backup restore of the whole spool over that NFS which is slow). The mount is just default but relatime and local_lock=none which may be suboptimal by performance - it could make sense to held locking local only or to disable it completely if you just have one NFS Client with a "single" CYRUS. It may make sense to disable locking (at least remote locks) as it may not be required in that scenario. Holding the db locally could improve performance, but it seems that the OS caching / buffering mechanisms are "enough" there in that old setup. Any further hints / experiences here for different NFS mount options / locking options are welcome - until today we do not run any further cyrus on NFS. It makes sense to monitor the cyrus services (service based) and the NFS mount and if it fail's, you should take care to repair the NFS mount and restart cyrus. Your cyrus conf should have a recover line within start and after such a "crash" a cyrus "reconstruct" run could make sense too. The spooler before LMTP held all messages qeued if the LMTP is not working properly. many thanks and best regards, Niels. -- --- Niels Dettenbach Syndicat IT & Internet http://www.syndicat.com PGP: https://syndicat.com/pub_key.asc ---
Attachment:
signature.asc
Description: This is a digitally signed message part.
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
