Thanks ! I'll look into it.
Le lun. 16 sept. 2019 à 18:01, a
écrit :
> Date: Sun, 15 Sep 2019 13:04:31 -0600
> From: Scott Lambert
> To: info-cyrus@lists.andrew.cmu.edu
> Subject: Re: Possible issue when upgrading to cyrus 3.0.8 using
> replication ?
> Message-ID
crit :
Date: Fri, 13 Sep 2019 10:20:17 +1000
From: "ellie timoney" mailto:el...@fastmail.com>>
To: info-cyrus@lists.andrew.cmu.edu
<mailto:info-cyrus@lists.andrew.cmu.edu>
Subject: Re: Possible issue when upgrading to cyrus 3.0.8 using
r
9 10:20:17 +1000
> From: "ellie timoney"
> To: info-cyrus@lists.andrew.cmu.edu
> Subject: Re: Possible issue when upgrading to cyrus 3.0.8 using
> replication ?
> Message-ID: <343a16a2-f5a2-4130-aae0-6a4994ab9...@www.fastmail.com>
> Content-Type: text/plain;
Hi Adrien,
The replication upgrade path should be okay. In-place upgrades (that would use
the affected reconstruct to bring mailboxes up to the same version as the
server) would get bitten. Whereas if you replicate to a newer version server,
the mailboxes on the replica will be created at the r
Hello,
I have a server that I can't update running cyrus 2.5.10 which contain
mailboxes that have existed from 2.3 and earlier (around 300Gb total). My
plan is to update by enabling replication with a new server running Debian
Buster (so cyrus 3.0.8) and then shutting down the old server. There wa
