Jukka Salmi --> info-cyrus (2010-06-25 02:30:49 +0200):
> Hi
>
> I'm currently running Cyrus IMAPd 2.2.13p1 on NetBSD/i386 without any
> problems. During the next few days I need to move the users' mailboxes
> to a NetBSD/amd64 system which will run Cyrus IMAPd 2.3.16. Some hints
> about this wo
On Fri, 25 Jun 2010, Jukka Salmi wrote:
> Since I can afford some hours of mail system downtime I'd prefer to copy
> over a compressed archive containing all the mailboxes, extract it on
> the new system and recursively run reconstruct(8) for all mailboxes;
> then I'd probably copy over the content
On 06/26/2010 11:38 AM, Jukka Salmi wrote:
> Patrick Boutilier --> info-cyrus (2010-06-24 22:16:47 -0300):
>> How much data do you have to move?
>
> It's not that much, about 2--3 GiB, but my upstream is only 640 kbit/s,
> thus copying would take at least 8 hours or so...
What I did before my big
Patrick Boutilier --> info-cyrus (2010-06-24 22:16:47 -0300):
> How much data do you have to move?
It's not that much, about 2--3 GiB, but my upstream is only 640 kbit/s,
thus copying would take at least 8 hours or so...
> > Some basic questions:
> >
> > - Is Cyrus on amd64 able to read skiplist
Hi,
Gary Smith --> info-cyrus (2010-06-24 17:50:40 -0700):
> YMMV, but here is what I have done in the past. From the destination,
> I rsync the source to get the bulk of the files over. Granted, this
> isn't a working copy when you're finished but it will cut down on the
> copy time. Then I sh
On 06/24/2010 09:30 PM, Jukka Salmi wrote:
> Hi
>
> I'm currently running Cyrus IMAPd 2.2.13p1 on NetBSD/i386 without any
> problems. During the next few days I need to move the users' mailboxes
> to a NetBSD/amd64 system which will run Cyrus IMAPd 2.3.16. Some hints
> about this would be appreci
> I'm currently running Cyrus IMAPd 2.2.13p1 on NetBSD/i386 without any
> problems. During the next few days I need to move the users' mailboxes
> to a NetBSD/amd64 system which will run Cyrus IMAPd 2.3.16. Some hints
> about this would be appreciated.
>
> The cleanest way would probably be to
