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 1/3 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 "Only Replicate Incoming Documents Saved or Modified After: 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.

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 x days" setting. For example, if Domino® purges deletion stubs on 1/1/99 and the "Remove documents not modified in the last x 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 x days" setting -- meaning documents that meet the purge interval criteria are purged as well as deletion stubs -- this automatic date reset ensures that the purged documents aren't replicated back into the replica.

For more information on the replication history, see Domino® Administrator Help.

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 40KB of rich text.

When users open a shortened document, they see "(TRUNCATED)" in the document title. To view the entire document, users must choose Actions - Retrieve Entire Document from the open document.

Keep the following points in mind when using this setting:

• Users can't categorize or edit shortened documents.
• Agents don't work on shortened documents.
• Shortened documents replicate only if the destination replica also has this option selected.

Use this setting to specify that a replica receives only the documents in a specific folder 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. Use @AllChildren or @AllDescendants instead and make sure the database performance property "Don't support specialized response hierarchy" is not selected.

For more information on database performance properties, see Setting advanced database properties.

Use this setting to control which non-document elements a replica receives. This table describes the Replicate options:

For information on the minimal Address Book options, see Notes® Help.

For information on directory catalogs, see Domino® Administrator Help.