Can I use (insert shared file system here) to make a highly available Cyrus?

In short, we don't recommend it. If you want to do it, it may possibly work but you may also lose your email or have corrupted cyrus.* files. You can look at the mailing list archives for more information.

There are several critical things that must be supported for this to work: * file locking * mmap() * writing to an mmap()'d file with the write() syscall

In general, this is bad news. Don't do it. Really. About the closest you can currently get is having a "warm spare" that takes over the IP of the affected backend, and have a SAN between the two systems.

CyrusMurder may be a "good enough" solution in some enviornments, as a way to partition failures and spread load across many machines. Combined with a warm-spare approach this can be a good way to achieve highly available systems (though not ones which are fully redundant)

-- RobSiemborski? - 02 Feb 2004

Topic revision: r38 - 31 Aug 2005 - 10:51:14 - TWikiGuest
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback