Hi Dave, Dave McMurtrie wrote: > As of Cyrus 2.3, the code supports the notion of application-level > replication. It's near real-time replication of all the application > data, but one copy of the data isn't live. This is more of an > active/passive solution, since you have to do something to make cyrus > aware of the 2nd copy of the data if you suffer some type of failure > of > the first copy. Quick question on this. If I setup an active/passive cluster and put the mail spool AND all of the application data on a SAN that both nodes have access to (not simultaneously, of course), doesn't that bypass the need for using "mupdate_config: replicated"? Thanks... Michael Sims ---- 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
