We are running the replication code in production at Columbia.
We made great use of it Monday morning when one of our backend
machines failed.
Switching to the replica was quite simple and relatively fast (maybe
5 to 10 minutes from deciding to switch to the replica before replica
was fully in action)
I consider the code to stable, though on occasion strange things
happen (e.g. when user renames user.INBOX to user.saved.INBOX) and
you have to restart the replication process (no downtime to Cyrus
involved).
-Patrick Radtke
On Sep 27, 2005, at 8:24 AM, Ken Murchison wrote:
David Carter wrote:
The complication is that there doesn't appear to be anyone left at
CMU to release new versions of Cyrus at the moment. Poor Jeffrey
Eaton seems to be the last man standing there. My own experience
of running things single handed is that it doesn't leave much time
for development work.
Jeff will have development help "real soon now".
--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26 Orchard Park, NY 14127
--PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp
----
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
----
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
