Exporting/Importing LDAP in Zimbra 6

[jterhune]

From the looks of things, the documentation for exporting and importing ldap in 5.x seems to be deprecated in 6: Exporting and Importing Zimbra LDAP Data » Zimbra :: Blog

From poking around, it looks like ldap information is now stored in /opt/zimbra/dada/ldap. I cannot figure out, though, how to do an import since slapd.conf no longer exists.

Zimbra Server » Zimbra :: Blog makes it sound like slapd.conf is gone in favor of cn=config:

OpenLDAP now allows for some on-the-fly configuration changes with zmlocalconfig via a cn=config backend instead of slapd.conf text files for preservation across upgrades.

I have no idea how to run slapadd anymore as it needs a slapd.conf file. Does anyone know how I can do an ldap import with the new cn=config system?

[jterhune]

Also, (completely guessing with the syntax) running:

slapd -q -b "" -F /opt/zimbra/data/ldap/cn\=config -cv -l ldap.bak

results in:

slapadd: slap_init no backend for ""

[ewebzone]

Originally Posted by jterhune

From the looks of things, the documentation for exporting and importing ldap in 5.x seems to be deprecated in 6: Exporting and Importing Zimbra LDAP Data » Zimbra :: Blog

From poking around, it looks like ldap information is now stored in /opt/zimbra/dada/ldap. I cannot figure out, though, how to do an import since slapd.conf no longer exists.

Zimbra Server » Zimbra :: Blog makes it sound like slapd.conf is gone in favor of cn=config:

I have no idea how to run slapadd anymore as it needs a slapd.conf file. Does anyone know how I can do an ldap import with the new cn=config system?

Are we alone here? As I see it, with this bug, there is no possible LDAP import from a full backup? It consistently gives errors about not being able to find ldap.conf, which doesn't even exist in v6 installs.

How can one do a complete migration, when they can't import the LDAP details (accounts, domains, distro lists). This info isn't created during standard mailbox restores -- leaving your shared calendars/tasks/etc useless.

How could this go overlooked?

[Ced91]

The wiki is not working for me too.
I have to replace a server in 5 days....
So I must retrofit to 32 bits on the new server. thank you.
This version of zimbra is causing many problem; I've post another thing for Outlook connector... What the next? Is it really tested?

[quanah]

Have you looked at the zmslapcat script? You can trivially derive how to slapadd from it. Also, if you parse zmupgrade.pm, it has an example of doing a slapadd with 6.0.

[Ced91]

Hi,

You can take a look at my others posts in the migration section and Outlook connector section.
Since you are a Zimbra employee, you have to give a right and sure way to perform the migration of Zimbra in your different supported OS platform.
This is not the case today with the 6.01 version of Zimbra and this cause many problem for the people who are with client's relation.

If we give some answer to ours clients when reading the WIKI and these are not working in real, we are degrading the image of Zimbra and us...

So for now, I don't have time and knowledge to develop and test a script.

I have an OLD hardware with Ubuntu 6.06/Zimbra 6.01 to replace with a new with Ubuntu 8.04. 32 bits or 64 bits (?) / Zimbra 6.01.
Actually no way to do that...
What's your best method and WIKI? For LDAP, to restore/move all the data?

Regards,

[quanah]

Wouldn't this be a lot similar to:
http://wiki.zimbra.com/index.php?title=32_bit

? Which has the 6.0 specific instructions.

[Ced91]

This WIKI has been modified today! After my post and test of this Week-End.
I will give a try and inform you.
Note: I have a ticket open to the support.
Regards.

[Ced91]

I have imported successfuly LDAP database. Thanks.

I will inform you for the next steps of migration Friday: MySQL import, Store and index import.

The WIKI is not clear enough:
- For the passwords of localconfig to modify since these parameters below are not indicated to import:
ldap_replication_password,
zimbra_logger_mysql_password,
mailboxd_keystore_password,
mailboxd_truststore_password,
ldap_nginx_password,
mailboxd_keystore_base_password,
What are we doing for these parameters, modify or not?

- through the 5 point: Certificates.
Is it only to perform if commercials certificates are installed or all the keystore files and certificates must be copied?

Thanks to clarify,

Regards,

[quanah]

I've updated the wiki to address the password keys that you note, and you must update the certificates regardless if they are self-signed or commercial.