This is a problem seen in almost every Notes/Domino environment old documents being added back to Domino database.
The most common case occurs when an old version of a NAB (Domino Directory) is brought back online after several months or years. When this occurs, previously deleted person documents, group documents, server documents, and other design elements can replicate back into the environment because the deletion stubs have already been purged.
How deleted documents reappeared after replication, How can this happen?
1. The purge interval is more frequent than the replication schedule.
2. A document was modified on one database replica after it was deleted on another replica copy.
3. A document was modified more often than the deleted document
Finding the old documents that reappeared is rather difficult and time consuming. To prevent this IBM has come with PIRC (Purge Interval Replication Control).
Lotus / Domino 8.5.3 has integrated with new feature, Purge Interval Replication Control (PIRC) prevents old documents from replicating back into the environment.
PIRC prevents documents from replicating back in two ways.
1. The first is by modifying the 'since time' used by the replicator.
2. The second way in which PIRC prevents older documents from replicating in is by stopping the
documents from being added to the database via NoteUpdate.
PIRC use Cutoff date of a database. The cutoff date is the date when purge last ran. Purge is the process which removes deletion stubs from a database. Purge runs at one-third of the purge interval. So if the purge interval is set to 90 days, then a database may have deletion stubs up to 120 days old. Therefore PIRC will use this date to prevent documents older than this date from replicating into the database. If the cutoff date is not set in a database, which happens when replication history is cleared, the current date minus the purge interval is used.
PIRC can be enabled using database Replication Setting under Space Saver tab.
You can also use Compact '-PIRC On' and '-PIRC Off' to enable PIRC to individual database.
PIRC generate DDM event when When PIRC blocks a note that is being pushed from a non-PIRC server.
For more information on PIRC refer IBM technote for complete details here
The most common case occurs when an old version of a NAB (Domino Directory) is brought back online after several months or years. When this occurs, previously deleted person documents, group documents, server documents, and other design elements can replicate back into the environment because the deletion stubs have already been purged.
How deleted documents reappeared after replication, How can this happen?
1. The purge interval is more frequent than the replication schedule.
2. A document was modified on one database replica after it was deleted on another replica copy.
3. A document was modified more often than the deleted document
Finding the old documents that reappeared is rather difficult and time consuming. To prevent this IBM has come with PIRC (Purge Interval Replication Control).
Lotus / Domino 8.5.3 has integrated with new feature, Purge Interval Replication Control (PIRC) prevents old documents from replicating back into the environment.
PIRC prevents documents from replicating back in two ways.
1. The first is by modifying the 'since time' used by the replicator.
2. The second way in which PIRC prevents older documents from replicating in is by stopping the
documents from being added to the database via NoteUpdate.
PIRC use Cutoff date of a database. The cutoff date is the date when purge last ran. Purge is the process which removes deletion stubs from a database. Purge runs at one-third of the purge interval. So if the purge interval is set to 90 days, then a database may have deletion stubs up to 120 days old. Therefore PIRC will use this date to prevent documents older than this date from replicating into the database. If the cutoff date is not set in a database, which happens when replication history is cleared, the current date minus the purge interval is used.
PIRC can be enabled using database Replication Setting under Space Saver tab.
You can also use Compact '-PIRC On' and '-PIRC Off' to enable PIRC to individual database.
PIRC generate DDM event when When PIRC blocks a note that is being pushed from a non-PIRC server.
For more information on PIRC refer IBM technote for complete details here
