[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: MDB data replication issues

Thanks Bastian for your response.

But I want to clear that I don't use slapadd while slapd is running. I have LDIF data which needs to be imported in the new Multimaster servers. That's why I used slapadd.
When I did the import (slapadd) with the big data, it doesn't get replicated. To check the problems I did the import with single entry only.

First I stop both the servers, do slapadd on Master server and then I start the Master server & replica server.
After doing all this too, the data is not getting replicated.

I did the same things with BDB backend in openLDAP 2.4.40.  It works just fine.
Can you please let me know what I've been doing wrong.

Br
Gurjot Kaur

-----Original Message-----
From: Bastian Tweddell [mailto:b.tweddell@fz-juelich.de]
Sent: Monday, June 27, 2016 6:22 PM
To: Gurjot Kaur <gurjot.kaur@aricent.com>
Cc: openldap-technical@openldap.org
Subject: Re: MDB data replication issues

On 27Jun16 11:32+0000, Gurjot Kaur wrote:
> When an LDIF entry is imported using slapadd, it doesn't get replicated in the replica server at all.
> Below is the ldapsearch result om Master server:

Do you use slapadd while slapd is running?

IIRC, slapadd is just for one thing: restore backup. For that reason,
the DB is offline (slapd not running). After successful restore, I start
slapd and syncrepl works as expected.

If you use slapadd on an online DB, I could imagine that the
syncrepl-overlay does not realize that there is a new entry and thus it
does not replicate it.

For daily-business modifications to the LDAP DB I always use ldap*
commands.


Cheers,
--
Bastian Tweddell               Juelich Supercomputing Centre
phone: +49 (2461) 61-6586          HPC in Neuroscience
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."