Replication Best Practices

Disable Unnecessary Repository Modules on the Target

Certain repository modules are not required in the target environment. For example, the broken links checker should only run in the source environment. The source environment provides access to the CMS for reviewing reports and resolving detected issues. Running the broken links checker on the target environment adds unnecessary overhead.

Review all modules in the target environment and disable or remove those that are not needed. Evaluate the following modules in particular:

• Broken links checker
• Event log cleanup module (only needed if the site application uses workflow)
• Updater executor (remove for security reasons)

Configure Per-Target Exclude and Ignore Paths

Starting with versions 15.7.10 and 16.9.3, you can define exclude and ignore paths for each replication target. Use this feature to limit the scope of replicated content. Narrowing the replication scope reduces the number of packages sent to the target and improves replication and synchronization performance. Exclude or ignore images and assets where possible to further optimize replication.