disaster recovery help: lost ldap db to fs corruption

[wryfi]

I went to reboot my server today, and all hell broke loose. A kernel panic during shutdown, and a power cycle later, I find myself with serious filesystem corruption.

I appear to have lost the LDAP database for zimbra, among other things. I do not have a recent backup. I really only care about recovering emails in the store (which appears to be mostly intact).

How can I go about dissecting the message store? Is there any way to reasonably get my mail back????

[wryfi]

Specifically, when trying to start zimbra, I get ...

sudo /etc/init.d/zimbra start
Host z.wryfi.net
Starting ldap...Done.
Failed.
Failed to start slapd. Attempting debug start to determine error.
hdb_db_open: database "": db_open(/opt/zimbra/data/ldap/hdb/db/id2entry.bdb) failed: Invalid argument (22).
backend_startup_one (type=hdb, suffix=""): bi_db_open failed! (22)
bdb_db_close: database "": alock_close failed

[wryfi]

I have now run db_recover and I still get the same error with id2entry.bdb.

I am now trying to follow instructions from [SOLVED] LDAP / slapd - Database environment corrupt (Issue & Solution).

I do not, however, seem to have a /opt/zimvbra/conf/slapd.conf file. There is some kind of default file in /opt/zimbra/openldap-2.4.23.2z/etc/openldap/slapd.conf, but when I try ~/openldap/sbin/slapadd -w -q -f ~/openldap-2.4.23.2z/etc/openldap/slapd.conf -l ../ldap.bak, I get:

Unrecognized database type (bdb)
/opt/zimbra/openldap-2.4.23.2z/etc/openldap/slapd.conf: line 53: <database> failed init (bdb)
slapadd: bad configuration file!

I suspect the missing ~/conf/slapd.conf is a problem. How can I recreate this file?

[wryfi]

Ok, so of course openldap-2.4.23 uses cn=config, duh ... running this command worked:

/opt/zimbra/openldap/sbin/slapadd -q -b "" -F /opt/zimbra/data/ldap/config -cv -l /tmp/ldap.bak

Now my ldap is back up and running. It remains to be seen what messages might have been lost. No more delaying on that backup plan!