[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: upgrading from 2.0 to 2.1


You can keep your existing slapd.conf and replication configuration for 
OpenLDAP 2.1.x provided you keep using the LDBM backend. Upgrading should not 
give much trouble if you realise that OpenLDAP 2.1.x is more strict on schema 
checking (structural/auxiliary object classes etc.). Also keep in mind that 
replicating from an OpenLDAP 2.0.x server to an OpenLDAP 2.1.x server is not 
The BDB backend brings very usefull improvements, but is quite different from 
the LDBM backend. For example using the BDB backend might also require 
changes to your backup & restore implementation. Also tuning the BDB backend 
(Berkeley DB cachesizes, checkpoint intervals etc.) requires some research 
and proper testing. Make sure you've done that research en testing before you 
move from LDBM to BDB on your production systems.



On Friday 27 June 2003 22:27, Allan Streib wrote:
> Planning to tackle an upgrade from 2.0.27 to the latest 2.1 release, and
> wondering if there are any guidlines out there other than the FAQ-o-Matic
> which has sparse info on this topic.  I understand I'll need to dump/load
> the data itself, but should my slapd.conf and replication configurations
> work unchanged?  Should I upgrade slapd and stay with ldbm as I'm
> currently doing, or is it "safe" to switch to the bdb backend at the same
> time.  Many thanks for info.
> Allan