Bron Gondwana wrote:
> On Sat, Oct 09, 2010 at 08:23:15AM -0400, Michael D. Sofka wrote:
>> Great. One final question on this topic.
>>
>> I currently have a warm-backup server (2.2.12) that I rsync to each
>> night. As mailboxes are moved to the new 2.3.16 server the rsynced
>> index files would
On 09 Oct 2010, at 23:12, Bron Gondwana wrote:
> Oh yeah - you're right. That's missing in 2.4 and I think it's because I
> planned to replace it with replication stuff which uses the append logic
> which does that on the fly. But I haven't done it yet. Would make sense
> to add that back, at le
On Sat, Oct 09, 2010 at 10:24:41PM -0400, Wesley Craig wrote:
> On 09 Oct 2010, at 20:31, Bron Gondwana wrote:
> > Yes, file mtimes get set to INTERNALDATE as much as possible (and vice
> > versa when reconstructing with a missing index - hence the reason for
> > doing it)
>
> Perhaps you're misun
On 09 Oct 2010, at 20:31, Bron Gondwana wrote:
> Yes, file mtimes get set to INTERNALDATE as much as possible (and vice
> versa when reconstructing with a missing index - hence the reason for
> doing it)
Perhaps you're misunderstanding me... In 2.3.recent, the second to last step of
undump (xfer)
On Sat, Oct 09, 2010 at 07:30:36AM -0400, Wesley Craig wrote:
> On 09 Oct 2010, at 00:04, Michael D. Sofka wrote:
> > Is the old format updated on xfer?
>
> It is updated on xfer -- when the mtimes of the message files are set to the
> INTERNALDATE.
Yes, file mtimes get set to INTERNALDATE as mu
On Sat, Oct 09, 2010 at 08:23:15AM -0400, Michael D. Sofka wrote:
> Great. One final question on this topic.
>
> I currently have a warm-backup server (2.2.12) that I rsync to each night. As
> mailboxes are moved to the new 2.3.16 server the rsynced index files would be
> the wrong version.
>
On Sat, Oct 09, 2010 at 09:59:44AM -0500, Patrick Goetz wrote:
> On 10/9/2010 7:23 AM, Michael D. Sofka wrote:
> >
> > I can either rsync just the mail messages to the warm backup, and then
> > reconstruct the index files. Or, I can take a slight detour, and upgrade
> > the warm backup server to
Imapsync with the proxy user is a third option during migration. I tested
imapsync previously and it worked. But rsync was much faster.
As to index consistency, I run the backups from an lvm snapshot.
Mike
"Simon Matter" wrote:
>> On 10/9/2010 7:23 AM, Michael D. Sofka wrote:
>>>
>>> I can
> On 10/9/2010 7:23 AM, Michael D. Sofka wrote:
>>
>> I can either rsync just the mail messages to the warm backup, and then
>> reconstruct the index files. Or, I can take a slight detour, and upgrade
>> the warm backup server to 2.3.16.
>>
>
> This is something I've been wondering, too. The probl
On 10/9/2010 7:23 AM, Michael D. Sofka wrote:
>
> I can either rsync just the mail messages to the warm backup, and then
> reconstruct the index files. Or, I can take a slight detour, and upgrade the
> warm backup server to 2.3.16.
>
This is something I've been wondering, too. The problem with
Great. One final question on this topic.
I currently have a warm-backup server (2.2.12) that I rsync to each night. As
mailboxes are moved to the new 2.3.16 server the rsynced index files would be
the wrong version.
I can either rsync just the mail messages to the warm backup, and then
recons
On 09 Oct 2010, at 00:04, Michael D. Sofka wrote:
> Is the old format updated on xfer?
It is updated on xfer -- when the mtimes of the message files are set to the
INTERNALDATE.
:wes
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cy
On Sat, Oct 09, 2010 at 12:04:23AM -0400, Michael D. Sofka wrote:
> Bron, Thanks for the answer. A one way xfer in fine. I'm just testing the
> new server, and the migration process.
>
> Is the old format updated on xfer? The account I moved is working fine.
Cyrus will automatically update th
Bron, Thanks for the answer. A one way xfer in fine. I'm just testing the
new server, and the migration process.
Is the old format updated on xfer? The account I moved is working fine.
Mike
"Bron Gondwana" wrote:
>On Fri, Oct 08, 2010 at 02:40:01PM -0400, Michael D. Sofka wrote:
>> But, wh
On Fri, Oct 08, 2010 at 02:40:01PM -0400, Michael D. Sofka wrote:
> But, when I try to move it back to the 2.2.12 back-end the same error
> message.
>
> Is this a cyrus version incompatibility? That is, are the moves
> one-way, at least when using xfer?
Gosh yes. The mailbox internal format h
process I had neglected to set: hashimapspool: true
No problem, I'll just move the maiboxes back. This failed with:
service imap pid nnn in BUSY state: terminated abnormally
on the 2.3.16 server. So, I shutdown cyrus, added the hashimapspool
option, moved the mail files and metadata
16 matches
Mail list logo
