Thanks Quanah; I take it that your advice from a while back still stands, slapadd the main dbase from mm-server1 to mm-server2 (this time I won't do a slapindex -- honest)?
Thanks in advance John -----Original Message----- From: Quanah Gibson-Mount [mailto:[email protected]] Sent: Monday, February 10, 2014 6:42 PM To: Borresen, John - 0442 - MITLL; Michael Ströder; [email protected] Subject: RE: Simple way to check that MMR is in sync? --On Monday, February 10, 2014 5:23 PM -0500 "Borresen, John - 0442 - MITLL" <[email protected]> wrote: > All, > > I've been reading this string... > > Comparing the entryCSNs & contextCSNs on both of my test servers at > the base DN (dc=example,dc=ldap): > > mm-server1: > entryCSN: 20140121153301.911487Z#000000#003#000000 > contextCSN: 20140203183831.751838Z#000000#001#000000 > contextCSN: 20140204143957.937393Z#000000#002#000000 > > mm-server2: > entryCSN: 20140121153301.911487Z#000000#003#000000 > contextCSN: 20140129140325.443822Z#000000#000#000000 > contextCSN: 20140203183831.751838Z#000000#001#000000 > contextCSN: 20140129183014.073734Z#000000#002#000000 > contextCSN: 20140121153301.911487Z#000000#003#000000 > > 1) What is this information telling me? (I want to be sure that I > know) > 2) Should I be concerned that there are more on mm-server2? a) Ignore entryCSN b) This means that mm-server2 has knowledge of 3 masters (1, 2, 3) mm-server1 only has knowledge of 2 masters (1, 2). This would imply that there is something broken in your setup. --Quanah -- Quanah Gibson-Mount Architect - Server Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration
