[SOLVED] Restoring ldap.bak

[Orangeruffy]

I'm having some trouble with my latest snapshot VM of my Zimbra server. Everything appears to be working except I can not authenticate in the admin console or as a user web or IMAP.

I have an older snapshot which I have upgraded to the same version - 6.0.9 and it allows me to auth fine. I have taken a backup of the ldap db.

I tried following the instructions here:

Exporting and Importing Zimbra LDAP Data » Zimbra :: Blog

but on the final import command I get the following errors for every entry:

slapadd: could not add entry dn="uid=info,ou=people,dc=domain,dc=co,dc=nz" (line=1961): id2entry_add failed: DB_KEYEXIST: Key/data pair already exists (-30995)

I am running the command:

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

Can anyone provide me with the correct instructions for preparing an restoring the LDAP db on version 6.0.9 please?

Any assistance would be greatly appreciated.

Thanks
Andy

[bdial]

did you delete the existing ldap database first?

[Orangeruffy]

I thought I had but I can't be sure, I'm fairly green on the LDAP side of things. What files should I be deleting to be sure?

I tried removing all the files in: /opt/zimbra/openldap/var/openldap-data/ but this does not seam to have worked so I tried putting DB_CONFIG back but still no change I am still getting the same errors.

Are you able to tell me which directory I should be deleting?

[king0770]

Before importing the ldap data on a 6.0.x, you will need to move the old hdb directories out of the way.

1) ldap stop

2) mv /opt/zimbra/data/ldap/hdb /opt/zimbra/data/ldap/OLD.hdb

3) mkdir /opt/zimbra/data/ldap/hdb

4) mkdir /opt/zimbra/data/ldap/hdb/db

5) mkdir /opt/zimbra/data/ldap/hdb/logs

6) cp /opt/zimbra/data/ldap/OLD.hdb/db/DB_CONFIG /opt/zimbra/data/ldap/hdb/db/DB_CONFIG

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

8) ldap start

[Orangeruffy]

Thanks for everybodies help. It turns out the issue I was having was the result of an IPv6 line being added to the hosts file after a Fedora update. Looks like this was preventing Zimbra from starting and all I in fact needed to do was remove this line.

Always easy when you know how