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?

Regards,
Suresh

On Mon, Jan 6, 2025 at 6:36 PM Quanah Gibson-Mount <quanah@fast-mail.org> wrote:

--On Monday, January 6, 2025 10:33 AM -0500 Suresh Veliveli
<Suresh.Veliveli@georgetown.edu> wrote:

>
> We just had another instance like this. Any suggestions?
>
>
> Thanks,
> Suresh
>
>
> On Fri, Jan 3, 2025 at 4:52 PM Suresh Veliveli
> <Suresh.Veliveli@georgetown.edu> wrote:
>
>
>
> 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.

What backend were you using on 2.6.3 before migrating to mdb? At this
point, I'd suspect your migration may not have been executed correctly.

--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)