Cyrus over NFS with _one_ instance

[Patrick Morris]

For what it's worth, I have a configuration that works this way with a 
NetApp.  We've got a content switch in front of the two servers that 
does automatic failover if the primary box goes down, and so far it's 
worked flawlessly.

I turned off all the database checkpointing and pruning on the secondary 
box in /etc/cyrus.conf, and gave it a slightly lower-priority MX record, 
but otherwise the two boxes are identical.

I'm almost reluctant to recommend this to anyone else, though, given the 
big ol' warning in the FAQ regarding Cyrus and NFS.  All I can say is it 
works for me; YMMV.

Ian G Batten wrote:

>It has always been my understanding that Cyrus isn't supported over NFS.
>Clearly, getting locking working for the scenario of two machines
>running Cyrus sharing /var/imap is Very Hard.  However, what if I only
>want to use _one_ instance of Cyrus, with failover (essentially, one Sun
>sat in front of a NetApp|Auspex|OtherNFSBox, with failover to another
>Sun if the first goes bang).  Are there issues with Cyrus over NFS if
>the running copy of Cyrus has an assurance that it's the only writer?
>
>ian
>  
>


-------------- next part --------------
This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL.  If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail.