Limiting the contents of a replica

The number of days specified here, known as the purge interval, controls when Domino® purges deletion stubs from a database. Deletion stubs are markers that remain from deleted documents so that Domino® knows to delete documents in other replicas of the database. Because deletion stubs take up disk space, Domino® regularly removes deletion stubs that are at least as old as the value specified. It checks for deletion stubs that require removal at one-third of the purge interval. For example, assuming the default value, 90 days, when a user opens a database, Domino® checks if it has been at least 30 days since it removed deletion stubs, and if so it removes any deletion stubs that are at least 90 days old. The Updall task, which runs by default at 2:00 AM, also removes deletion stubs.

You can shorten the purge interval, if you want, but be sure to replicate more frequently than the purge interval; otherwise, deleted documents can be replicated back to the replica.

Optionally, you can select the check box to remove documents in the replica that haven't changed within the purge interval. If you select the check box, when Domino® removes deletion stubs it also removes documents that haven't changed within the specified number of days. These documents are purged, meaning no deletion stubs remain for the documents, so the documents aren't deleted in other replicas. The This replica includes deletion stubs for all documents deleted since date setting prevents the purged documents from reappearing through replication. If the other replicas have this check box selected, similar document purging occurs in them.

This setting can prevent old documents which may have been deleted from replicating back into a database after their deletion stubs have been purged. The most common case occurs when an old version of a Domino® Directory is brought back into an organization 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 had already been purged. The Enable Purge Interval Replication Control setting prevents unwanted documents from replicating back into the environment.

Purge interval replication control uses the cutoff date of a database – the date when deletion stubs were last removed – to prevent documents older than the date from replicating into the database. Purge runs at one-third of the purge interval. If the purge interval is set to 90 days, then a database may have deletion stubs up to 120 days old. If the cutoff date is not set in a database, for example if the replication history has been cleared, purge internal replication control uses the current date minus the purge interval.

For details on this setting, see the technote in the related topics.

A replica can only receive documents created or modified since the date specified. If you clear the database replication history, during the next replication, Domino® scans only documents created or modified since the date specified here. If you clear the date before clearing the replication history, Domino® scans all documents in the database.

Use this option in conjunction with clearing the replication history to solve replication problems. If you clear or change this date, when Domino® next purges deletion stubs, it resets the date to correspond to the number of days specified in Remove documents not modified in the last n days setting. For example, if Domino® purges deletion stubs on 1/1/99 and the Remove documents not modified in the last n days setting is 90, on 1/1/99 Domino® resets the date to 10/1/98. If the check box is selected in the Remove documents not modified in the last n days setting -- meaning documents that meet the purge interval criteria are purged as well as deletion stubs -- this automatic date reset insures that the purged documents aren't replicated back into the replica.

If you select this setting, Domino® prevents large attachments from replicating and shortens the documents that this replica receives. The shortened documents contain only a document summary that includes basic information, such as the author and subject, and the first 40K of rich text.

When users open a shortened document, they see (TRUNCATED) in the document title. To view the entire document, users open it and choose Actions > Retrieve Entire Document.

Keep the following points in mind when using this setting:

• Users can not categorize or edit shortened documents.
• Shortened documents do not replicate unless the destination replica also has this option selected.

Use this setting to specify that a replica receives only the documents in a specific directory or view or only documents that meet selection criteria specified in a formula. Replication formulas are similar to view selection formulas.

Keep in mind the following points when you use replication formulas:

• You cannot use @DbLookup, @UserName, @Environment, or @Now in a replication formula.
• Using @IsResponseDoc in a replication formula causes all response documents in a database to replicate, not just those that meet the selection criteria. To avoid this, use @AllChildren or @AllDescendants instead, and make sure the database performance property Don't support specialized response hierarchy is not selected.

Use this setting to control which non-document elements a replica receives.