Re: Using xfer to migrate mailboxes to a new server

2010-02-18 Thread nodens2099
On 18/02/2010 13:08, J. Roeleveld wrote: > On Thursday 18 February 2010 12:31:02 Reinaldo de Carvalho wrote: >> On Thu, Feb 18, 2010 at 7:40 AM, Per-Olov Sjöholm wrote: >>> It's resonalbe fast >>> The bad thing is that you need all passwords. >> >> No, use cyrus global admin. > > Won't that kill t

Re: Using xfer to migrate mailboxes to a new server

2010-02-18 Thread J. Roeleveld
On Thursday 18 February 2010 12:31:02 Reinaldo de Carvalho wrote: > On Thu, Feb 18, 2010 at 7:40 AM, Per-Olov Sjöholm wrote: > > It's resonalbe fast > > The bad thing is that you need all passwords. > > No, use cyrus global admin. Won't that kill the "seen" database? Cyrus Home Page: http:/

Re: Using xfer to migrate mailboxes to a new server

2010-02-18 Thread Reinaldo de Carvalho
On Thu, Feb 18, 2010 at 7:40 AM, Per-Olov Sjöholm wrote: > It's resonalbe fast > The bad thing is that you need all passwords. No, use cyrus global admin. > So this is not an ideal solution, but for sure it works great when you don't > have all the time you would like to dig for a better solutio

Re: Using xfer to migrate mailboxes to a new server

2010-02-18 Thread Per-Olov Sjöholm
On 15 feb 2010, at 15.59, Elver Loho wrote: > On 15 February 2010 16:21, Kevin Kobb wrote: >> The last time we moved to new hardware, I used imapsync to migrate all >> the mailboxes to the new hardware. We moved from a different IMAP server >> to Cyrus, and this worked great. I don't know if thi

Re: Using xfer to migrate mailboxes to a new server

2010-02-16 Thread Wesley Craig
On 16 Feb 2010, at 06:35, Simon Fraser wrote: > On Tue, 2010-02-16 at 11:29 +, David Mayo wrote: >> Some additional things to look out for: >> >> - You must run this command on the existing back-end This is true, but I'm not 100% positive why it's implemented this way. The (trivial) bit of

Re: Using xfer to migrate mailboxes to a new server

2010-02-16 Thread Simon Fraser
On Tue, 2010-02-16 at 11:29 +, David Mayo wrote: > >> localhost.localdomain> xfer user.elver 192.168.0.180 > >> xfermailbox: Server(s) unavailable to complete operation > > > > There should be a bit more information in the log, too. While debugging > > the authentication and permissions I fou

Re: Using xfer to migrate mailboxes to a new server

2010-02-16 Thread David Mayo
Hi all, We are in the process of moving our mailboxes from a Cyrus 2.2 server to a Cyrus 2.3 server. I have several comments regarding this which I was planning to share with the list - so this seems an opportune moment. Simon Fraser wrote: > On Mon, 2010-02-15 at 15:25 +0200, Elver Loho wrote

Re: Using xfer to migrate mailboxes to a new server

2010-02-15 Thread Elver Loho
On 15 February 2010 16:21, Kevin Kobb wrote: > The last time we moved to new hardware, I used imapsync to migrate all > the mailboxes to the new hardware. We moved from a different IMAP server > to Cyrus, and this worked great. I don't know if this work as well now > moving from Cyrus to Cyrus, as

Re: Using xfer to migrate mailboxes to a new server

2010-02-15 Thread Elver Loho
On 15 February 2010 16:05, Simon Fraser wrote: > On Mon, 2010-02-15 at 15:25 +0200, Elver Loho wrote: > >> localhost.localdomain> xfer user.elver 192.168.0.180 >> xfermailbox: Server(s) unavailable to complete operation > > There should be a bit more information in the log, too. While debugging >

Re: Using xfer to migrate mailboxes to a new server

2010-02-15 Thread Kevin Kobb
On 2/15/2010 8:25 AM, Elver Loho wrote: > Hi, > > We've got Cyrus running fine on our old server since 2006. Now we're > setting up a new server and would like to migrate all the mailboxes > over to the new one before replacing the old server. For this task the > "xfer" command seems relevant. > >

Re: Using xfer to migrate mailboxes to a new server

2010-02-15 Thread Simon Fraser
On Mon, 2010-02-15 at 15:25 +0200, Elver Loho wrote: > localhost.localdomain> xfer user.elver 192.168.0.180 > xfermailbox: Server(s) unavailable to complete operation There should be a bit more information in the log, too. While debugging the authentication and permissions I found the error messa