Thanks for the info. The man page for cyr_dbtool doesn't indicate this is possible (which is not to say it isn't possible, just undocumented). cvt_cyrusdb appears to be more of a candidate. Is this what I should be using, or could you give an example of how to use cyr_dbtool? Many thanks, Chris Bron Gondwana wrote: > On Wed, Sep 26, 2007 at 11:46:08AM -0500, Chris Harms wrote: > >> Hello, >> >> We will be migrating our cyrus server from x86 to x86_64 for an interim >> period and then likely returning to x86 after some time. We will be >> upgrading from 2.2.x to 2.3.x as well, and I am wondering if there is a >> way to preserve the per mailbox databases, specifically the seen state? >> I have run through a test of this process once without luck retaining >> the information. Is there a way to do this moving to x86_64 and then >> >> likewise moving back to x86? >> > > You can always dump and restore the seen state using cyr_dbtool, though > that's a fair bit of work! Amazing how much isn't hard work once you > have a tested script to do it for you though :)[0] > > There are also a couple of fields (e.g. QUOTA information, MODSEQ) in > the cyrus.index file which if you've got values higher than 2^32 in them > will change value when you switch back to 32 bit. > > Bron. > > [0] and it looks like you've actually tested that your process will work > before committing to it, which puts you ahead of 90% of the IT shops > out there! > ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
