<div dir="ltr"><div>Thanks ! I'll look into it.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le lun. 16 sept. 2019 à 18:01, <<a href="mailto:info-cyrus-request@lists.andrew.cmu.edu">info-cyrus-request@lists.andrew.cmu.edu</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Date: Sun, 15 Sep 2019 13:04:31 -0600<br>
From: Scott Lambert <<a href="mailto:lambert@lambertfam.org" target="_blank">lambert@lambertfam.org</a>><br>
To: <a href="mailto:info-cyrus@lists.andrew.cmu.edu" target="_blank">info-cyrus@lists.andrew.cmu.edu</a><br>
Subject: Re: Possible issue when upgrading to cyrus 3.0.8 using<br>
replication ?<br>
Message-ID: <<a href="mailto:ee8d6274-d3f4-280a-ff09-528c24b4e090@lambertfam.org" target="_blank">ee8d6274-d3f4-280a-ff09-528c24b4e090@lambertfam.org</a>><br>
Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
<br>
If you can create the mailboxes on the new server, without replication, <br>
perhaps it would be safer/less downtime to use IMAPsync to move the data <br>
to the new server.? It will be slow, but I don't mind slow while the <br>
source server is still online and users are happy.<br>
<br>
On 9/14/19 5:12 PM, Adrien Remillieux wrote:<br>
> Thank you for your answer !<br>
><br>
> Considering what you said I'll try to enable replication on the new <br>
> server. If it doesn't work I'll just schedule some downtime, copy the <br>
> /var/spool/cyrus folder to the new server, install cyrus 3.0.11 from <br>
> the backports and then upgrade the mailboxes in place.<br>
><br>
> We've been using cyrus since 2004 so there's definitely a lot of old <br>
> mailboxes around and I don't which versions of cyrus were used.<br>
><br>
> Cheers,<br>
> Adrien<br>
><br>
> Le?dim. 15 sept. 2019 ??00:35, Adrien Remillieux <br>
> <<a href="mailto:adrien.remillieux@gmail.com" target="_blank">adrien.remillieux@gmail.com</a> <mailto:<a href="mailto:adrien.remillieux@gmail.com" target="_blank">adrien.remillieux@gmail.com</a>>> a <br>
> ?crit?:<br>
><br>
> Date: Fri, 13 Sep 2019 10:20:17 +1000<br>
> From: "ellie timoney" <<a href="mailto:ellie@fastmail.com" target="_blank">ellie@fastmail.com</a> <mailto:<a href="mailto:ellie@fastmail.com" target="_blank">ellie@fastmail.com</a>>><br>
> To: <a href="mailto:info-cyrus@lists.andrew.cmu.edu" target="_blank">info-cyrus@lists.andrew.cmu.edu</a><br>
> <mailto:<a href="mailto:info-cyrus@lists.andrew.cmu.edu" target="_blank">info-cyrus@lists.andrew.cmu.edu</a>><br>
> Subject: Re: Possible issue when upgrading to cyrus 3.0.8 using<br>
> ? ? ? ? replication ?<br>
> Message-ID: <<a href="mailto:343a16a2-f5a2-4130-aae0-6a4994ab9556@www.fastmail.com" target="_blank">343a16a2-f5a2-4130-aae0-6a4994ab9556@www.fastmail.com</a><br>
> <mailto:<a href="mailto:343a16a2-f5a2-4130-aae0-6a4994ab9556@www.fastmail.com" target="_blank">343a16a2-f5a2-4130-aae0-6a4994ab9556@www.fastmail.com</a>>><br>
> Content-Type: text/plain; charset="us-ascii"<br>
><br>
> Hi Adrien,<br>
><br>
> The replication upgrade path should be okay. In-place upgrades<br>
> (that would use the affected reconstruct to bring mailboxes up to<br>
> the same version as the server) would get bitten. Whereas if you<br>
> replicate to a newer version server, the mailboxes on the replica<br>
> will be created at the replica's preferred version already, so you<br>
> don't need to reconstruct afterwards.<br>
><br>
> If you have messages that would theoretically be affected by this<br>
> bug in 3.0, you won't be able to replicate them to 3.0 in the<br>
> first place, because I think replication won't allow the 0 modseq.<br>
> If this arises, I'm not sure how to recover from it and replicate<br>
> the affected messages, since 2.4 and 2.5 won't alter the 0 modseq.<br>
> If it can't replicate them, it will complain about it, so if you<br>
> plan for the replication needing some handholding/restarting,<br>
> you'll at least be able to identify which messages are broken in<br>
> the process, and then figure out how to handle it once you know<br>
> the size of the problem?<br>
><br>
> Another option, if you want to stick with the Debian packages,<br>
> would be to skip 3.0.8 and install 3.0.11 from buster-backports<br>
> (<a href="https://packages.debian.org/buster-backports/cyrus-imapd" rel="noreferrer" target="_blank">https://packages.debian.org/buster-backports/cyrus-imapd</a>), and<br>
> then you'll be immune to the problem. Though you still won't be<br>
> able to replicate the affected messages to the new server, hmm.<br>
><br>
> Cheers,<br>
><br>
> ellie<br>
><br>
> On Thu, Sep 12, 2019, at 6:50 AM, Adrien Remillieux wrote:<br>
> > Hello,<br>
> ><br>
> > I have a server that I can't update running cyrus 2.5.10 which<br>
> contain mailboxes that have existed from 2.3 and earlier (around<br>
> 300Gb total). My plan is to update by enabling replication with a<br>
> new server running Debian Buster (so cyrus 3.0.8) and then<br>
> shutting down the old server. There was a problem when upgrading<br>
> to 3.x.x with mailboxes created with cyrus 2.3 or before and that<br>
> was fixed in 3.0.11 (see<br>
> <a href="https://www.cyrusimap.org/imap/download/release-notes/3.0/x/3.0.11.html" rel="noreferrer" target="_blank">https://www.cyrusimap.org/imap/download/release-notes/3.0/x/3.0.11.html</a><br>
> and <a href="https://github.com/cyrusimap/cyrus-imapd/issues/2839" rel="noreferrer" target="_blank">https://github.com/cyrusimap/cyrus-imapd/issues/2839</a> for the<br>
> bug report)<br>
> ><br>
> > Does this upgrade path suffer from the same issue ? I am not<br>
> familiar with the inner-workings of cyrus. It appears that the<br>
> Debian maintainers have not backported the patch in 3.0.8 (see<br>
> <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933163" rel="noreferrer" target="_blank">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933163</a> and I<br>
> looked at the source code)<br>
> ><br>
> > Cheers,<br>
> > Adrien<br>
> > ----<br>
> > Cyrus Home Page: <a href="http://www.cyrusimap.org/" rel="noreferrer" target="_blank">http://www.cyrusimap.org/</a><br>
> > List Archives/Info:<br>
> <a href="http://lists.andrew.cmu.edu/pipermail/info-cyrus/" rel="noreferrer" target="_blank">http://lists.andrew.cmu.edu/pipermail/info-cyrus/</a><br>
> > To Unsubscribe:<br>
> > <a href="https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus" rel="noreferrer" target="_blank">https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus</a><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL:<br>
> <<a href="http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20190913/5ed8a417/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20190913/5ed8a417/attachment-0001.html</a>><br>
><br>
><br>
> ----<br>
> Cyrus Home Page: <a href="http://www.cyrusimap.org/" rel="noreferrer" target="_blank">http://www.cyrusimap.org/</a><br>
> List Archives/Info: <a href="http://lists.andrew.cmu.edu/pipermail/info-cyrus/" rel="noreferrer" target="_blank">http://lists.andrew.cmu.edu/pipermail/info-cyrus/</a><br>
> To Unsubscribe:<br>
> <a href="https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus" rel="noreferrer" target="_blank">https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20190915/83294228/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20190915/83294228/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
Info-cyrus mailing list<br>
<a href="mailto:Info-cyrus@lists.andrew.cmu.edu" target="_blank">Info-cyrus@lists.andrew.cmu.edu</a><br>
<a href="https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus" rel="noreferrer" target="_blank">https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Info-cyrus Digest, Vol 170, Issue 5<br>
******************************************<br>
</blockquote></div></div>