[
A recent event with a customer reminded me of 1999 when everyone was on the Y2K checking programme. At the time a business partner was recommending to check your Domino applications you should bring the server down and change the OS date to a post 2K date (e.g. 2030); bring it back up and test... You could then sign off your applications. All well and good, until after resetting the date to 1999 and restarting the server, you realise that your applications are not replicating correctly. This is because you were not warned to use sample data, or to disconnect your server from the live network and while your server was years ahead of you, it replicated with spokes (or worse, a cluster member!).
Each application on your Domino server retains a replication history (File / Replication / Replication History) where it remembers when it last successfully replicated with another replica on the network. This is a good thing because it is used as a checkpoint for the next replication. When your server is replicating, it looks at the history checkpoint for the destination server and will only replicate documents modified after that date. This makes for excellent, efficient replication.
Except for when your Server thought it was 2030 and replicated with another server. As it should, each application retains the checkpoint as the date in 2030, and will dutifully not try to replicate any changes or additions from before that date. So when your date is reset, new documents are ignored until 2030..... A bit of a wait, me thinks...
The solution is relatively simple; go into the application and enter the Replication History dialog box. From there, choose the "clear" option so the server will check and replicate all documents in the database. The downside to this is the next replication will take a long time as all documents are checked.
]