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 contents of $configdirectory/user/ and
> start Cyrus IMAPd. Does this make sense? And what data will I be
> missing? ;-)
>
> Some basic questions:
>
> - Is Cyrus on amd64 able to read skiplist files created by Cyrus on
> i386? (If not, I'd probably have to use cvt_cyrusdb(8) to dump and
> restore the relevant files.)
Yes, it is. Heck, it managed to read (and upgrade in-place, I suppose)
skiplist files from Cyrus 2.1 just fine...
> - What about the cyrus.{cache,header,index,squat} files? Can I expect
> Cyrus on amd64 to be able to read them just fine? (This seems not to
> be that important since those files are easily recreated IIUC.)
Yes, if they're skiplist. I wouldn't trust that to work if it is berkeley
DB.
Be careful with the mailbox list, though. Better dump it to the portable
text file format, update any missing ACL rights, and restore it in the new
box.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
----
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
