Notes.ini Entry


Name:
    Debug_Exclusive_Replication

Syntax
    Debug_Exclusive_Replication=0 / 1

Applies to:
    Servers

Add-on:

    First Release:
      6.0.5

    Obsolete since:

      Category:
        Debug

      Default:
        None

      UI equivalent:
        None

      Description:
      In your environment, multiple Lotus® Domino® server Replicator tasks are running on the same Lotus Notes® database, simultaneously. The target database grows substantially larger (two or three times larger) that the source database.

      This issue was reported to Quality Engineering and has been fixed in release 6.5.3 and 6.0.5. To utilize this fix, the following notes.ini entry must be enabled:

      DEBUG_EXCLUSIVE_REPLICATION=1

      This setting is not dynamic and requires a server restart.

      Side effects of using debug_exclusive replication

      If you have debug_exclusive_replication set on a hub server, the same database will not be replicated to other servers concurrently with multiple replicators. It will only replicate the database with each server one after another. To avoid this, do not set debug_exclusive_replication on the hub server but set it on the spoke servers. This will prevent the databases from growing on the spoke servers and only the hub databases would need to be compacted on a regular basis.

      Background:

      The increase in database size occurs when more than one replicator pulls documents into a database. Both replicator tasks populate the database.

      If a large document containing attachments is being pulled at the same time, for several minutes, each replicator first creates a document. Then space is allocated for the objects inside the database. When the attachments of the document are all transferred, the first replicator tries to store the document and is successful.

      When the second replicator tries to store the document, it is unsuccessful. The document already exists. The space already allocated by the second replicator is not freed and the database has some white space.

      The excess white space can be removed by running compact -B against the target database. The effects of this are particularly noticeable if a new replica is being populated by multiple replicators. Be aware that running multiple replicators will not improve the time it takes to populate a database.