When doing migration, it is very useful to construct a temporary
dovecot-migration.conf which lacks *any* automatic mailbox creation and has
only the bare minimum you need (sieve needs to be configured, and mailbox
attributes). This means no autocreate/autosubscribe loaded, and no auto=creat
> On 11/01/2021 05:18 Thomas Winterstein
> wrote:
>
>
> we were able to narrow down the cause of the problem.
>
>
> After the initial dsync migration process the mailbox GUIDs are the same
> for each mailbox-name across all users.
> Is this intended behaviour of dsync?
> If no
we were able to narrow down the cause of the problem.
After the initial dsync migration process the mailbox GUIDs are the same
for each mailbox-name across all users.
Is this intended behaviour of dsync?
If not, how can this be changed?
After the first replication process the
dsync is intended to be used to change mailbox format, so it should work just
fine.
that's exactly what we thought and why we use dsync to migrate like
described here
https://wiki2.dovecot.org/Migration/Dsync
Our replication is configured according to
https://wiki.dovecot.org/Replicat
dsync is intended to be used to change mailbox format, so it should work just
fine.
Aki
> On 07/01/2021 11:17 Andrea Gabellini
> wrote:
>
>
> Hello,
>
> I had a similar problem some time ago, and the problem was the mailbox
> format change.
>
> Please try to migrate with the same format.
Hello,
I had a similar problem some time ago, and the problem was the mailbox
format change.
Please try to migrate with the same format.
Andrea
Il 05/01/21 15:02, Thomas Winterstein ha scritto:
> No one?
>
> If there are limitations in regards to how dsync in migration and
> replication can o
No one?
If there are limitations in regards to how dsync in migration and
replication can operate together these should be stated clearly in the
documentation.
On 23.12.2020 20:33, Thomas Winterstein wrote:
Hello everyone,
we are working on migrating from dovecot 2.0.9 (maildir) to 2.2.36
Hello everyone,
we are working on migrating from dovecot 2.0.9 (maildir) to 2.2.36
(mdbox). The new cluster has two backend mail servers which replicate
through doveadm replicator. To move the data initially we use doveadm
backup (imapc).
Our migration command
doveadm -o mail_fsync=never
