Repository replication in Artifactory is a mechanism that enables the synchronization of artifacts between multiple Artifactory instances. It ensures that changes made to artifacts, such as uploads, downloads, or deletions, are propagated across all replicated instances, allowing for consistent and reliable access to artifacts in distributed environments.
When attempting to replicate files from one Artifactory instance to another, users may notice that metadata files are not replicated. This behavior can be perplexing, especially when expecting an exact replica of the source instance on the target instance.
The reason behind metadata files not being replicated lies in the nature of the information they contain. Metadata files often include source-specific URL information that is not relevant or applicable to the destination instance. Replicating this source-specific data would lead to inconsistencies and potential conflicts.
Therefore, non-replication of metadata files is an intentional and expected behavior. It ensures that the destination instance remains independent and accurately represents its own environment.
To confirm that this is the behavior you're running into, you may utilize the Replicationdiff script located in https://github.com/jfrog/artifactory-scripts/tree/master/replicationDiff. This script will run a comparison of files between the source and target instances and highlight the missing files. If you see that these files are metadata files, then you can be sure that replication is working as intended.
Below are some examples of metadata files of popular package types that you can expect to not get replicated:
Maven: maven-metadata.xml
Npm: package.json
RPM: anything under repodata folder
Docker: anything under "/_uploads/"