Re: Migration from one server to 2 new servers

[Kishore Potnuru]

Hi,

I have tried the same way as per your suggestion. But it's throwing an
error.

-
[root@production2 log]# doveadm backup -a All -R -u kish...@test.ba.com
imapc:
dsync(kish...@test.ba.com): Info: imapc(production1.baplc.com:143):
Connected to xxx.xxx.xxx.xxx:143 (local yyy.yyy.yyy.yyy:45992)
dsync(kish...@test.ba.com): Warning: imapc(production1.baplc.com:143):
connect(xxx.xxx.xxx.xxx, 143) timed out after 30 seconds - reconnecting
(delay 0 ms)
dsync(kish...@test.ba.com): Info: imapc(production1.baplc.com:143):
Connected to xxx.xxx.xxx.xxx:143 (local yyy.yyy.yyy.yyy:46014)
dsync(kish...@test.ba.com): Error: imapc(production1.baplc.com:143):
connect(xxx.xxx.xxx.xxx, 143) timed out after 30 seconds - disconnecting
dsync(kish...@test.ba.com): Error: User initialization failed: imapc: Login
to production1.baplc.com failed: Disconnected from server
[root@production2 log]#
--

I looked into the production1 (old server) logs. I see the below error.

===
Jul 28 11:14:23 auth: Fatal: Master passdb can't have pass=yes if there are
no passdbs
Jul 28 11:14:23 master: Error: service(auth): command startup failed,
throttling
===

after the above error, I have commented "pass=yes" in production1 (old
server) server, then I see the below error.


Jul 28 11:17:10 auth: Fatal: No passdbs specified in configuration file.
PLAIN mechanism needs one
Jul 28 11:17:10 master: Error: service(auth): command startup failed,
throttling
===

Please suggest me on fixing the issue.

On Tue, Jul 28, 2020 at 6:57 AM Aki Tuomi 
wrote:

> Hi!
>
> Kishore, you got the command wrong..
>
> `doveadm backup -R -u username-goes-here imapc:`
>
> for this to work, you need to configure following things:
>
> imapc_host = old-host-name
> imapc_password = master-password
> imapc_master_user = master-user-name
>
> and on the old host you need
>
> passdb {
>args = /etc/dovecot/passwd.masterusers
>driver = passwd-file
>master = yes
>pass = yes
> }
>
> This should let you pull the mails from the old host to your new host over
> IMAP.
>
> You should probably also look at
>
> https://wiki.dovecot.org/Migration/Dsync
>
> Aki
>
> > On 28/07/2020 03:02 Antonio Leding  wrote:
> >
> >
> > Hey Kishore…
> >
> > I believe this is the thread I mentioned earlier. It is quite long and
> spans a monthly barrier (Feb\Mar 2012) so if you use the “Next\Previous
> message” links, you need to be sure to pick up the thread in each monthly
> archive. I have provided links to the first post of the thread in each
> archive here:
> >
> > https://dovecot.org/list/dovecot/2012-February/133718.html
> > https://dovecot.org/list/dovecot/2012-March/134110.html
> >
> > Also, mention of a working syntax for the remote side command can be
> found in this post:
> >
> > https://dovecot.org/list/dovecot/2012-February/081425.html
> >
> > I’m sure one of the Dovecot devs will chime in at some point but in the
> meantime, hopefully the above will offer some relief…
> >
> >
> >
> >
> > > On Jul 27, 2020, at 4:38 PM, Antonio Leding  wrote:
> > >
> > >
> > > I seem to recall a post a while back where, due to the age of the
> remote end, the remote side command had to be entered in the command
> executed on the local side.
> > >
> > > Do you have dsync on the 2.0.9 machine?
> > >
> > >
> > >
> > >
> > >
> > > > On Jul 27, 2020, at 4:16 PM, Kishore Potnuru <
> kishore.reac...@gmail.com> wrote:
> > > >
> > > >
> > > > This is what my understanding. May be I am also wrong here.
> > > >
> > > > Backup option is there in my new server, production2.
> > > >
> > > > When I use the command with -R option from new server, it is
> connecting to old server, Production1 and giving the output of the doveadm
> backup command in old server to get the data. If you see the command and
> error I posted, it shows the same.
> > > >
> > > > Sorry just incase if I am wrong.
> > > >
> > > > Kishore
> > > >
> > > >
> > > > On Mon, 27 Jul, 2020, 11:32 pm Antonio Leding, 
> wrote:
> > > > > Well that option set still doesn’t look correct…
> > > > >
> > > > > Here is the doveadm option set from my 2.2.2 server which is
> several weeks\months before 2.2.36…
> > > > >
> > > > >
> > > > >
> > > > > [Jul-27 @ 15:25:09 ] > dovecot --version
> > > > > 2.2.2
> > > > >
> > > > > [Jul-27 @ 15:26:53 ] > ls -l /usr/local/bin/doveadm
> > > > > -rwxr-xr-x 1 root root 1379203 May 22 2013 /usr/local/bin/doveadm
> > > > >
> > > > > [Jul-27 @ 15:25:12 ] > doveadm
> > > > > usage: doveadm [-Dv] [-f ]  []
> > > > >
> > > > > altmove [-u |-A] [-S ] [-r] 
> > > > > auth cache|test
> > > > > backup [-u |-A] [-S ] [-dfR] [-l ] [-m
> ] [-n ] [-s ] 
> > > > > batch [-u |-A] [-S ]   [ 
> [..]]
> > > > > config [doveconf parameters]
> > > > > copy [-u |-A] [-S ]  [user  user>] 
> > > > > director add|dump|flush|map|move|remove|ring|ring|ring|status
> > > > > dump [-t ] 
> > > > > exec  [binary parameters]
> > > > > expunge [-u |-A] [-S ] [-d] 
> > > > > 

Re: Migration from one server to 2 new servers

[Kishore Potnuru]

Hi,

I have tried the same way as per your suggestion. But it's throwing the
below error.

-
[root@production2 log]# doveadm backup -a All -R -u kish...@test.ba.com
imapc:
dsync(kish...@test.ba.com): Info: imapc(production1.baplc.com:143):
Connected to 161.2.11.119:143 (local 161.2.12.152:45992)
dsync(kish...@test.ba.com): Warning: imapc(production1.baplc.com:143):
connect(161.2.11.119, 143) timed out after 30 seconds - reconnecting (delay
0 ms)
dsync(kish...@test.ba.com): Info: imapc(production1.baplc.com:143):
Connected to 161.2.11.119:143 (local 161.2.12.152:46014)
dsync(kish...@test.ba.com): Error: imapc(production1.baplc.com:143):
connect(161.2.11.119, 143) timed out after 30 seconds - disconnecting
dsync(kish...@test.ba.com): Error: User initialization failed: imapc: Login
to production1.baplc.com failed: Disconnected from server
[root@production2 log]#
--

I looked into the production1 (old server) logs. I see the below error.

===
Jul 28 11:14:23 auth: Fatal: Master passdb can't have pass=yes if there are
no passdbs
Jul 28 11:14:23 master: Error: service(auth): command startup failed,
throttling
===

After the above error, I have commented "pass=yes" in production1 (old
server) server, then I see the below error.


Jul 28 11:17:10 auth: Fatal: No passdbs specified in configuration file.
PLAIN mechanism needs one
Jul 28 11:17:10 master: Error: service(auth): command startup failed,
throttling
===

Please suggest me on fixing the issue. I have also copied the dovecot.conf
from both the servers below.

=
My old server dovecot.conf (production1):
=

disable_plaintext_auth = no

listen = *
log_path = /var/log/dovecot.log
mail_location = maildir:/z1dev/mail/virtual/%d/%n/Maildir/
passdb {
args = /etc/dovecot/passwd
driver = passwd-file
master = yes
pass = yes
}
pop3_uidl_format = %g
protocols = pop3 imap
ssl = yes
ssl_cert = 
wrote:

> Hi!
>
> Kishore, you got the command wrong..
>
> `doveadm backup -R -u username-goes-here imapc:`
>
> for this to work, you need to configure following things:
>
> imapc_host = old-host-name
> imapc_password = master-password
> imapc_master_user = master-user-name
>
> and on the old host you need
>
> passdb {
>args = /etc/dovecot/passwd.masterusers
>driver = passwd-file
>master = yes
>pass = yes
> }
>
> This should let you pull the mails from the old host to your new host over
> IMAP.
>
> You should probably also look at
>
> https://wiki.dovecot.org/Migration/Dsync
>
> Aki
>
> > On 28/07/2020 03:02 Antonio Leding  wrote:
> >
> >
> > Hey Kishore…
> >
> > I believe this is the thread I mentioned earlier. It is quite long and
> spans a monthly barrier (Feb\Mar 2012) so if you use the “Next\Previous
> message” links, you need to be sure to pick up the thread in each monthly
> archive. I have provided links to the first post of the thread in each
> archive here:
> >
> > https://dovecot.org/list/dovecot/2012-February/133718.html
> > https://dovecot.org/list/dovecot/2012-March/134110.html
> >
> > Also, mention of a working syntax for the remote side command can be
> found in this post:
> >
> > https://dovecot.org/list/dovecot/2012-February/081425.html
> >
> > I’m sure one of the Dovecot devs will chime in at some point but in the
> meantime, hopefully the above will offer some relief…
> >
> >
> >
> >
> > > On Jul 27, 2020, at 4:38 PM, Antonio Leding  wrote:
> > >
> > >
> > > I seem to recall a post a while back where, due to the age of the
> remote end, the remote side command had to be entered in the command
> executed on the local side.
> > >
> > > Do you have dsync on the 2.0.9 machine?
> > >
> > >
> > >
> > >
> > >
> > > > On Jul 27, 2020, at 4:16 PM, Kishore Potnuru <
> kishore.reac...@gmail.com> wrote:
> > > >
> > > >
> > > > This is what my understanding. May be I am also wrong here.
> > > >
> > > > Backup option is there in my new server, production2.
> > > >
> > > > When I use the command with -R option from new server, it is
> connecting to old server, Production1 and giving the output of the doveadm
> backup command in old server to get the data. If you see the command and
> error I posted, it shows the same.
> > > >
> > > > Sorry just incase if I am wrong.
> > > >
> > > > Kishore
> > > >
> > > >
> > > > On Mon, 27 Jul, 2020, 11:32 pm Antonio Leding, 
> wrote:
> > > > > Well that option set still doesn’t look correct…
> > > > >
> > > > > Here is the doveadm option set from my 2.2.2 server which is
> several weeks\months before 2.2.36…
> > > > >
> > > > >
> > > > >
> > > > > [Jul-27 @ 15:25:09 ] > dovecot --version
> > > > > 2.2.2
> > > > >
> > > > > [Jul-27 @ 15:26:53 ] > ls -l /usr/local/bin/doveadm
> > > > > -rwxr-xr-x 1 root root 1379203 May 22 2013 /usr/local/bin/doveadm
> > > > >
> > > > > [Jul-27 @ 15:25:12 ] > doveadm
> > > > > usage: doveadm [-Dv] [-f 

Re: Migration from one server to 2 new servers

[Aki Tuomi]

Hi!

Kishore, you got the command wrong..

`doveadm backup -R -u username-goes-here imapc:`

for this to work, you need to configure following things:

imapc_host = old-host-name
imapc_password = master-password
imapc_master_user = master-user-name

and on the old host you need

passdb {
   args = /etc/dovecot/passwd.masterusers
   driver = passwd-file
   master = yes
   pass = yes
}

This should let you pull the mails from the old host to your new host over 
IMAP. 

You should probably also look at

https://wiki.dovecot.org/Migration/Dsync

Aki

> On 28/07/2020 03:02 Antonio Leding  wrote:
> 
> 
> Hey Kishore…
> 
> I believe this is the thread I mentioned earlier. It is quite long and spans 
> a monthly barrier (Feb\Mar 2012) so if you use the “Next\Previous message” 
> links, you need to be sure to pick up the thread in each monthly archive. I 
> have provided links to the first post of the thread in each archive here:
> 
> https://dovecot.org/list/dovecot/2012-February/133718.html
> https://dovecot.org/list/dovecot/2012-March/134110.html
> 
> Also, mention of a working syntax for the remote side command can be found in 
> this post:
> 
> https://dovecot.org/list/dovecot/2012-February/081425.html
> 
> I’m sure one of the Dovecot devs will chime in at some point but in the 
> meantime, hopefully the above will offer some relief…
> 
> 
> 
> 
> > On Jul 27, 2020, at 4:38 PM, Antonio Leding  wrote:
> > 
> > 
> > I seem to recall a post a while back where, due to the age of the remote 
> > end, the remote side command had to be entered in the command executed on 
> > the local side.
> > 
> > Do you have dsync on the 2.0.9 machine?
> > 
> > 
> > 
> > 
> > 
> > > On Jul 27, 2020, at 4:16 PM, Kishore Potnuru  
> > > wrote:
> > > 
> > > 
> > > This is what my understanding. May be I am also wrong here.
> > > 
> > > Backup option is there in my new server, production2.
> > > 
> > > When I use the command with -R option from new server, it is connecting 
> > > to old server, Production1 and giving the output of the doveadm backup 
> > > command in old server to get the data. If you see the command and error I 
> > > posted, it shows the same.
> > > 
> > > Sorry just incase if I am wrong.
> > > 
> > > Kishore
> > > 
> > > 
> > > On Mon, 27 Jul, 2020, 11:32 pm Antonio Leding,  wrote:
> > > > Well that option set still doesn’t look correct…
> > > > 
> > > > Here is the doveadm option set from my 2.2.2 server which is several 
> > > > weeks\months before 2.2.36…
> > > > 
> > > > 
> > > > 
> > > > [Jul-27 @ 15:25:09 ] > dovecot --version
> > > > 2.2.2
> > > > 
> > > > [Jul-27 @ 15:26:53 ] > ls -l /usr/local/bin/doveadm
> > > > -rwxr-xr-x 1 root root 1379203 May 22 2013 /usr/local/bin/doveadm
> > > > 
> > > > [Jul-27 @ 15:25:12 ] > doveadm
> > > > usage: doveadm [-Dv] [-f ]  []
> > > > 
> > > > altmove [-u |-A] [-S ] [-r] 
> > > > auth cache|test
> > > > backup [-u |-A] [-S ] [-dfR] [-l ] [-m 
> > > > ] [-n ] [-s ] 
> > > > batch [-u |-A] [-S ]   [  [..]]
> > > > config [doveconf parameters]
> > > > copy [-u |-A] [-S ]  [user  > > > user>] 
> > > > director add|dump|flush|map|move|remove|ring|ring|ring|status
> > > > dump [-t ] 
> > > > exec  [binary parameters]
> > > > expunge [-u |-A] [-S ] [-d] 
> > > > fetch [-u |-A] [-S ]  
> > > > force-resync [-u |-A] [-S ] 
> > > > fs copy|delete|get|iter|iter-dirs|put|stat
> > > > help 
> > > > import [-u |-A] [-S ] [-s]  
> > > >  
> > > > index [-u |-A] [-S ] [-q] [-n ]  > > > mask>
> > > > instance list|remove
> > > > kick [-a ] [-f] [|]
> > > > log errors|find|reopen|test
> > > > mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe
> > > > mount add|list|remove
> > > > move [-u |-A] [-S ]  [user  > > > user>] 
> > > > penalty [-a ] []
> > > > proxy kick|list
> > > > purge [-u |-A] [-S ]
> > > > pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-t hash] [-u user] [-V]
> > > > reload
> > > > replicator remove|replicate|status
> > > > search [-u |-A] [-S ] 
> > > > sis deduplicate|find
> > > > stats dump|top
> > > > stop
> > > > sync [-u |-A] [-S ] [-dfR] [-l ] [-m 
> > > > ] [-n ] [-s ] 
> > > > user [-a ] [-x ] [-f field] [-u]  > > > mask> [...]
> > > > who [-a ] [-1] [] []
> > > > zlibconnect  []
> > > > 
> > > > 
> > > > 
> > > > 
> > > > > On Jul 27, 2020, at 3:28 PM, Kishore Potnuru 
> > > > >  wrote:
> > > > > 
> > > > > 
> > > > > Oh, I am extremely sorry. I was confused when typing the issue. 
> > > > > Please help me in fixing the issue. Production1 is my old server. 
> > > > > Production2 is my new server. Typing here correctly. Ignore all 
> > > > > previous one's.
> > > > > 
> > > > > > The new version is:
> > > > > > 
> > > > > > [root@production2 ~]# dovecot --version
> > > > > > 2.2.36 (1f10bfa63)
> > > > > > 
> > > > > > 
> > > > > > The old version is : 
> > > > > > ==
> > > > > > [root@production1 ~]# dovecot --version
> > > > > > 2.0.9
> > > > > > 
> > > > > > 
> > > > > > I have executed the command 

Re: Migration from one server to 2 new servers

[Antonio Leding]

Hey Kishore…

I believe this is the thread I mentioned earlier.  It is quite long and spans a 
monthly barrier (Feb\Mar 2012) so if you use the “Next\Previous message” links, 
you need to be sure to pick up the thread in each monthly archive.  I have 
provided links to the first post of the thread in each archive here:

https://dovecot.org/list/dovecot/2012-February/133718.html 

https://dovecot.org/list/dovecot/2012-March/134110.html 


Also, mention of a working syntax for the remote side command can be found in 
this post:  

https://dovecot.org/list/dovecot/2012-February/081425.html 


I’m sure one of the Dovecot devs will chime in at some point but in the 
meantime, hopefully the above will offer some relief…



> On Jul 27, 2020, at 4:38 PM, Antonio Leding  wrote:
> 
> I seem to recall a post a while back where, due to the age of the remote end, 
> the remote side command had to be entered in the command executed on the  
> local side.
> 
> Do you have dsync on the 2.0.9 machine?
> 
> 
> 
>> On Jul 27, 2020, at 4:16 PM, Kishore Potnuru > > wrote:
>> 
>> This is what my understanding. May be I am also wrong here. 
>> 
>> Backup option is there in my new server, production2. 
>> 
>> When I use the command with -R option from new server, it is connecting to 
>> old server, Production1 and giving the output of the doveadm backup command 
>> in old server to get the data. If you see the command and error I posted, it 
>> shows the same. 
>> 
>> Sorry just incase if I am wrong.
>> 
>> Kishore
>> 
>> On Mon, 27 Jul, 2020, 11:32 pm Antonio Leding, > > wrote:
>> Well that option set still doesn’t look correct…
>> 
>> Here is the doveadm option set from my 2.2.2 server which is several 
>> weeks\months before 2.2.36…
>> 
>> 
>> 
>> [Jul-27 @ 15:25:09 ] > dovecot --version
>> 2.2.2
>> 
>> [Jul-27 @ 15:26:53 ] > ls -l /usr/local/bin/doveadm
>> -rwxr-xr-x 1 root root 1379203 May 22  2013 /usr/local/bin/doveadm
>> 
>> [Jul-27 @ 15:25:12 ] > doveadm
>> usage: doveadm [-Dv] [-f ]  []
>> 
>>   altmove  [-u |-A] [-S ] [-r] 
>>   auth cache|test
>>   backup   [-u |-A] [-S ] [-dfR] [-l ] [-m 
>> ] [-n ] [-s ] 
>>   batch[-u |-A] [-S ]   [  
>> [..]]
>>   config   [doveconf parameters]
>>   copy [-u |-A] [-S ]  [user > user>] 
>>   director add|dump|flush|map|move|remove|ring|ring|ring|status
>>   dump [-t ] 
>>   exec  [binary parameters]
>>   expunge  [-u |-A] [-S ] [-d] 
>>   fetch[-u |-A] [-S ]  
>>   force-resync [-u |-A] [-S ] 
>>   fs   copy|delete|get|iter|iter-dirs|put|stat
>>   help 
>>   import   [-u |-A] [-S ] [-s]  
>>  
>>   index[-u |-A] [-S ] [-q] [-n ] 
>> 
>>   instance list|remove
>>   kick [-a ] [-f] [|]
>>   log  errors|find|reopen|test
>>   mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
>>   mountadd|list|remove
>>   move [-u |-A] [-S ]  [user > user>] 
>>   penalty  [-a ] []
>>   proxykick|list
>>   purge[-u |-A] [-S ]
>>   pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-t hash] [-u 
>> user] [-V]
>>   reload
>>   replicator   remove|replicate|status
>>   search   [-u |-A] [-S ] 
>>   sis  deduplicate|find
>>   statsdump|top
>>   stop
>>   sync [-u |-A] [-S ] [-dfR] [-l ] [-m 
>> ] [-n ] [-s ] 
>>   user [-a ] [-x ] [-f field] [-u] 
>>  [...]
>>   who  [-a ] [-1] [] []
>>   zlibconnect   []
>> 
>> 
>>> On Jul 27, 2020, at 3:28 PM, Kishore Potnuru >> > wrote:
>>> 
>>> Oh, I am extremely sorry. I was confused when typing the issue. Please help 
>>> me in fixing the issue. Production1 is my old server. Production2 is my new 
>>> server. Typing here correctly. Ignore all previous one's.
>>> 
>>> The new version is:
>>> 
>>> [root@production2 ~]# dovecot --version
>>> 2.2.36 (1f10bfa63)
>>> 
>>> 
>>> The old version is : 
>>> ==
>>> [root@production1 ~]# dovecot --version
>>> 2.0.9
>>> 
>>> 
>>> I have executed the command from the new server:
>>> 
>>> 
>>> 
>>> =
>>> [root@production2 test.org.com ]# doveadm backup -R 
>>> -u kish...@test.org.com  
>>> remote:vm...@production1.baplc.com 
>>> 
>>> vm...@production1.baplc.com 's password:
>>> usage: doveadm [-Dv] [-f ]  []
>>> 
>>>   altmove  [-u |-A] [-S ] 
>>>   auth [-a ] [-x ]  []
>>>   config   [doveconf parameters]
>>>   director add|flush|map|remove|status
>>>   dump [-t ] 
>>>   expunge  [-u |-A] [-S ] 
>>>   fetch   

Re: Migration from one server to 2 new servers

[Antonio Leding]

I seem to recall a post a while back where, due to the age of the remote end, 
the remote side command had to be entered in the command executed on the  local 
side.

Do you have dsync on the 2.0.9 machine?



> On Jul 27, 2020, at 4:16 PM, Kishore Potnuru  
> wrote:
> 
> This is what my understanding. May be I am also wrong here. 
> 
> Backup option is there in my new server, production2. 
> 
> When I use the command with -R option from new server, it is connecting to 
> old server, Production1 and giving the output of the doveadm backup command 
> in old server to get the data. If you see the command and error I posted, it 
> shows the same. 
> 
> Sorry just incase if I am wrong.
> 
> Kishore
> 
> On Mon, 27 Jul, 2020, 11:32 pm Antonio Leding,  > wrote:
> Well that option set still doesn’t look correct…
> 
> Here is the doveadm option set from my 2.2.2 server which is several 
> weeks\months before 2.2.36…
> 
> 
> 
> [Jul-27 @ 15:25:09 ] > dovecot --version
> 2.2.2
> 
> [Jul-27 @ 15:26:53 ] > ls -l /usr/local/bin/doveadm
> -rwxr-xr-x 1 root root 1379203 May 22  2013 /usr/local/bin/doveadm
> 
> [Jul-27 @ 15:25:12 ] > doveadm
> usage: doveadm [-Dv] [-f ]  []
> 
>   altmove  [-u |-A] [-S ] [-r] 
>   auth cache|test
>   backup   [-u |-A] [-S ] [-dfR] [-l ] [-m 
> ] [-n ] [-s ] 
>   batch[-u |-A] [-S ]   [  
> [..]]
>   config   [doveconf parameters]
>   copy [-u |-A] [-S ]  [user  user>] 
>   director add|dump|flush|map|move|remove|ring|ring|ring|status
>   dump [-t ] 
>   exec  [binary parameters]
>   expunge  [-u |-A] [-S ] [-d] 
>   fetch[-u |-A] [-S ]  
>   force-resync [-u |-A] [-S ] 
>   fs   copy|delete|get|iter|iter-dirs|put|stat
>   help 
>   import   [-u |-A] [-S ] [-s]  
>  
>   index[-u |-A] [-S ] [-q] [-n ] 
> 
>   instance list|remove
>   kick [-a ] [-f] [|]
>   log  errors|find|reopen|test
>   mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
>   mountadd|list|remove
>   move [-u |-A] [-S ]  [user  user>] 
>   penalty  [-a ] []
>   proxykick|list
>   purge[-u |-A] [-S ]
>   pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-t hash] [-u 
> user] [-V]
>   reload
>   replicator   remove|replicate|status
>   search   [-u |-A] [-S ] 
>   sis  deduplicate|find
>   statsdump|top
>   stop
>   sync [-u |-A] [-S ] [-dfR] [-l ] [-m 
> ] [-n ] [-s ] 
>   user [-a ] [-x ] [-f field] [-u] 
>  [...]
>   who  [-a ] [-1] [] []
>   zlibconnect   []
> 
> 
>> On Jul 27, 2020, at 3:28 PM, Kishore Potnuru > > wrote:
>> 
>> Oh, I am extremely sorry. I was confused when typing the issue. Please help 
>> me in fixing the issue. Production1 is my old server. Production2 is my new 
>> server. Typing here correctly. Ignore all previous one's.
>> 
>> The new version is:
>> 
>> [root@production2 ~]# dovecot --version
>> 2.2.36 (1f10bfa63)
>> 
>> 
>> The old version is : 
>> ==
>> [root@production1 ~]# dovecot --version
>> 2.0.9
>> 
>> 
>> I have executed the command from the new server:
>> 
>> 
>> 
>> =
>> [root@production2 test.org.com ]# doveadm backup -R -u 
>> kish...@test.org.com  
>> remote:vm...@production1.baplc.com 
>> 
>> vm...@production1.baplc.com 's password:
>> usage: doveadm [-Dv] [-f ]  []
>> 
>>   altmove  [-u |-A] [-S ] 
>>   auth [-a ] [-x ]  []
>>   config   [doveconf parameters]
>>   director add|flush|map|remove|status
>>   dump [-t ] 
>>   expunge  [-u |-A] [-S ] 
>>   fetch[-u |-A] [-S ]  
>>   force-resync [-u |-A] [-S ] 
>>   help 
>>   import   [-u |-A] [-S ]  
>>  
>>   kick [-a ] [-f] [|]
>>   log  find|reopen|test
>>   mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
>>   penalty  [-a ] []
>>   purge[-u |-A] [-S ]
>>   pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
>>   reload
>>   search   [-u |-A] [-S ] 
>>   sis  deduplicate|find
>>   stop
>>   user [-a ] [-x ]  [...]
>>   who  [-a ] [-1] [] []
>> dsync-local(kish...@test.org.com ): Error: 
>> read(vm...@production1.baplc.com ) 
>> failed: EOF (version not received)
>> dsync-local(kish...@test.org.com ): Error: 
>> Remote command returned error 1: ssh -lvmail production1.baplc.com 
>>  doveadm dsync-server -ukish...@test.org.com 
>> 
>> 
>> [root@production2 test.org.com ]#
>> 
>> =
>> 
>> 
>> On 

Re: Migration from one server to 2 new servers

[Kishore Potnuru]

This is what my understanding. May be I am also wrong here.

Backup option is there in my new server, production2.

When I use the command with -R option from new server, it is connecting to
old server, Production1 and giving the output of the doveadm backup command
in old server to get the data. If you see the command and error I posted,
it shows the same.

Sorry just incase if I am wrong.

Kishore

On Mon, 27 Jul, 2020, 11:32 pm Antonio Leding,  wrote:

> Well that option set still doesn’t look correct…
>
> Here is the doveadm option set from my 2.2.2 server which is several
> weeks\months before 2.2.36…
>
>
>
> [Jul-27 @ 15:25:09 ] > dovecot --version
> 2.2.2
>
> [Jul-27 @ 15:26:53 ] > ls -l /usr/local/bin/doveadm
> -rwxr-xr-x 1 root root 1379203 May 22  2013 /usr/local/bin/doveadm
>
> [Jul-27 @ 15:25:12 ] > doveadm
> usage: doveadm [-Dv] [-f ]  []
>
>   altmove  [-u |-A] [-S ] [-r] 
>   auth cache|test
>   backup   [-u |-A] [-S ] [-dfR] [-l ] [-m
> ] [-n ] [-s ] 
>   batch[-u |-A] [-S ]   [
>  [..]]
>   config   [doveconf parameters]
>   copy [-u |-A] [-S ]  [user
> ] 
>   director add|dump|flush|map|move|remove|ring|ring|ring|status
>   dump [-t ] 
>   exec  [binary parameters]
>   expunge  [-u |-A] [-S ] [-d] 
>   fetch[-u |-A] [-S ]  
>   force-resync [-u |-A] [-S ] 
>   fs   copy|delete|get|iter|iter-dirs|put|stat
>   help 
>   import   [-u |-A] [-S ] [-s]  location>  
>   index[-u |-A] [-S ] [-q] [-n ]
> 
>   instance list|remove
>   kick [-a ] [-f] [|]
>   log  errors|find|reopen|test
>   mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
>   mountadd|list|remove
>   move [-u |-A] [-S ]  [user
> ] 
>   penalty  [-a ] []
>   proxykick|list
>   purge[-u |-A] [-S ]
>   pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-t hash] [-u
> user] [-V]
>   reload
>   replicator   remove|replicate|status
>   search   [-u |-A] [-S ] 
>   sis  deduplicate|find
>   statsdump|top
>   stop
>   sync [-u |-A] [-S ] [-dfR] [-l ] [-m
> ] [-n ] [-s ] 
>   user [-a ] [-x ] [-f field] [-u]
>  [...]
>   who  [-a ] [-1] [] []
>   zlibconnect   []
>
>
> On Jul 27, 2020, at 3:28 PM, Kishore Potnuru 
> wrote:
>
> Oh, I am extremely sorry. I was confused when typing the issue. Please
> help me in fixing the issue. Production1 is my old server. Production2 is
> my new server. Typing here correctly. Ignore all previous one's.
>
> The new version is:
> 
> [root@production2 ~]# dovecot --version
> 2.2.36 (1f10bfa63)
>
>
> The old version is :
> ==
> [root@production1 ~]# dovecot --version
> 2.0.9
>
>
> I have executed the command from the new server:
>
>
>
> =
> [root@production2 test.org.com]# doveadm backup -R -u kish...@test.org.com
>  remote:vm...@production1.baplc.com
> vm...@production1.baplc.com's password:
> usage: doveadm [-Dv] [-f ]  []
>
>   altmove  [-u |-A] [-S ] 
>   auth [-a ] [-x ]  []
>   config   [doveconf parameters]
>   director add|flush|map|remove|status
>   dump [-t ] 
>   expunge  [-u |-A] [-S ] 
>   fetch[-u |-A] [-S ]  
>   force-resync [-u |-A] [-S ] 
>   help 
>   import   [-u |-A] [-S ] 
>  
>   kick [-a ] [-f] [|]
>   log  find|reopen|test
>   mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
>   penalty  [-a ] []
>   purge[-u |-A] [-S ]
>   pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
>   reload
>   search   [-u |-A] [-S ] 
>   sis  deduplicate|find
>   stop
>   user [-a ] [-x ]  [...]
>   who  [-a ] [-1] [] []
> dsync-local(kish...@test.org.com): Error: read(vm...@production1.baplc.com)
> failed: EOF (version not received)
> dsync-local(kish...@test.org.com): Error: Remote command returned error
> 1: ssh -lvmail production1.baplc.com doveadm dsync-server -
> ukish...@test.org.com
>
> [root@production2 test.org.com]#
>
> =
>
>
>
> On Mon, 27 Jul, 2020, 11:18 pm Antonio Leding,  wrote:
>
>> Fair enough but the command snippet I posted was taken directly from your
>> earlier post dated *Mon Jul 27 23:11:06 EEST 2020* and it does say
>> “production1”…I just double-checked as well...
>>
>> FWIW…the server order in the command you just pasted is the exact reverse
>> from the Jul 27th post I mentioned above…
>>
>> Here you appear to be exec’ing the command on prod2 and trying to pull
>> from the remote of prod 1…your earlier post was exec’ing on prod1 and
>> pulling from the remote of prod2…
>>
>>
>>
>>
>>
>>
>> On Jul 27, 2020, at 3:10 PM, Kishore Potnuru 
>> wrote:
>>
>> I am executing the command from the new server. I was executing the
>> command from production2 server only. It has the backup option, but whereas
>> 

Re: Migration from one server to 2 new servers

[Antonio Leding]

Well that option set still doesn’t look correct…

Here is the doveadm option set from my 2.2.2 server which is several 
weeks\months before 2.2.36…



[Jul-27 @ 15:25:09 ] > dovecot --version
2.2.2

[Jul-27 @ 15:26:53 ] > ls -l /usr/local/bin/doveadm
-rwxr-xr-x 1 root root 1379203 May 22  2013 /usr/local/bin/doveadm

[Jul-27 @ 15:25:12 ] > doveadm
usage: doveadm [-Dv] [-f ]  []

  altmove  [-u |-A] [-S ] [-r] 
  auth cache|test
  backup   [-u |-A] [-S ] [-dfR] [-l ] [-m 
] [-n ] [-s ] 
  batch[-u |-A] [-S ]   [  
[..]]
  config   [doveconf parameters]
  copy [-u |-A] [-S ]  [user ] 
  director add|dump|flush|map|move|remove|ring|ring|ring|status
  dump [-t ] 
  exec  [binary parameters]
  expunge  [-u |-A] [-S ] [-d] 
  fetch[-u |-A] [-S ]  
  force-resync [-u |-A] [-S ] 
  fs   copy|delete|get|iter|iter-dirs|put|stat
  help 
  import   [-u |-A] [-S ] [-s]  
 
  index[-u |-A] [-S ] [-q] [-n ] 

  instance list|remove
  kick [-a ] [-f] [|]
  log  errors|find|reopen|test
  mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
  mountadd|list|remove
  move [-u |-A] [-S ]  [user ] 
  penalty  [-a ] []
  proxykick|list
  purge[-u |-A] [-S ]
  pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-t hash] [-u user] 
[-V]
  reload
  replicator   remove|replicate|status
  search   [-u |-A] [-S ] 
  sis  deduplicate|find
  statsdump|top
  stop
  sync [-u |-A] [-S ] [-dfR] [-l ] [-m 
] [-n ] [-s ] 
  user [-a ] [-x ] [-f field] [-u]  [...]
  who  [-a ] [-1] [] []
  zlibconnect   []


> On Jul 27, 2020, at 3:28 PM, Kishore Potnuru  
> wrote:
> 
> Oh, I am extremely sorry. I was confused when typing the issue. Please help 
> me in fixing the issue. Production1 is my old server. Production2 is my new 
> server. Typing here correctly. Ignore all previous one's.
> 
> The new version is:
> 
> [root@production2 ~]# dovecot --version
> 2.2.36 (1f10bfa63)
> 
> 
> The old version is : 
> ==
> [root@production1 ~]# dovecot --version
> 2.0.9
> 
> 
> I have executed the command from the new server:
> 
> 
> 
> =
> [root@production2 test.org.com ]# doveadm backup -R -u 
> kish...@test.org.com  
> remote:vm...@production1.baplc.com 
> 
> vm...@production1.baplc.com 's password:
> usage: doveadm [-Dv] [-f ]  []
> 
>   altmove  [-u |-A] [-S ] 
>   auth [-a ] [-x ]  []
>   config   [doveconf parameters]
>   director add|flush|map|remove|status
>   dump [-t ] 
>   expunge  [-u |-A] [-S ] 
>   fetch[-u |-A] [-S ]  
>   force-resync [-u |-A] [-S ] 
>   help 
>   import   [-u |-A] [-S ]   parent mailbox> 
>   kick [-a ] [-f] [|]
>   log  find|reopen|test
>   mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
>   penalty  [-a ] []
>   purge[-u |-A] [-S ]
>   pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
>   reload
>   search   [-u |-A] [-S ] 
>   sis  deduplicate|find
>   stop
>   user [-a ] [-x ]  [...]
>   who  [-a ] [-1] [] []
> dsync-local(kish...@test.org.com ): Error: 
> read(vm...@production1.baplc.com ) 
> failed: EOF (version not received)
> dsync-local(kish...@test.org.com ): Error: 
> Remote command returned error 1: ssh -lvmail production1.baplc.com 
>  doveadm dsync-server -ukish...@test.org.com 
> 
> 
> [root@production2 test.org.com ]#
> 
> =
> 
> 
> On Mon, 27 Jul, 2020, 11:18 pm Antonio Leding,  > wrote:
> Fair enough but the command snippet I posted was taken directly from your 
> earlier post dated Mon Jul 27 23:11:06 EEST 2020 and it does say 
> “production1”…I just double-checked as well...
> 
> FWIW…the server order in the command you just pasted is the exact reverse 
> from the Jul 27th post I mentioned above…
> 
> Here you appear to be exec’ing the command on prod2 and trying to pull from 
> the remote of prod 1…your earlier post was exec’ing on prod1 and pulling from 
> the remote of prod2…
> 
> 
> 
> 
> 
> 
>> On Jul 27, 2020, at 3:10 PM, Kishore Potnuru > > wrote:
>> 
>> I am executing the command from the new server. I was executing the command 
>> from production2 server only. It has the backup option, but whereas 
>> production1 doesn't have it. Though I am executing from production2, I am 
>> seeing the below error. Is it becasue production1 server doesn't have that 
>> 

Re: Migration from one server to 2 new servers

[Kishore Potnuru]

Oh, I am extremely sorry. I was confused when typing the issue. Please help
me in fixing the issue. Production1 is my old server. Production2 is my new
server. Typing here correctly. Ignore all previous one's.

The new version is:

[root@production2 ~]# dovecot --version
2.2.36 (1f10bfa63)


The old version is :
==
[root@production1 ~]# dovecot --version
2.0.9


I have executed the command from the new server:



=
[root@production2 test.org.com]# doveadm backup -R -u kish...@test.org.com
remote:vm...@production1.baplc.com
vm...@production1.baplc.com's password:
usage: doveadm [-Dv] [-f ]  []

  altmove  [-u |-A] [-S ] 
  auth [-a ] [-x ]  []
  config   [doveconf parameters]
  director add|flush|map|remove|status
  dump [-t ] 
  expunge  [-u |-A] [-S ] 
  fetch[-u |-A] [-S ]  
  force-resync [-u |-A] [-S ] 
  help 
  import   [-u |-A] [-S ] 
 
  kick [-a ] [-f] [|]
  log  find|reopen|test
  mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
  penalty  [-a ] []
  purge[-u |-A] [-S ]
  pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
  reload
  search   [-u |-A] [-S ] 
  sis  deduplicate|find
  stop
  user [-a ] [-x ]  [...]
  who  [-a ] [-1] [] []
dsync-local(kish...@test.org.com): Error: read(vm...@production1.baplc.com)
failed: EOF (version not received)
dsync-local(kish...@test.org.com): Error: Remote command returned error 1:
ssh -lvmail production1.baplc.com doveadm dsync-server -
ukish...@test.org.com

[root@production2 test.org.com]#

=



On Mon, 27 Jul, 2020, 11:18 pm Antonio Leding,  wrote:

> Fair enough but the command snippet I posted was taken directly from your
> earlier post dated *Mon Jul 27 23:11:06 EEST 2020* and it does say
> “production1”…I just double-checked as well...
>
> FWIW…the server order in the command you just pasted is the exact reverse
> from the Jul 27th post I mentioned above…
>
> Here you appear to be exec’ing the command on prod2 and trying to pull
> from the remote of prod 1…your earlier post was exec’ing on prod1 and
> pulling from the remote of prod2…
>
>
>
>
>
>
> On Jul 27, 2020, at 3:10 PM, Kishore Potnuru 
> wrote:
>
> I am executing the command from the new server. I was executing the
> command from production2 server only. It has the backup option, but whereas
> production1 doesn't have it. Though I am executing from production2, I am
> seeing the below error. Is it becasue production1 server doesn't have that
> option? Please let me know, if it is confusing.
>
>
> The new version is:
> 
> [root@production2 ~]# dovecot --version
> 2.2.36 (1f10bfa63)
>
>
> The old version is :
> ==
> [root@production1 ~]# dovecot --version
> 2.0.9
>
>
> I have executed the command from the new server:
>
>
>
> =
> [root@production2 test.org.com]# doveadm backup -R -u kish...@test.org.com
> remote:vm...@production1.baplc.com
> vm...@production1.baplc.com's password:
> usage: doveadm [-Dv] [-f ]  []
>
>   altmove  [-u |-A] [-S ] 
>   auth [-a ] [-x ]  []
>   config   [doveconf parameters]
>   director add|flush|map|remove|status
>   dump [-t ] 
>   expunge  [-u |-A] [-S ] 
>   fetch[-u |-A] [-S ]  
>   force-resync [-u |-A] [-S ] 
>   help 
>   import   [-u |-A] [-S ] 
>  
>   kick [-a ] [-f] [|]
>   log  find|reopen|test
>   mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
>   penalty  [-a ] []
>   purge[-u |-A] [-S ]
>   pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
>   reload
>   search   [-u |-A] [-S ] 
>   sis  deduplicate|find
>   stop
>   user [-a ] [-x ]  [...]
>   who  [-a ] [-1] [] []
> dsync-local(kish...@test.org.com): Error: read(vm...@production1.baplc.com)
> failed: EOF (version not received)
> dsync-local(kish...@test.org.com): Error: Remote command returned error
> 1: ssh -lvmail production1.baplc.com doveadm dsync-server -
> ukish...@test.org.com
>
> [root@production2 test.org.com]#
>
> =
>
> On Mon, Jul 27, 2020 at 10:55 PM Antonio Leding  wrote:
>
>> Not sure if this matters but the prompt when attempting the “doveadm
>> backup” command shows it to be a “production" server…
>>
>> [root at production1  
>> test.org.com]# doveadm backup -R -u kishore at test.org.com 
>> 
>> remote:vmail at production2.baplc.com 
>> 
>>
>>
>> ...that would seem to me to indicate the old box.  If so, then per
>> Kishore’s earlier posts, the machine where this is being attempted is
>> running 2.0.9…not 2.2.36
>>
>> Maybe nothing but 

Re: Migration from one server to 2 new servers

[Antonio Leding]

Also, FWIW...your doveadm command is missing quite a few options…here is mine…

[Jul-27 @ 15:11:57] > dovecot —version
2.3.10.1 (a3d0e1171)

[Jul-27 @ 15:22:39] > ls -l /usr/bin/doveadm
-rwxr-xr-x. 1 root root 2949584 May 19 02:09 /usr/bin/doveadm

[Jul-27 @ 15:21:31] > doveadm
usage: doveadm [-Dv] [-f ]  []

  altmove  [-u |-A] [-S ] [-r] 
  auth cache|login|lookup|test
  backup   [-u |-A] [-S ] [-fPRU] [-l ] [-r 
] [-m ] [-g ] [-n  | -N] [-x 
] [-s ] [-t ] -d|
  batch[-u |-A] [-S ]   [  
[..]]
  config   [doveconf parameters]
  copy [-u |-A] [-S ]  [user ] 
  deduplicate  [-u |-A] [-S ] [-m] 
  dict get|inc|iter|set|unset
  director add|down|dump|flush|kick|map|move|remove|ring|status|up|update
  dump [-t ] 
  exec  [binary parameters]
  expunge  [-u |-A] [-S ] [-m] 
  fetch[-u |-A] [-S ]  
  flagsadd|remove|replace
  force-resync [-u |-A] [-S ] [-f] 
  fs   copy|delete|get|iter|iter-dirs|metadata|put|stat
  help 
  import   [-u |-A] [-S ] [-U source-user] [-s]   
  index[-u |-A] [-S ] [-q] [-n ] 

  instance list|remove
  kick [-a ] [|]
  log  errors|find|reopen|test
  mailbox  
cache|cache|create|delete|list|metadata|mutf7|path|rename|status|subscribe|unsubscribe|update
  move [-u |-A] [-S ]  [user ] 
  oldstats dump|reset|top
  penalty  [-a ] []
  process  status
  proxykick|list
  purge[-u |-A] [-S ]
  pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-t hash] [-u user] 
[-V]
  rebuild  attachments
  reload
  replicator   add|dsync-status|remove|replicate|status
  save [-u |-A] [-S ] [-m mailbox]
  search   [-u |-A] [-S ] 
  service  status|stop
  sieveactivate|deactivate|delete|get|list|put|rename
  sis  deduplicate|find
  statsdump
  stop
  sync [-u |-A] [-S ] [-1fPRU] [-l ] [-r 
] [-m ] [-g ] [-n  | -N] [-x 
] [-s ] [-t ] -d|
  user [-a ] [-x ] [-f field] [-e 
] [-u]  [...]
  who  [-a ] [-1] [] []
  zlibconnect   []


> On Jul 27, 2020, at 3:18 PM, Antonio Leding  wrote:
> 
> Fair enough but the command snippet I posted was taken directly from your 
> earlier post dated Mon Jul 27 23:11:06 EEST 2020 and it does say 
> “production1”…I just double-checked as well...
> 
> FWIW…the server order in the command you just pasted is the exact reverse 
> from the Jul 27th post I mentioned above…
> 
> Here you appear to be exec’ing the command on prod2 and trying to pull from 
> the remote of prod 1…your earlier post was exec’ing on prod1 and pulling from 
> the remote of prod2…
> 
> 
> 
> 
> 
> 
>> On Jul 27, 2020, at 3:10 PM, Kishore Potnuru > > wrote:
>> 
>> I am executing the command from the new server. I was executing the command 
>> from production2 server only. It has the backup option, but whereas 
>> production1 doesn't have it. Though I am executing from production2, I am 
>> seeing the below error. Is it becasue production1 server doesn't have that 
>> option? Please let me know, if it is confusing.
>> 
>> 
>> The old version is:
>> 
>> [root@production2 ~]# dovecot --version
>> 2.2.36 (1f10bfa63)
>> 
>> 
>> The New version is : 
>> ==
>> [root@production1 ~]# dovecot --version
>> 2.0.9
>> 
>> 
>> I have executed the command from the new server:
>> 
>> 
>> 
>> =
>> [root@production2 test.org.com ]# doveadm backup -R -u 
>> kish...@test.org.com  
>> remote:vm...@production1.baplc.com 
>> 
>> vm...@production1.baplc.com 's password:
>> usage: doveadm [-Dv] [-f ]  []
>> 
>>   altmove  [-u |-A] [-S ] 
>>   auth [-a ] [-x ]  []
>>   config   [doveconf parameters]
>>   director add|flush|map|remove|status
>>   dump [-t ] 
>>   expunge  [-u |-A] [-S ] 
>>   fetch[-u |-A] [-S ]  
>>   force-resync [-u |-A] [-S ] 
>>   help 
>>   import   [-u |-A] [-S ]  
>>  
>>   kick [-a ] [-f] [|]
>>   log  find|reopen|test
>>   mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
>>   penalty  [-a ] []
>>   purge[-u |-A] [-S ]
>>   pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
>>   reload
>>   search   [-u |-A] [-S ] 
>>   sis  deduplicate|find
>>   stop
>>   user [-a ] [-x ]  [...]
>>   who  [-a ] [-1] [] []
>> dsync-local(kish...@test.org.com ): Error: 
>> read(vm...@production1.baplc.com ) 
>> failed: EOF (version not received)
>> dsync-local(kish...@test.org.com ): Error: 
>> Remote command returned error 1: ssh -lvmail production1.baplc.com 
>>  doveadm 

Re: Migration from one server to 2 new servers

[Antonio Leding]

Fair enough but the command snippet I posted was taken directly from your 
earlier post dated Mon Jul 27 23:11:06 EEST 2020 and it does say 
“production1”…I just double-checked as well...

FWIW…the server order in the command you just pasted is the exact reverse from 
the Jul 27th post I mentioned above…

Here you appear to be exec’ing the command on prod2 and trying to pull from the 
remote of prod 1…your earlier post was exec’ing on prod1 and pulling from the 
remote of prod2…






> On Jul 27, 2020, at 3:10 PM, Kishore Potnuru  
> wrote:
> 
> I am executing the command from the new server. I was executing the command 
> from production2 server only. It has the backup option, but whereas 
> production1 doesn't have it. Though I am executing from production2, I am 
> seeing the below error. Is it becasue production1 server doesn't have that 
> option? Please let me know, if it is confusing.
> 
> 
> The old version is:
> 
> [root@production2 ~]# dovecot --version
> 2.2.36 (1f10bfa63)
> 
> 
> The New version is : 
> ==
> [root@production1 ~]# dovecot --version
> 2.0.9
> 
> 
> I have executed the command from the new server:
> 
> 
> 
> =
> [root@production2 test.org.com ]# doveadm backup -R -u 
> kish...@test.org.com  
> remote:vm...@production1.baplc.com 
> 
> vm...@production1.baplc.com 's password:
> usage: doveadm [-Dv] [-f ]  []
> 
>   altmove  [-u |-A] [-S ] 
>   auth [-a ] [-x ]  []
>   config   [doveconf parameters]
>   director add|flush|map|remove|status
>   dump [-t ] 
>   expunge  [-u |-A] [-S ] 
>   fetch[-u |-A] [-S ]  
>   force-resync [-u |-A] [-S ] 
>   help 
>   import   [-u |-A] [-S ]   parent mailbox> 
>   kick [-a ] [-f] [|]
>   log  find|reopen|test
>   mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
>   penalty  [-a ] []
>   purge[-u |-A] [-S ]
>   pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
>   reload
>   search   [-u |-A] [-S ] 
>   sis  deduplicate|find
>   stop
>   user [-a ] [-x ]  [...]
>   who  [-a ] [-1] [] []
> dsync-local(kish...@test.org.com ): Error: 
> read(vm...@production1.baplc.com ) 
> failed: EOF (version not received)
> dsync-local(kish...@test.org.com ): Error: 
> Remote command returned error 1: ssh -lvmail production1.baplc.com 
>  doveadm dsync-server -ukish...@test.org.com 
> 
> 
> [root@production2 test.org.com ]#
> 
> =
> 
> On Mon, Jul 27, 2020 at 10:55 PM Antonio Leding  > wrote:
> Not sure if this matters but the prompt when attempting the “doveadm backup” 
> command shows it to be a “production" server…
> 
> [root at production1  
> test.org.com ]# doveadm backup -R -u kishore at 
> test.org.com 
> remote:vmail at production2.baplc.com 
> 
> 
> ...that would seem to me to indicate the old box.  If so, then per Kishore’s 
> earlier posts, the machine where this is being attempted is running 2.0.9…not 
> 2.2.36
> 
> Maybe nothing but thought I would mention it…
> 
> 
> 
> 
>> On Jul 27, 2020, at 2:50 PM, Sami Ketola > > wrote:
>> 
>> 
>> 
>>> On 28. Jul 2020, at 0.10, Kishore Potnuru >> > wrote:
>>> 
>>> Yes. Please find the details of the servers below. I am executing the 
>>> command from one of the new servers.
>> 
>> I find it very hard to believe this. Shall I look at the version control 
>> when backup was added as option to doveadm?
>> 
>> 2.2.36 has it:
>> 
>> [root@ketola ~]# dovecot --version
>> 2.2.36.8 (0c9d56b41)
>> [root@ketola ~]# doveadm backup
>> doveadm backup [-u |-A] [-S ]  [-fPRU] [-l ] [-r 
>> ] [-m ] [-g ] [-n  | -N] [-x 
>> ] [-s ] [-t ] -d|
>> 
>> 
>> Sami
>> 
>> 
> 

Re: Migration from one server to 2 new servers

[Kishore Potnuru]

I am executing the command from the new server. I was executing the command
from production2 server only. It has the backup option, but whereas
production1 doesn't have it. Though I am executing from production2, I am
seeing the below error. Is it becasue production1 server doesn't have that
option? Please let me know, if it is confusing.


The old version is:

[root@production2 ~]# dovecot --version
2.2.36 (1f10bfa63)


The New version is :
==
[root@production1 ~]# dovecot --version
2.0.9


I have executed the command from the new server:



=
[root@production2 test.org.com]# doveadm backup -R -u kish...@test.org.com
remote:vm...@production1.baplc.com
vm...@production1.baplc.com's password:
usage: doveadm [-Dv] [-f ]  []

  altmove  [-u |-A] [-S ] 
  auth [-a ] [-x ]  []
  config   [doveconf parameters]
  director add|flush|map|remove|status
  dump [-t ] 
  expunge  [-u |-A] [-S ] 
  fetch[-u |-A] [-S ]  
  force-resync [-u |-A] [-S ] 
  help 
  import   [-u |-A] [-S ] 
 
  kick [-a ] [-f] [|]
  log  find|reopen|test
  mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
  penalty  [-a ] []
  purge[-u |-A] [-S ]
  pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
  reload
  search   [-u |-A] [-S ] 
  sis  deduplicate|find
  stop
  user [-a ] [-x ]  [...]
  who  [-a ] [-1] [] []
dsync-local(kish...@test.org.com): Error: read(vm...@production1.baplc.com)
failed: EOF (version not received)
dsync-local(kish...@test.org.com): Error: Remote command returned error 1:
ssh -lvmail production1.baplc.com doveadm dsync-server -
ukish...@test.org.com

[root@production2 test.org.com]#

=

On Mon, Jul 27, 2020 at 10:55 PM Antonio Leding  wrote:

> Not sure if this matters but the prompt when attempting the “doveadm
> backup” command shows it to be a “production" server…
>
> [root at production1  
> test.org.com]# doveadm backup -R -u kishore at test.org.com 
> 
> remote:vmail at production2.baplc.com 
> 
>
>
> ...that would seem to me to indicate the old box.  If so, then per
> Kishore’s earlier posts, the machine where this is being attempted is
> running 2.0.9…not 2.2.36
>
> Maybe nothing but thought I would mention it…
>
>
>
>
> On Jul 27, 2020, at 2:50 PM, Sami Ketola  wrote:
>
>
>
> On 28. Jul 2020, at 0.10, Kishore Potnuru 
> wrote:
>
> Yes. Please find the details of the servers below. I am executing the
> command from one of the new servers.
>
>
> I find it very hard to believe this. Shall I look at the version control
> when backup was added as option to doveadm?
>
> 2.2.36 has it:
>
> [root@ketola ~]# dovecot --version
> 2.2.36.8 (0c9d56b41)
> [root@ketola ~]# doveadm backup
> doveadm backup [-u |-A] [-S ]  [-fPRU] [-l ] [-r
> ] [-m ] [-g ] [-n  | -N] [-x
> ] [-s ] [-t ] -d|
>
>
> Sami
>
>
>
>

Re: Migration from one server to 2 new servers

[Sami Ketola]

> On 28. Jul 2020, at 0.10, Kishore Potnuru  wrote:
> 
> Yes. Please find the details of the servers below. I am executing the command 
> from one of the new servers.

I find it very hard to believe this. Shall I look at the version control when 
backup was added as option to doveadm?

2.2.36 has it:

[root@ketola ~]# dovecot --version
2.2.36.8 (0c9d56b41)
[root@ketola ~]# doveadm backup
doveadm backup [-u |-A] [-S ]  [-fPRU] [-l ] [-r 
] [-m ] [-g ] [-n  | -N] [-x 
] [-s ] [-t ] -d|


Sami

Re: Migration from one server to 2 new servers

[Kishore Potnuru]

Yes. Please find the details of the servers below. I am executing the
command from one of the new servers.


My Current Production Server details:

Linux OS-  Red Hat Enterprise Linux Server release 6.5 (Santiago)
Dovecot version -  2.0.9
Postfix version -  2.6.6


New Servers:
==
Linux OS-  Red Hat Enterprise Linux Server release 7.7 (Maipo)
Dovecot version -  2.2.36 (1f10bfa63)
Postfix version -  2.10.1
==

Thanks & Regards,
Kishore

On Mon, 27 Jul, 2020, 9:43 pm Sami Ketola,  wrote:

>
>
> > On 27. Jul 2020, at 23.11, Kishore Potnuru 
> wrote:
> >
> > Hi ,
> >
> > I have tried the below command from the new server. But I am getting an
> error. Anything is missing here?
> >
>
> Are you sure that is dovecot 2.2.36?
>
> Sami
>
>
>

Re: Migration from one server to 2 new servers

[Sami Ketola]

> On 27. Jul 2020, at 23.11, Kishore Potnuru  wrote:
> 
> Hi ,
> 
> I have tried the below command from the new server. But I am getting an 
> error. Anything is missing here?
> 

Are you sure that is dovecot 2.2.36?

Sami

Re: Migration from one server to 2 new servers

[Kishore Potnuru]

Hi ,

I have tried the below command from the new server. But I am getting an
error. Anything is missing here?


[root@production1 test.org.com]# doveadm backup -R -u kish...@test.org.com
remote:vm...@production2.baplc.com
vm...@production1.baplc.com's password:
usage: doveadm [-Dv] [-f ]  []

  altmove  [-u |-A] [-S ] 
  auth [-a ] [-x ]  []
  config   [doveconf parameters]
  director add|flush|map|remove|status
  dump [-t ] 
  expunge  [-u |-A] [-S ] 
  fetch[-u |-A] [-S ]  
  force-resync [-u |-A] [-S ] 
  help 
  import   [-u |-A] [-S ] 
 
  kick [-a ] [-f] [|]
  log  find|reopen|test
  mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
  penalty  [-a ] []
  purge[-u |-A] [-S ]
  pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
  reload
  search   [-u |-A] [-S ] 
  sis  deduplicate|find
  stop
  user [-a ] [-x ]  [...]
  who  [-a ] [-1] [] []
dsync-local(kish...@test.org.com): Error: read(vm...@production1.baplc.com)
failed: EOF (version not received)
dsync-local(kish...@test.org.com): Error: Remote command returned error 1:
ssh -lvmail production1.baplc.com doveadm dsync-server -
ukish...@test.org.com
[root@production1 test.org.com]#



On Mon, Jul 27, 2020 at 3:08 PM Aki Tuomi 
wrote:

> No, but there is backup option on the new server. That's why the -R, which
> means "backup to here".
>
> Aki
>
> > On 27/07/2020 16:20 Kishore Potnuru  wrote:
> >
> >
> > Hi,
> >
> > But there is no "doveadm backup" option in dovecot 2.0.9 version.
> >
> > [root@production ~]# doveadm -backup
> > doveadm: invalid option -- 'b'
> > [root@production ~]# dovecot --version
> > 2.0.9
> >
> > Copy the contents by using "scp", will that work?
> >
> > Thanks,
> > Kishore Potnuru
> >
> >
> > On Mon, Jul 27, 2020 at 10:00 AM Aki Tuomi 
> wrote:
> > >
> > >  > On 27/07/2020 11:59 Kishore Potnuru 
> 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.
> > >  >
> > >  > My Current Production Server details:
> > >  > 
> > >  > Linux OS - Red Hat Enterprise Linux Server release 6.5 (Santiago)
> > >  > Dovecot version - 2.0.9
> > >  > Postfix version - 2.6.6
> > >  > 
> > >  >
> > >  > New Servers:
> > >  > ==
> > >  > Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo)
> > >  > Dovecot version - 2.2.36 (1f10bfa63)
> > >  > Postfix version - 2.10.1
> > >  > ==
> > >  >
> > >  > 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.
> > >  >
> > >  > 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.
> > >  >
> > >  > 2. copy/migrate the data from old server to new servers. Please
> suggest what is the best way?
> > >  >
> > >  > 3. I see that dovecot version(2.0.9) in old production server, I do
> not know the which is the best option? see the options in the current
> version.
> > >  >
> > >  > =
> > >  > [root@prodcution ~]# doveadm
> > >  > usage: doveadm [-Dv] [-f ]  []
> > >  >
> > >  > altmove [-u |-A] [-S ] 
> > >  > auth [-a ] [-x ]  []
> > >  > config [doveconf parameters]
> > >  > director add|flush|map|remove|status
> > >  > dump [-t ] 
> > >  > expunge [-u |-A] [-S ] 
> > >  > fetch [-u |-A] [-S ]  
> > >  > force-resync [-u |-A] [-S ] 
> > >  > help 
> > >  > import [-u |-A] [-S ] 
>  
> > >  > kick [-a ] [-f] [|]
> > >  > log find|reopen|test
> > >  > mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe
> > >  > penalty [-a ] []
> > >  > purge [-u |-A] [-S ]
> > >  > pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
> > >  > reload
> > >  > search [-u |-A] [-S ] 
> > >  > sis deduplicate|find
> > >  > stop
> > >  > user [-a ] [-x ]  [...]
> > >  >
> > >  > =
> > >  >
> > >  > Please suggest me.
> > >  >
> > >  > Thanks,
> > >  > Kishore Potnuru
> > >
> > >  `doveadm backup -R -u someone imapc:` comes to mind, with master
> password/master user authentication.
> > >
> > >  Aki
> > >
>

Re: Migration from one server to 2 new servers

[Sami Ketola]

Hi,

the idea was to run it on the new server and not on the old server.
That is also why you should use -R parameter to pull the mails from remote, not 
push.

Sami


> On 27. Jul 2020, at 17.13, Kishore Potnuru  wrote:
> 
> 
> 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. 
> 
> [root@production ~]# doveadm backup -u kish...@test.org.com 
>  remote:vm...@production2.test.org.com 
> 
> usage: doveadm [-Dv] [-f ]  []
> 
>   altmove  [-u |-A] [-S ] 
>   auth [-a ] [-x ]  []
>   config   [doveconf parameters]
>   director add|flush|map|remove|status
>   dump [-t ] 
>   expunge  [-u |-A] [-S ] 
>   fetch[-u |-A] [-S ]  
>   force-resync [-u |-A] [-S ] 
>   help 
>   import   [-u |-A] [-S ]   parent mailbox> 
>   kick [-a ] [-f] [|]
>   log  find|reopen|test
>   mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
>   penalty  [-a ] []
>   purge[-u |-A] [-S ]
>   pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
>   reload
>   search   [-u |-A] [-S ] 
>   sis  deduplicate|find
>   stop
>   user [-a ] [-x ]  [...]
>   who  [-a ] [-1] [] []
> 
> 
> On Mon, Jul 27, 2020 at 2:22 PM Admin dishaw.org  
> mailto:ad...@dishaw.org>> wrote:
> 
> 
> > On Jul 27, 2020, at 4:59 AM, Kishore Potnuru  > > 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.
> 
> 

Re: Migration from one server to 2 new servers

[Admin dishaw.org]

> On Jul 27, 2020, at 10:13 AM, Kishore Potnuru  
> wrote:
> 
> 
> 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. 
> 
> [root@production ~]# doveadm backup -u kish...@test.org.com 
>  remote:vm...@production2.test.org.com 
> 

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 Mon, Jul 27, 2020 at 2:22 PM Admin dishaw.org  
> mailto:ad...@dishaw.org>> wrote:
> 
> 
> > On Jul 27, 2020, at 4:59 AM, Kishore Potnuru  > > 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.
> 
> 

Re: Migration from one server to 2 new servers

[Kishore Potnuru]

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.

[root@production ~]# doveadm backup -u kish...@test.org.com
remote:vm...@production2.test.org.com
usage: doveadm [-Dv] [-f ]  []

  altmove  [-u |-A] [-S ] 
  auth [-a ] [-x ]  []
  config   [doveconf parameters]
  director add|flush|map|remove|status
  dump [-t ] 
  expunge  [-u |-A] [-S ] 
  fetch[-u |-A] [-S ]  
  force-resync [-u |-A] [-S ] 
  help 
  import   [-u |-A] [-S ] 
 
  kick [-a ] [-f] [|]
  log  find|reopen|test
  mailbox  create|delete|list|mutf7|rename|status|subscribe|unsubscribe
  penalty  [-a ] []
  purge[-u |-A] [-S ]
  pw   [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
  reload
  search   [-u |-A] [-S ] 
  sis  deduplicate|find
  stop
  user [-a ] [-x ]  [...]
  who  [-a ] [-1] [] []


On Mon, Jul 27, 2020 at 2:22 PM Admin dishaw.org  wrote:

>
>
> > On Jul 27, 2020, at 4:59 AM, Kishore Potnuru 
> 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.
>
>
>

Re: Migration from one server to 2 new servers

[Aki Tuomi]

No, but there is backup option on the new server. That's why the -R, which 
means "backup to here".

Aki

> On 27/07/2020 16:20 Kishore Potnuru  wrote:
> 
> 
> Hi,
> 
> But there is no "doveadm backup" option in dovecot 2.0.9 version.
> 
> [root@production ~]# doveadm -backup
> doveadm: invalid option -- 'b'
> [root@production ~]# dovecot --version
> 2.0.9
> 
> Copy the contents by using "scp", will that work?
> 
> Thanks,
> Kishore Potnuru
> 
> 
> On Mon, Jul 27, 2020 at 10:00 AM Aki Tuomi  wrote:
> > 
> >  > On 27/07/2020 11:59 Kishore Potnuru  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.
> >  > 
> >  > My Current Production Server details:
> >  > 
> >  > Linux OS - Red Hat Enterprise Linux Server release 6.5 (Santiago)
> >  > Dovecot version - 2.0.9
> >  > Postfix version - 2.6.6
> >  > 
> >  > 
> >  > New Servers:
> >  > ==
> >  > Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo)
> >  > Dovecot version - 2.2.36 (1f10bfa63)
> >  > Postfix version - 2.10.1 
> >  > ==
> >  > 
> >  > 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.
> >  > 
> >  > 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.
> >  > 
> >  > 2. copy/migrate the data from old server to new servers. Please suggest 
> > what is the best way?
> >  > 
> >  > 3. I see that dovecot version(2.0.9) in old production server, I do not 
> > know the which is the best option? see the options in the current version.
> >  > 
> >  > =
> >  > [root@prodcution ~]# doveadm
> >  > usage: doveadm [-Dv] [-f ]  []
> >  > 
> >  > altmove [-u |-A] [-S ] 
> >  > auth [-a ] [-x ]  []
> >  > config [doveconf parameters]
> >  > director add|flush|map|remove|status
> >  > dump [-t ] 
> >  > expunge [-u |-A] [-S ] 
> >  > fetch [-u |-A] [-S ]  
> >  > force-resync [-u |-A] [-S ] 
> >  > help 
> >  > import [-u |-A] [-S ]   > parent mailbox> 
> >  > kick [-a ] [-f] [|]
> >  > log find|reopen|test
> >  > mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe
> >  > penalty [-a ] []
> >  > purge [-u |-A] [-S ]
> >  > pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
> >  > reload
> >  > search [-u |-A] [-S ] 
> >  > sis deduplicate|find
> >  > stop
> >  > user [-a ] [-x ]  [...]
> >  > 
> >  > =
> >  > 
> >  > Please suggest me.
> >  > 
> >  > Thanks,
> >  > Kishore Potnuru
> >  
> >  `doveadm backup -R -u someone imapc:` comes to mind, with master 
> > password/master user authentication.
> >  
> >  Aki
> >

Re: Migration from one server to 2 new servers

[Admin dishaw.org]

> On Jul 27, 2020, at 9:20 AM, Kishore Potnuru  
> wrote:
> 
> Hi,
> 
> But there is no "doveadm backup" option in dovecot 2.0.9 version. 
> 
> [root@production ~]# doveadm -backup
> doveadm: invalid option -- 'b'
> [root@production ~]# dovecot --version
> 2.0.9

The command is "doveadm backup”. 

> 
> Copy the contents by using "scp", will that work?
> 

I would recommend against that approach unless you know what you are doing.

> Thanks,
> Kishore Potnuru
> 
> On Mon, Jul 27, 2020 at 10:00 AM Aki Tuomi  > wrote:
> 
> > On 27/07/2020 11:59 Kishore Potnuru  > > 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.
> > 
> > My Current Production Server details:
> > 
> > Linux OS - Red Hat Enterprise Linux Server release 6.5 (Santiago)
> > Dovecot version - 2.0.9
> > Postfix version - 2.6.6
> > 
> > 
> > New Servers:
> > ==
> > Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo)
> > Dovecot version - 2.2.36 (1f10bfa63)
> > Postfix version - 2.10.1 
> > ==
> > 
> > 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.
> > 
> > 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.
> > 
> > 2. copy/migrate the data from old server to new servers. Please suggest 
> > what is the best way?
> > 
> > 3. I see that dovecot version(2.0.9) in old production server, I do not 
> > know the which is the best option? see the options in the current version.
> > 
> > =
> > [root@prodcution ~]# doveadm
> > usage: doveadm [-Dv] [-f ]  []
> > 
> >  altmove [-u |-A] [-S ] 
> >  auth [-a ] [-x ]  []
> >  config [doveconf parameters]
> >  director add|flush|map|remove|status
> >  dump [-t ] 
> >  expunge [-u |-A] [-S ] 
> >  fetch [-u |-A] [-S ]  
> >  force-resync [-u |-A] [-S ] 
> >  help 
> >  import [-u |-A] [-S ]   > parent mailbox> 
> >  kick [-a ] [-f] [|]
> >  log find|reopen|test
> >  mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe
> >  penalty [-a ] []
> >  purge [-u |-A] [-S ]
> >  pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
> >  reload
> >  search [-u |-A] [-S ] 
> >  sis deduplicate|find
> >  stop
> >  user [-a ] [-x ]  [...]
> > 
> > =
> > 
> > Please suggest me.
> > 
> > Thanks,
> > Kishore Potnuru
> 
> `doveadm backup -R -u someone imapc:` comes to mind, with master 
> password/master user authentication.
> 
> Aki

Re: Migration from one server to 2 new servers

[Admin dishaw.org]

> On Jul 27, 2020, at 4:59 AM, Kishore Potnuru  
> 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.

Re: Migration from one server to 2 new servers

[Kishore Potnuru]

Hi,

But there is no "doveadm backup" option in dovecot 2.0.9 version.

[root@production ~]# doveadm -backup
doveadm: invalid option -- 'b'
[root@production ~]# dovecot --version
2.0.9

Copy the contents by using "scp", will that work?

Thanks,
Kishore Potnuru

On Mon, Jul 27, 2020 at 10:00 AM Aki Tuomi 
wrote:

>
> > On 27/07/2020 11:59 Kishore Potnuru  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.
> >
> > My Current Production Server details:
> > 
> > Linux OS - Red Hat Enterprise Linux Server release 6.5 (Santiago)
> > Dovecot version - 2.0.9
> > Postfix version - 2.6.6
> > 
> >
> > New Servers:
> > ==
> > Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo)
> > Dovecot version - 2.2.36 (1f10bfa63)
> > Postfix version - 2.10.1
> > ==
> >
> > 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.
> >
> > 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.
> >
> > 2. copy/migrate the data from old server to new servers. Please suggest
> what is the best way?
> >
> > 3. I see that dovecot version(2.0.9) in old production server, I do not
> know the which is the best option? see the options in the current version.
> >
> > =
> > [root@prodcution ~]# doveadm
> > usage: doveadm [-Dv] [-f ]  []
> >
> >  altmove [-u |-A] [-S ] 
> >  auth [-a ] [-x ]  []
> >  config [doveconf parameters]
> >  director add|flush|map|remove|status
> >  dump [-t ] 
> >  expunge [-u |-A] [-S ] 
> >  fetch [-u |-A] [-S ]  
> >  force-resync [-u |-A] [-S ] 
> >  help 
> >  import [-u |-A] [-S ]   parent mailbox> 
> >  kick [-a ] [-f] [|]
> >  log find|reopen|test
> >  mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe
> >  penalty [-a ] []
> >  purge [-u |-A] [-S ]
> >  pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
> >  reload
> >  search [-u |-A] [-S ] 
> >  sis deduplicate|find
> >  stop
> >  user [-a ] [-x ]  [...]
> >
> > =
> >
> > Please suggest me.
> >
> > Thanks,
> > Kishore Potnuru
>
> `doveadm backup -R -u someone imapc:` comes to mind, with master
> password/master user authentication.
>
> Aki
>

Re: Migration from one server to 2 new servers

[Aki Tuomi]

> On 27/07/2020 11:59 Kishore Potnuru  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.
> 
> My Current Production Server details:
> 
> Linux OS - Red Hat Enterprise Linux Server release 6.5 (Santiago)
> Dovecot version - 2.0.9
> Postfix version - 2.6.6
> 
> 
> New Servers:
> ==
> Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo)
> Dovecot version - 2.2.36 (1f10bfa63)
> Postfix version - 2.10.1 
> ==
> 
> 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.
> 
> 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.
> 
> 2. copy/migrate the data from old server to new servers. Please suggest what 
> is the best way?
> 
> 3. I see that dovecot version(2.0.9) in old production server, I do not know 
> the which is the best option? see the options in the current version.
> 
> =
> [root@prodcution ~]# doveadm
> usage: doveadm [-Dv] [-f ]  []
> 
>  altmove [-u |-A] [-S ] 
>  auth [-a ] [-x ]  []
>  config [doveconf parameters]
>  director add|flush|map|remove|status
>  dump [-t ] 
>  expunge [-u |-A] [-S ] 
>  fetch [-u |-A] [-S ]  
>  force-resync [-u |-A] [-S ] 
>  help 
>  import [-u |-A] [-S ]   mailbox> 
>  kick [-a ] [-f] [|]
>  log find|reopen|test
>  mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe
>  penalty [-a ] []
>  purge [-u |-A] [-S ]
>  pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V]
>  reload
>  search [-u |-A] [-S ] 
>  sis deduplicate|find
>  stop
>  user [-a ] [-x ]  [...]
> 
> =
> 
> Please suggest me.
> 
> Thanks,
> Kishore Potnuru

`doveadm backup -R -u someone imapc:` comes to mind, with master 
password/master user authentication.

Aki