syncrepl (refreshAndPersist) fails after system date is moved backwards

Hello,

I'm facing some problems with replication and hoping that someone could clarify how this case should work (is this a bug or a feature). Replication seems to work initially as expected but if I change the system date to something in the past (e.g. 1 year backwards) then the replication stops working. When I change back the current date (to the year that it initially was) then everything seems to work fine again.

Is this kind of behaviour in LDAP a restriction that has to do with having timestamps in the CSNs or is this a bug? I tried to find this problem from the archives with no success.

Br, -Jani