Hi
What we did before is
-
Run
the “LDAP IP” as virtual IP on old servers
-
Create a new
set of LDAP servers with multi master replication
-
Verify functionality
on new servers
-
Create on
unidirectional replication from one old LDAP to one new LDAP
-
Move the virtual
IPS to the new servers
This gets a bit more
tricky if you use AD Replication with password sync but basically you only need to point the password sync to the virtual IP as well and make sure all SSL certificate stuff is in order, then the PWD Sync wil keep on working, the AD Replication can be broken
and recreated on the new servers (don’t forget to do a full sync afterwards)
For us that worked pretty
good when upgrading the OS the same way you are doing it right now
Soeren
From:
389-users-bounces@lists.fedoraproject.org [mailto:389-users-bounces@lists.fedoraproject.org]
On Behalf Of harry.devine@faa.gov
Sent: Tuesday, August 13, 2013 9:10 PM
To: 389-users@lists.fedoraproject.org
Subject: [389-users] Question about installing on new servers
We have 2 new servers that we are bringing into our suite, and we'd like them to eventually take over the current 389-ds role. We currently have
2 servers that are running 1.2.1 on CentOS 5.7 64-bit, and the 2 new servers are being installed with RHEL 6.3 64-bit. What we'd ultimately like to see/have happen is:
install 389-ds on the new servers
set up replication to replicate the data from the 2 old servers to the 2 new servers
point the underlying LDAP operations to the 2 new servers
take the 2 old servers out of the mix
Does anyone have any ideas or thoughts on if this is a good plan? And the best way to accomplish what we'd like to do?
Thanks,
Harry Devine
Common ARTS Software Development
AJM-245
(609)485-4218
Harry.Devine@faa.gov