- Previous message: Mark Edwards: "Re: migrating to a different db"
- Maybe in reply to: Ken Murchison: "Re: migrating to a different db"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
|
|
|
From: Andrew Morgan (no email)
Date: Mon May 01 2006 - 16:39:36 EDT
On Mon, 1 May 2006, Mark Edwards wrote:
> On May 1, 2006, at 8:32 AM, Andrew Morgan wrote:
>
>> On Sun, 30 Apr 2006, Mark Edwards wrote:
>>
>>> Can someone tell me what the repercussions of rebuilding cyrus with a
>>> different db, say db43 instead of db41, and starting the new one up with
>>> the same data and configuration? Will it run? Will there be data
>>> corruption of any kind?
>>
>> The safest and most reliable way to perform that upgrade is to use
>> cvt_cyrusdb to convert your databases to plaintext using the old binaries.
>> Then upgrade the software and use cvt_cyrusdb again to convert back into
>> berkeley DB.
>
> Can I assume that only files with a .db extension are in BDB format, or might
> other files be as well, such as .seen .sub or .index?
The format of the various Cyrus backends is defined at compile time in
older versions (2.1.x and older) and at run time in the imapd.conf file
for newer versions (2.2.x and newer).
Andy
---- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
|
|
|