<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Did you use the IP when creating the replication agreement? The IP *should* have no bearing on it, at least thats what I thought. I'd be interested it know now, because I'll be moving a master soon.<div><br><div><div>On Dec 16, 2012, at 8:50 PM, Shardul Kerkar <<a href="mailto:SKerkar@accessline.com">SKerkar@accessline.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="content-type" content="text/html; charset=utf-8"><div dir="auto"><div>Adding another Master is not an option because for the end result the IP address and dns record of the master should be same. I did try to swap the hardware on the existing Master after stopping writes and making sure that the db was in sync. After recreating replication agreements with the hubs, it is now complaining that the hubs have a different generation id, hence won't replicate. <br><br><div><br></div><div><br></div></div><div><br>On Dec 16, 2012, at 6:52 AM, "Dan Lavu" <<a href="mailto:dan@lavu.net">dan@lavu.net</a>> wrote:<br><br></div><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><base href="x-msg://10280/">You do not have to init the database as long as they are in sync, you can just 'send updates'. If all the slaves are 1.1.2, you'd want to eventually upgrade those machines too, have you considered just adding another master (master/master) then sliding the original master out? Should equate to zero downtime. <div><br><div><div>On Dec 14, 2012, at 6:53 PM, Shardul Kerkar <<a href="mailto:SKerkar@accessline.com">SKerkar@accessline.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div lang="EN-US" link="blue" vlink="purple" style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div class="WordSection1" style="page: WordSection1; "><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">Hi Folks,<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">I have recently been tasked with moving a Single Ldap Master from a dying machine to a spanking new blade. After doing some research it appears to me that the optimum way to do this will be installing a fresh instance of the application on the new server, import the database and then recreate and reinitialize all the hubs and replicas. The problem I face is that this work place has a humongous LDAP database will 3 mil+ entries. Re-initialization is taking upto 3 hours in some cases. With 5 hubs and 20 replicas to reinitialize, the downtime is unacceptable to the client.<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">If I stop writes to the Master, then export the database to the new box and recreate the New-Master-Hub replication after removing the old Master , will I still need to re-initialize the hubs? Is there any way to do this swap without reinitializing or fooling the hubs and reps into thinking that they are still talking to the same Master albeit on a new machine (same ip address/dns).<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">The client is still using ver. 1.1.2 on Centos 5.4<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">Thanks,<o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">Shar Ker<o:p></o:p></div></div>--<br>389 users mailing list<br>389-<a href="mailto:users@lists.fedoraproject.org" style="color: purple; text-decoration: underline; ">users@lists.fedoraproject.org</a><br><a href="https://admin.fedoraproject.org/mailman/listinfo/389-users" style="color: purple; text-decoration: underline; ">https://admin.fedoraproject.org/mailman/listinfo/389-users</a></div></blockquote></div><br></div></blockquote><blockquote type="cite"><ATT00001..c></blockquote></div>--<br>389 users mailing list<br>389-<a href="mailto:users@lists.fedoraproject.org">users@lists.fedoraproject.org</a><br><a href="https://admin.fedoraproject.org/mailman/listinfo/389-users">https://admin.fedoraproject.org/mailman/listinfo/389-users</a></blockquote></div><br></div></body></html>