Hi, we have had the RHEL4 32bit OSS zimbra running in an OpenVZ container sucessfully for the last four years, and I've just migrated the virtual machine to a new server. Unfortunately I think there may have been some corruption in transit as zimbra fails to startup with the following repeated in the zimbra.log

Code:
Nov 18 20:03:33 mail slapd[8250]: bdb(): file id2entry.bdb has LSN 20/7544382, past end of log at 20/7535686
Nov 18 20:03:33 mail slapd[8250]: bdb(): Commonly caused by moving a database from one database environment
Nov 18 20:03:33 mail slapd[8250]: bdb(): to another without clearing the database LSNs, or by removing all of
Nov 18 20:03:33 mail slapd[8250]: bdb(): the log files from a database environment
Nov 18 20:03:33 mail slapd[8250]: bdb(): /opt/zimbra/data/ldap/hdb/db/id2entry.bdb: unexpected file type or format
Nov 18 20:03:33 mail slapd[8250]: hdb_db_open: database "": db_open(/opt/zimbra/data/ldap/hdb/db/id2entry.bdb) failed: Invalid argument (22).
Nov 18 20:03:33 mail slapd[8250]: backend_startup_one (type=hdb, suffix=""): bi_db_open failed! (22)
Nov 18 20:03:33 mail slapd[8250]: bdb_db_close: database "": alock_close failed
Nov 18 20:03:33 mail slapd[8250]: slapd stopped.
I've looked at a few related posts:
http://www.zimbra.com/forums/adminis...-solution.html
http://www.zimbra.com/forums/install...n-t-start.html

and the reccommended next step is to run db_recover, however I just want to check if there are any differences in Zimbra 6.x as these posts are several years old. For example I can't find db_recover in the sleepycat directory it is now in the jetty directory.

Any advice you can give is appreciated, I don't mind trying a few things as if I hose the install I can recover the VM and try something else.

I have a week old backup of the VM that I can use as a last resort but bringing over this weeks mail is something I would rather avoid.