Hi Quanah,

You are correct. I misspoke. We ran "bdb" in OpenLDAP: slapd 2.4.50 (Aug 6 2020 11:11:46). We switched to "mdb" when we went from 2.4.50 to 2.6.x version. The upgrade path, as mentioned, was a clean install of 2.6.x and export of db (slapcat) and import(slapadd).

Regards,

Suresh

On Fri, Jan 17, 2025 at 12:48 PM Quanah Gibson-Mount <quanah@fast-mail.org> wrote:

--On Monday, January 6, 2025 6:47 PM -0500 Suresh Veliveli
<Suresh.Veliveli@georgetown.edu> wrote:

>
> It was "bdb". For migration, we did a clean install, used "slapcat" to
> export the db and "slapadd" to import. We used this procedure a
> number of times in the past when we switched OS, for upgrades etc. Do
> you have a recommended procedure in mind?

>> We did an upgrade from 2.6.3 to 2.6.7 at the same time, changing the
>> backend db to "mdb". I think that's when we started to notice that
>> consumer replication is not recovering. So we upgraded again to 2.6.8 to
>> now 2.6.9.

There was no bdb backend in the 2.6 series. It was removed after the 2.4
series, so the upgrade route you describe is not feasible.

--Quanah

Suresh Veliveli

Sr. UNIX Systems Engineer

Georgetown University

University Information Services | Security Infrastructure and Policy-Identity and Collaboration

202-262-6676 (cell) | 202-687-3108 (work)