>> Marc Patermann <hans.moser(a)ofd-z.niedersachsen.de&gt; schrieb am 29.08.2013 um

Ulrich Windl schrieb (29.08.2013 09:48 Uhr): > When I examine my slapcat of the config database (multi-master replication), I see a duplicate contextCSN; one of them seems obsolete: > contextCSN: 20130722065709.189194Z#000000#000#000000 > contextCSN: 20130729112421.079210Z#000000#001#000000 ----------------------------------------------^

ServerID Marc

>> Quanah Gibson-Mount <quanah(a)zimbra.com&gt; schrieb am 29.08.2013 um 18:25 in

--On Thursday, August 29, 2013 9:48 AM +0200 Ulrich Windl <Ulrich.Windl(a)rz.uni-regensburg.de&gt; wrote: > Hi! > > When I examine my slapcat of the config database (multi-master > replication), I see a duplicate contextCSN; one of them seems obsolete: > contextCSN: 20130722065709.189194Z#000000#000#000000 > contextCSN: 20130729112421.079210Z#000000#001#000000 > > Can I remove one of those, and if so, how? I tried once, but the CSN > re-appered, maybe from an other master... > > Or are those expected to be there? The #000# CSN if from when the database was single master. It will never update once you've moved to MMR, but there are likely still entries that existed prior to MMR with entryCSNs with #000#. You can simply ignore that CSN now that you are in MMR mode. The script I wrote to compare CSNs across MMR nodes does exactly that (ignore's the #000# CSN).

--Quanah -- Quanah Gibson-Mount Lead Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration