Tried to go to 2.5 and had more serious issues than going to
2.4. From the top of my head I don't recall what it was...
we are aiming for 0 / minimal down time and users changes. I
want to get the mail setup on the new server and just change the
ip address of the new server to the old server's ip address.
Hoping to have minimal impact to the users.
jack
On 04/06/2016 01:25 PM, ktm@xxxxxxxx
wrote:
On Wed, Apr 06, 2016 at 01:20:13PM -0500, Jack Snodgrass via Info-cyrus wrote:Is there a documented process for taking a system from: Cyrus v2.2.13 to Cyrus v2.4.17 I have an old debian box with Cyurs v2.2.13. I have a new debian box with Cyrus v2.4.17 Is there a documented / official process for migrating mail like this? I could not find one. I have rsync'd the mail between the two systems. /usr/lib/cyrus/bin/reconstruct did NOT magically convert the system from the old to the new. I wrote a script to create the mailboxes and their folders. After that ( or maybe before... ) I ran: /usr/lib/cyrus/bin/reconstruct -G -f and I think that has me close to where I want to be. I have mail boxes and folders and test users can view their mail. The 'seen' flags and probably some other flags / acls are not working. Isn't there a simple upgrade / migrate script path that I am failing to find? jackHi Jack, Why are you migrating to v2.5.x? It has been out for quite a while now? If you have a lot of users, the 2.2 -> 2.4 upgrade can be painful I/O-wise. Regards, Ken --
jack - Southlake Texas - http://mylinuxguy.net - 817-601-7338 |
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus