[389-users] how to keep in sync centos-ds in a dr scenario
jamespfinn at gmail.com
Thu Apr 26 15:03:28 UTC 2012
Instead of having the same actual IP for each server, why not use virtual
IPs with something like heartbeat? This way if replica-A at siteA goes down,
replica-A at siteB will take over. This entirely depends on your network
topology, but may be a step in the right direction.
Having servers with the same IPs doens't seem to be the most elegant
solution; same with rsync'ing your database instead of using replication.
On Thu, Apr 26, 2012 at 7:03 AM, Paul Robert Marino <prmarino1 at gmail.com>wrote:
> Well that's not a great way to set that up but its workable. You will need
> to sync without ssl and do a destination nat betwean them
> On Apr 26, 2012 4:05 AM, "Maurizio Marini" <maumar at cost.it> wrote:
>> I have a disaster recovery scenario:
>> on a remote location I have the same servers with the same hostnames and
>> same ip's, exactly all the same.
>> Nightly I use rsync to keep all the servers in sync.
>> One of this server is a CentOS5 with centos-ds and samba as pdc.
>> I cannot use replica between current and dr, as the 2 server have the
>> same ip
>> and hostname.
>> I am using ldap2db to import the nightly ldif backup.
>> /usr/lib/dirsrv/slapd-centos-ds/ldif2db -n userRoot -i
>> It seems work, it's dirty but does work.
>> Do u see any side-effects? Have u some suggestion?
>> 389 users mailing list
>> 389-users at lists.fedoraproject.org
> 389 users mailing list
> 389-users at lists.fedoraproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the 389-users