Re: Upgrading Murder from 2.3 to 2.4

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 11 May 2012, David Mayo wrote:

> We are looking at upgrading from Cyrus IMAP 2.3 to 2.4. We run a Murder
> with one front end server and one back end server. We plan to XFER
> mailboxes from the old back end to a new back end server with more storage.
>
> From the mailing list I understand we should upgrade the front end
> server first before transferring mailboxes.
>
> My planned changes for the front end server are to add the
> suppress_capabilities directive to imapd.conf, ensure the lock directory
> is created on tmpfs and touch a blank user_deny.db. My expectation is
> that I can stop the front end server, upgrade the software and restart
> it with the updated imapd.conf.
>
> As far as the front end upgrade is concerned, is there really any
> difference between the behaviour of 2.3 vs 2.4? Most of the changes
> appear to be focused on the mailbox handling code. Does anyone running a
> Murder have experience of the upgrade from 2.3 to 2.4 they could share?
> Will users notice any difference at this stage?

>From my notes:

5. Stop cyrus on frontends
6. Upgrade cyrus-mm to v2.4
7. Switch all cyrus servers to improved_mbox_sort
8. Upgrade cyrus-fe[123] to v2.4

and some more detailed notes on those steps:

Switch all cyrus servers to improved_mbox_sort
----------------------------------------------
cd /var/spool/cyrus/config
/etc/init.d/cyrus stop
/usr/local/cyrus/bin/ctl_mboxlist -d > mailbox_list.txt
mv mailboxes.db mailboxes.db.unsorted
add "improved_mboxlist_sort: 1" to /etc/imapd.conf
/usr/local/cyrus/bin/ctl_mboxlist -u < mailbox_list.txt
/etc/init.d/cyrus start


Upgrade cyrus-fe[123] to v2.4
------------------------
/etc/init.d/cyrus stop
make install
# clean out db dir
rm /var/spool/cyrus/config/db/*
# suppress new 2.4 capabilities in imapd.conf:
suppress_capabilities: ESEARCH LIST-EXTENDED QRESYNC WITHIN XLIST ENABLE SORT=DISPLAY
/etc/init.d/cyrus start


I upgraded the backends by simply transferring the mailboxes to new 
backend servers that were running v2.4.  This also spread out the load of 
re-indexing all the mailboxes.  I haven't removed the 
suppress_capabilities settings from the frontends yet, so I don't think my 
users have seen any difference.

 	Andy
----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/


[Index of Archives]     [Cyrus SASL]     [Squirrel Mail]     [Asterisk PBX]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [KDE]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux