Use replication tasks to copy the contents of the Main Repository to distributed repositories.
Unless you have replicated Main Repository contents to all your distributed repositories, some systems do not receive them. Make sure that all your distributed repositories are up-to-date.
Note
If you are using global updating for all your updates, replication tasks might not be necessary for your environment, although they are recommended for redundancy. However, if you are not using global updating for any of your updates, you must schedule a Repository Replication server task or run a Replicate Now task.
Scheduling regular Repository Replication server tasks is the best way to ensure that your distributed repositories are up-to-date. Scheduling daily replication tasks ensures that managed systems stay up-to-date. Using Repository Replication tasks automates replication to your distributed repositories.
Occasionally, you might check in files to your Main Repository that you want to replicate to distributed repositories immediately, rather than wait for the next scheduled replication. Run a Replicate Now task to update your distributed repositories manually.
Full vs. incremental replication
When creating a replication task, select Incremental replication or Full replication. Incremental replication uses less bandwidth and copies only the new updates in the Main Repository that are not yet in the distributed repository. Full replication copies the entire contents of the Main Repository.