Ciao, Michael

I understood the risks but how can I resolve my issue? My case I want to upgrade all servers step by step without lost data on = secondary LDAP servers

For now when I add the new attribute to some item in LDAP then this item = lost on secondary servers. Moreover, replication stops after receiving the first item with unknown = data. So, I will lose not only one changed item and also all next

I have a few hundred of LDAPs servers which should be updated one-by-one = and in this case, I will lose the data until upgrade all of them

Thank you in advance. Best regards, Alex

On Jul 23, 2019, at 12:52, Michael Str=C3=B6der michael@stroeder.com =

wrote:

=20 On 7/23/19 9:10 AM, alex.soloviov@wildix.com wrote:

...

Actually, I have the configuration with several LDAP server without =

this =3D

...

problem. But the version of these LDAPs is a bit less - 2.4.31.=3D20 On this installation when I changed the schema on the main server, on =

=3D

...

secondary I see fully replicated data and warnings about unknown =3D attributes like: 5d36b192 UNKNOWN attributeDescription "TESTTYPE" inserted.

=20 Mainly running a replication setup without consistent schema on all =

replicas is asking for trouble. It may work in some niche cases. But in = most cases it will fail miserably.

=20 =3D> Fix your setup. =20 Ciao, Michael. =20