Replication Best Practices

Disable unnecessary repository modules on the target

Some repository modules don't make sense in a target environment. For instance, the broken links checker should only run in the source environment, since that is where a CMS is available to view the reports and where the problems that were found can be fixed. Having the broken links checker enabled on the target is only unnecessary overhead. In general you should review the modules in the target environment that can be disabled or removed entirely. You should review the necessity of the following modules:

• Broken links checker
• Event log cleanup module (only useful when the site application uses workflow)
• Updater executor (to be removed for security reasons)

Use per-target exclude and ignore paths

As of 15.7.10 and 16.9.3, you can define exclude and ignore paths par target. This should be done to narrow the scope of replicated content and can drastically reduce the number of packages that need to be sent to the target, speeding up replication and partial/full syncs. Excluding or ignoring images and assets is also highly recommended.