Cyrus replication
saved my ass the other day when my 'master' replica server failed. Now the
'replica' server has become the new master, and I've set up a new replica. I've
pretty much copied the master configuration on the ex-replica and all wen well
with this hitch.
The old master used
>On my servers I have /var/lib/imap and /var/spool/imap. To migrate
>everything on another box with the same software releases, I simply stop
>cyrus, rsync both dirs to the new box and start it again. You only have a
>problem if you for example use BDB for some database backends and your old
>an
I've found a '#yrus.cache' instead of cyrus.cach in a mailbox directory, the
user was unable to access it (I/O error).
What could it be ? It's a 2.3.1 system..
Fabio Rossetti
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.ed
tent:
5A1C0: ptr 0 is 5A228; compare() = 64 skiplist inconsistent: 5
Fabio Rossetti
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
