competition

[Simon Matter]

> On Wednesday 22 September 2010 15:29:20 Kenneth Marshall wrote:
>> On Wed, Sep 22, 2010 at 10:48:49PM +0930, Daniel O'Connor wrote:
>> > On 22/09/2010, at 22:33, Kenneth Marshall wrote:
>> > >> On a bad shutdown it requires admin intervention very frequently
>> which
>> > >> is pretty tedious.
>> > >>
>> > >> And yes, upgrading it is also a PITA.
>> > >
>> > > That is why we moved to skiplist. The server would require manual
>> > > intervention to even restart after certain types of system events.
>> > > It is hard to explain why mail was unavailable for 30+mins. when
>> > > the server rebooted in 2mins. BDB would need to be much, much
>> > > easier to manage and be more robust for us to use.
>> >
>> > Yep, I plan to migrate to skiplist some day :)
>> >
>> > Now if only I could use skiplist with openldap ;)
>>
>> Sadly, OpenLDAP does need the performance of BDB.
>
> With current "LDIF" exports of OpenLDAP, the downtime caused by a corrupt
> BDB
> database is "acceptable".
>
> Is a similar method possible with cyrus?
> Eg. a simple command that exports all BDB-database-files to a simple
> format
> that can easily be re-imported into Cyrus when the DBD is corrupted?

That's exactly what our RPM does. It converts all BDB databases to
skiplist on shutdown. On startup, it detects the format of all database
files and converts it back to what is configured if needed.

As Bron told us, with 2.4 the magic on startup is done inside Cyrus. My
question remains, why can't we get rid of BDB completely?

Simon