[389-users] Re: keepalived with 389-ds

2018-07-12 Thread Brian Lehnhardt
Thanks. To make sure I'm understanding, you're saying it's not a good idea to use a VIP between the two masters? Is this type of setup not compatible? ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to

[389-users] keepalived with 389-ds

2018-07-11 Thread Brian Lehnhardt
Does anyone use keepalived with a mult-master setup? I'm currently using an haproxy, but I think just using a vip between the two masters should be sufficient for my use case. I'm curious how keepalived would work with a 389 server. ___ 389-users

[389-users] Re: Best method to duplicate 389-ds to new server?

2018-07-11 Thread Brian Lehnhardt
Yeah, my plan is to setup a replication agreement. That way I don't have to do multiple imports. I need the old and new servers to stay in sync until the cutover. ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an

[389-users] Best method to duplicate 389-ds to new server?

2018-07-11 Thread Brian Lehnhardt
I have a current 389 deployment that I need to duplicate to a new set of servers to be used at a different facility on a different network. I'm thinking that I could either do an import or use replication. My plan is to use replication to replicate the data to the new set of servers. That