Re: Replication strategy

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



William,

You could make multiple agreements that sync the Ou's only that you want
rather than the full tree sync. That's one option.

Answer: For me it's not a option, I have several OUs and wouldn't be a easy thing to do.

Reading the docs, it looks like it's because the external ou has users
in, and it's part of this subtree, so I think you can't avoid it I'm
sorry. There doesn't seem to be an exclude filter or include filter, so
I think there is not an easy solution here.


Answer: That's what I thought

Another option might be to break external ou to a seperate backend as a
subsuffix, because I *think* replication only operates on a single
backend (not across it), but mreynolds may know the correct answer to
this,

Answer: I already thought about that too once you confirmed me there's no other way to do that. I'll try on it in my lab.

Thanks a lot.

On Sun, Jun 4, 2017 at 10:33 PM, William Brown <wibrown@xxxxxxxxxx> wrote:
On Fri, 2017-06-02 at 10:36 -0300, Alberto Viana wrote:
> William,
>
> I do nothing hehehehe, what I mean that I just ignore the errors :)
>
> Here's my agreement:
>

> nsds7WindowsReplicaSubtree: dc=my,dc=domain
> nsds7DirectoryReplicaSubtree: dc=my,dc=domain

You could make multiple agreements that sync the Ou's only that you want
rather than the full tree sync. That's one option.

Reading the docs, it looks like it's because the external ou has users
in, and it's part of this subtree, so I think you can't avoid it I'm
sorry. There doesn't seem to be an exclude filter or include filter, so
I think there is not an easy solution here.

Another option might be to break external ou to a seperate backend as a
subsuffix, because I *think* replication only operates on a single
backend (not across it), but mreynolds may know the correct answer to
this,

Sorry I can't help more :(

--
Sincerely,

William Brown
Software Engineer
Red Hat, Australia/Brisbane


_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org


_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx

[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux