[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Keeping a new n-master environment in sync with an old single master env during a migration
- To: Chris Cardone <ccardone@squaretrade.com>, openldap-technical@openldap.org
- Subject: Re: Keeping a new n-master environment in sync with an old single master env during a migration
- From: Quanah Gibson-Mount <quanah@symas.com>
- Date: Thu, 02 Aug 2018 10:19:37 -0700
- Content-disposition: inline
- In-reply-to: <CADr0+sc4a1G5eq-HQr3k=pJiQDeDD1v59awY_VJQtN8KjcJC4Q@mail.gmail.com>
- References: <CADr0+sc4a1G5eq-HQr3k=pJiQDeDD1v59awY_VJQtN8KjcJC4Q@mail.gmail.com>
--On Tuesday, July 31, 2018 12:13 PM -0600 Chris Cardone
<ccardone@squaretrade.com> wrote:
openldap-server-2.4.23p2 - configured with slapd.conf
openldap 2.4.42 - configured with a cn=config database
Both of these openldap versions are quite old and have significant
replication related issues. I'd strongly advise using a current release.
So im looking for some guidance / options to keep my new LDAP environment
in sync with my old, without any service disruptions on either set of
systems.
Since you're keeping them isolated from one another, you would need to
ensure that writes to any given environment are also sent to the other
environment. It's possible you could write a process using the sync
replication protocol to "listen" to each environment and replay the writes
on the other one.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>