RE: Moving data from Cyrus 2.3.7 (RHEL) to 2.3.16 (Invoca)
Hi, Quoting Simpson, John R john_simp...@reyrey.com: John Simpson Senior Software Engineer, I. T. Engineering and Operations All the basics seem to be working, thank you again for your help. One last question. With rolling replication, should the replica automatically catch up to the master or do I need to seed the replica with rsync (or a batched sync_client)? You should use sync_client -u to bring the replic in sync with the master. This will also take care of sieve scrtipts and mailboxes that don't change often. I can replicate individual mailboxes with sync_client -m mailbox and mailboxes are replicated when they receive a new message, but if neither of those actions takes place the replica is not populated. Yes M.MengeTel.: (49) 7071/29-70316 Universität Tübingen Fax.: (49) 7071/29-5912 Zentrum für Datenverarbeitung mail: michael.me...@zdv.uni-tuebingen.de Wächterstraße 76 72074 Tübingen smime.p7s Description: S/MIME Signatur Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Moving data from Cyrus 2.3.7 (RHEL) to 2.3.16 (Invoca)
Greetings all, Hi John, We have been running Cyrus 2.3.7, as packaged by Red Hat (cyrus-imapd-2.3.7-2.el5) for some time, and we're upgrading to 2.3.16 (cyrus-imapd-2.3.16-8, thanks Simon) to support replication. We will be You are welcome! The RHEL package is based on ours but it's a bit old now. deploying new servers for 2.3.16, not upgrading the existing servers. In the past, we have simply rsync'd /var/spool/imap and /var/lib/imap to the new servers, but this doesn't seem like a good idea when dealing with different versions and packagings. The good news is you should not have to worry about anything, the RPM takes care of it automagically :) If you are able to test things and quickly shutdown the old production servers I tried it the following way: 1) Check /etc/imapd.conf and /etc/cyrus.conf on the old and the new server. I think they should be identical but better look at them. And of course also check your auth config, for example if you are running saslauthd and such. 2) rsync -aH --delete (you may really want to sync hardlinks as well!) /var/spool/imap and /var/lib/imap from old to new while old is running. 3) service cyrus-imapd stop on the old box so databases are in a consistent state (and are converted to skiplist for migration if they are not already skiplist) 4) Rerun the rsync, should go quite fast now 5) Start Cyrus on the new box and check how it works. Please let me know if you have any problems. Regards, Simon Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Moving data from Cyrus 2.3.7 (RHEL) to 2.3.16 (Invoca)
On 10/14/2010 09:36 AM, Simpson, John R wrote: We have been running Cyrus 2.3.7, as packaged by Red Hat (cyrus-imapd-2.3.7-2.el5) for some time, and we're upgrading to 2.3.16 (cyrus-imapd-2.3.16-8, thanks Simon) to support replication. Speaking of replication, is there any documentation at all on how to set this up and what it does? What about for creating a murder server pool? -- Patrick Goetz Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Moving data from Cyrus 2.3.7 (RHEL) to 2.3.16 (Invoca)
On 10/14/2010 11:20 AM, Patrick Goetz wrote: On 10/14/2010 09:36 AM, Simpson, John R wrote: We have been running Cyrus 2.3.7, as packaged by Red Hat (cyrus-imapd-2.3.7-2.el5) for some time, and we're upgrading to 2.3.16 (cyrus-imapd-2.3.16-8, thanks Simon) to support replication. Speaking of replication, is there any documentation at all on how to set this up and what it does? http://www.cyrusimap.org/docs/cyrus-imapd/2.3.16/install-replication.php What about for creating a murder server pool? http://www.cyrusimap.org/docs/cyrus-imapd/2.3.16/install-murder.php Thanks, Dave -- Dave McMurtrie, SPE Email Systems Team Leader Carnegie Mellon University, Computing Services Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
RE: Moving data from Cyrus 2.3.7 (RHEL) to 2.3.16 (Invoca)
Thank you Simon! To clarify one point, when you say the RPM takes care of it automagically, does that mean that I should rsync the old data to the new server BEFORE installing the cyrus-imapd 2.3.16-8 RPMS? The new servers will be bare-bones -- no pre-existing data or older version of Cyrus. John John Simpson Senior Software Engineer, I. T. Engineering and Operations -Original Message- From: Simon Matter [mailto:simon.mat...@invoca.ch] Sent: Thursday, October 14, 2010 10:56 AM To: Simpson, John R Cc: info-cyrus@lists.andrew.cmu.edu Subject: Re: Moving data from Cyrus 2.3.7 (RHEL) to 2.3.16 (Invoca) Greetings all, Hi John, We have been running Cyrus 2.3.7, as packaged by Red Hat (cyrus-imapd-2.3.7-2.el5) for some time, and we're upgrading to 2.3.16 (cyrus-imapd-2.3.16-8, thanks Simon) to support replication. We will be You are welcome! The RHEL package is based on ours but it's a bit old now. deploying new servers for 2.3.16, not upgrading the existing servers. In the past, we have simply rsync'd /var/spool/imap and /var/lib/imap to the new servers, but this doesn't seem like a good idea when dealing with different versions and packagings. The good news is you should not have to worry about anything, the RPM takes care of it automagically :) If you are able to test things and quickly shutdown the old production servers I tried it the following way: 1) Check /etc/imapd.conf and /etc/cyrus.conf on the old and the new server. I think they should be identical but better look at them. And of course also check your auth config, for example if you are running saslauthd and such. 2) rsync -aH --delete (you may really want to sync hardlinks as well!) /var/spool/imap and /var/lib/imap from old to new while old is running. 3) service cyrus-imapd stop on the old box so databases are in a consistent state (and are converted to skiplist for migration if they are not already skiplist) 4) Rerun the rsync, should go quite fast now 5) Start Cyrus on the new box and check how it works. Please let me know if you have any problems. Regards, Simon Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
RE: Moving data from Cyrus 2.3.7 (RHEL) to 2.3.16 (Invoca)
Thank you Simon! To clarify one point, when you say the RPM takes care of it automagically, does that mean that I should rsync the old data to the new server BEFORE installing the cyrus-imapd 2.3.16-8 RPMS? The new No, you have to install the cyrus-imapd RPMs first. You can even start it to see if it works. But then before syncing, shut it down. What the RPM takes care of it automagically is the conversion of databases according to the defaults in the package and/or your settings in /etc/imapd.conf. Simon servers will be bare-bones -- no pre-existing data or older version of Cyrus. John John Simpson Senior Software Engineer, I. T. Engineering and Operations -Original Message- From: Simon Matter [mailto:simon.mat...@invoca.ch] Sent: Thursday, October 14, 2010 10:56 AM To: Simpson, John R Cc: info-cyrus@lists.andrew.cmu.edu Subject: Re: Moving data from Cyrus 2.3.7 (RHEL) to 2.3.16 (Invoca) Greetings all, Hi John, We have been running Cyrus 2.3.7, as packaged by Red Hat (cyrus-imapd-2.3.7-2.el5) for some time, and we're upgrading to 2.3.16 (cyrus-imapd-2.3.16-8, thanks Simon) to support replication. We will be You are welcome! The RHEL package is based on ours but it's a bit old now. deploying new servers for 2.3.16, not upgrading the existing servers. In the past, we have simply rsync'd /var/spool/imap and /var/lib/imap to the new servers, but this doesn't seem like a good idea when dealing with different versions and packagings. The good news is you should not have to worry about anything, the RPM takes care of it automagically :) If you are able to test things and quickly shutdown the old production servers I tried it the following way: 1) Check /etc/imapd.conf and /etc/cyrus.conf on the old and the new server. I think they should be identical but better look at them. And of course also check your auth config, for example if you are running saslauthd and such. 2) rsync -aH --delete (you may really want to sync hardlinks as well!) /var/spool/imap and /var/lib/imap from old to new while old is running. 3) service cyrus-imapd stop on the old box so databases are in a consistent state (and are converted to skiplist for migration if they are not already skiplist) 4) Rerun the rsync, should go quite fast now 5) Start Cyrus on the new box and check how it works. Please let me know if you have any problems. Regards, Simon Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
RE: Moving data from Cyrus 2.3.7 (RHEL) to 2.3.16 (Invoca)
John Simpson Senior Software Engineer, I. T. Engineering and Operations All the basics seem to be working, thank you again for your help. One last question. With rolling replication, should the replica automatically catch up to the master or do I need to seed the replica with rsync (or a batched sync_client)? I can replicate individual mailboxes with sync_client -m mailbox and mailboxes are replicated when they receive a new message, but if neither of those actions takes place the replica is not populated. John Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
