I tried this command also. It didn't work. It shows syntax again. Please see the supported commands in dovecot 2.0.9 version. This doesn't support replication also as per syntax, if i am not wrong. Please suggest me.
I’ve only used the tcps destination, not the remote. I don’t have 2.0.x on any machines, so I can’t test—have you checked the man page (man doveadm-backup)? To the best of my knowledge, Dsync existed in 2.0.x.
If you setup tcps, make sure you create a CA and certificates for the two servers. If you don’t want to do that and want to use tcp, either do that on a local network or tunnel the connection through SSH.
> On Jul 27, 2020, at 4:59 AM, Kishore Potnuru <kishore.reachme@gmail.com> wrote:
>
> Hi
>
> I am in the process/planning of moving from my existing dovecot imap/pop3 server to 2 new servers (for HA/Resilience). I will be implementing dovecot replication on new servers. Please find my current and new servers versions.
>
I recently did a similar move
>
> What is the best way to stop/copy/migrate the current production data to the new servers? I am planning the following steps. Not sure if it is correct or not.
>
Step 0.
Setup replication and have mail replicate from the old servers to the new servers.
> 1. Stop the Postfix services on the old server and wait for few mins. So that no new emails will be coming to the old servers. Existing emails will be delivered to the receipients.
>
I stopped Postfix on the old servers and did not start Postfix on the new servers. I waited until I saw that no mail was replicating from the old Dovecot to the new servers.
> 2. copy/migrate the data from old server to new servers. Please suggest what is the best way?
Using the replication mechanism was the best method for me.