Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

1) admin4.nsf set to future date after replicating with one of the server?

2) date is set to future now November 2013

3) tried clearing replication history, didnt help

4) tried to create a local replica, didnt help either

5) Creating a new copy of admin4.nsf on all 117 servers sounds difficult and prone to issues.

any idea will be helpfull.


share|improve this question
  1. Verify that ALL servers have the proper time
  2. Find out why that server "travelled" in time
  3. Replication history has to be purged from the database on the server (check ALL other databases for signs of this, too!)
  4. Deletion stubs must be purged from database

Item 3. and 4. according to "Time Travel for Beginners" out of Paul Mooney's and Bill Buchan's "Worst Practices in IBM Lotus Domino - Learning From the Mistakes of Others" (pdf) session at Lotusphere 2006

share|improve this answer
is PIRC the 'Deletion stubs must be purged from database' from this article i found -> it look like 853 feature - if yes then we are on 851 .. many thanks – kasper_341 Aug 23 '13 at 16:02
That is just a new feature to make it easier. You can use the updall task to remove deletion stubs, or create a copy (not a replica) of the DB and redeploy it. – leyrer Aug 23 '13 at 16:59

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.