I thought I'd follow up on this thread, as I just this weekend performed such a migration, myself, except I was migrating from Red Hat Linux 6.2 to Slackware Linux Current (pre-8.0), where both systems were cyrus-imap-2.0.15 systems and both systems had Berkeley db-3.2.9.
I not only tarred up my mailspool (/var/spool/imap), but also my sieve directory structure (/var/spool/sieve) and my imap databases directory (/var/imap) and copied them over to the new machine, where I untarred them into the same directory structure. Config files were exactly the same on both systems. I ran ctl_mailbox -r and reconstruct -r after the migration, started master, and everything seems to have migrated perfectly. None of my users has had a complaint yet. So, it would seem, from my experience, that migration from and to identical system types, with the same versions of both cyrus-imap and db-3.2.9 presents no major obstacles. The only problem we encountered was with our sasldb passwords and our mailman passwords, which was likely to have been caused by different salt values (or whatever randomizer is used). However, we maintain a store of our users passwords in plain text, and I was able to use an expect script in conjunction with a shell script I wrote to automatically reset the users passwords to their expected values. Hope this helps, Will --On Thursday, 27 September, 2001 12:16 -0700 David Fuchs <[EMAIL PROTECTED]> wrote: > This morning, I just finished completing exactly what you are doing > (except we use FreeBSD on both systems) by migrating from 1.5.19 to > 2.0.14. Here is a quick guide (I wrote everything down...): * Copy > the 'mailboxes' file from the old Cyrus 1.5.19 to the new machine > somewhere. * Run the command: su <cyrus_user> -c > "/path/to/cyrus-2.0.14/bin/ctl_mboxlist -u < > /path/to/old/cyrus/mailboxes" * This command creates a mailboxes.db > with the information from the old mailboxes file. * I created a > dot-patch (user/ instead of user.) a while ago for my customers, which > means I had to edit the 'mailboxes' file and replace all dots with > slashes before I could import it into Cyrus 2.0.14. You can safely skip > any modifications to the 'mailboxes' file. > * Tar up your mailstore on the old server. ie: tar -zcvf > cyrus-mboxes.tar.gz /path/to/cyrus-1.5.19_partitions * Tar up your > quotas if you have them. ie: tar -zcvf cyrus-quotas.tar.gz > /path/to/cyrus-1.5.19/quota > * ftp or scp the cyrus-mboxes.tar.gz and cyrus-quotas.tar.gz to the new > server. * Untar the mailstore to the proper location, and ensure that > your new imapd.conf correctly reflects the old partition scheme. * > The partition scheme must be identical, or you're going to find yourself > making changes to the mailboxes.db and quotas. > * Untar the quotas to the proper location ie: the imapd.conf's > <config_directory>/quota . > * Reconstruct your mailbox headers and quotas for to ensure integrity. > * su <cyrus_user> -c "/path/to/cyrus-2.0.14/bin/reconstruct" > * su <cyrus_user> -c "/path/to/cyrus-2.0.14/bin/quota -f" > * Start the 'master' process... > * Cross your fingers and test some mailboxes! > Hope that helps! > > -David Fuchs > > > Jesse Ahrens wrote: > > Hi, > I have to admit a fair amount of greenness in this so bear with me. I'm > trying to migrate the mailboxes from a solaris 7 box running Cyrus IMAP > 1.5.19 to a FreeBSD 4.4 box running Cyrus 2.0.14. If anyone has a guide > or a URL to do this I'd be extremely grateful for any knowledge anyone > can lend. Thanks in advance. > > Jesse Ahrens > Unix Systems Administrator > Meridian Advertising > 4850 G St. > Omaha, NE 68117 > 402-733-6400 x266 > > > ---------------------------------------------------------------------------- William K. Hardeman [EMAIL PROTECTED] http://www.wkh.org Always listen to experts. They'll tell you what can't be done and why. Then do it. --Robert A. Heinlein
