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

Re: (ITS#4626) "glue" objectclass in syncrepl consumer



On Mon, Jul 31, 2006 at 06:16:02PM +0000, ahasenack@terra.com.br wrote:
> My setup consists of three servers:
> 
> a) syncrepl provider for the whole database: dc=example,dc=com
> 
> b) Two databases:
> - ou=global,dc=example,dc=com: consumer from (a)
> - dc=example,dc=com: provider
> Both are glued together.
> 
> c) One database, pulling everything from (b)
> 
> Config files for (a), (b) and (c) are below. I can also submit the sample
> databases I'm using if needed.

With this same setup, replication of "ou=global" from (b) to (c) isn't working.
No change is detected when I alter ou=global in server (a).

I'll try to draw it:

(a) one database, one syncprov:

             + dc=example,dc=com
            / \
         ...   + ou=global
              / \
           ...   ...


(b)
             + dc=example,dc=com
            / \
         ...   + ou=global (pulled from (a) via syncrepl)
              / \
           ...   ...

This is two databases glued together: one for dc=example,dc=com and another for
ou=global, which is pulled from (a) using ou=global,dc=example,dc=com as the
base. I tried with one syncprov in dc=example,dc=com loaded after glue, and
with two syncprov (one for each database).


(c)

              + dc=example,dc=com
             / \
          ...   + ou=global
               / \
            ...   ...

This one is a single database and a consumer from (b). The syncrepl base is
dc=example,dc=com. It's a backup server for (b).

This server doesn't get changes done to ou=global, and it also has the issue
where the ou=global entry itself gets mangled.