Skip to end of metadata
Go to start of metadata
Table of Contents


Through the Replication Add-on in Artifactory Pro, Artifactory allows replication of repositories to support development by different teams distributed over distant geographical sites. The benefits of replication are:

  • Ensuring developers all work with the same version of remote artifacts
  • Ensuring build artifacts are shared efficiently between the different development teams
  • Overcome connectivity issues such as network latency and stability when accessing remote artifacts
  • Accessing specific versions of remote artifacts

Two main methods of replication are supported:

Push Replication

Push replication is used to synchronize Local Repositories, and is implemented by the Artifactory server on the near end invoking a synchronization of artifacts to the far end.

There are two ways to invoke push replication:

  • Scheduled push: Pushes are scheduled asynchronously at regular intervals
  • Event-based push: Pushes occur in nearly in real-time since each create, copy, move or delete of an artifact is immediately propagated to the far end.


  • It is fast because it is asynchronous.
  • It minimizes the time that repositories are not synchronized.
  • It reduces traffic on the master node in case of a replication chain ("Server A" replicates to "Server B", "Server B" then replicates to "Server C" etc.).

Avoid Replication Loops ("Cyclic Replication")

A replication loop occurs ("Cyclic" or "Bi-directional" replication) occurs when two instances of Artifactory running on different servers are replicating content from one to the other concurrently.

For example, "Server A" is configured to replicate its repositories to "Server B", while at the same time, "Server B" is configured to replicate its repositories to "Server A".

Or "Server A" replicates to "Server B" which replicates to "Server C" which replicates back to "Server A".

We strongly recommend avoiding cyclic replication since this can have disastrous effects on your system causing loss of data, or conversely, exponential growth of disk-space usage.

Replication Loop

Replication loop to be strictly avoided

When to Use Push Replication

Event-based push replication is recommended when it is important for the repository at the far end to be updated in near-real-time for any change (create, copy, move or delete of an artifact) in the repository at the near end.

In addition, we recommend running regular scheduled replication on top of event-based replication to guarantee full copy consistency even in cases of server downtime and network partitions.

Pull Replication

Pull replication is invoked by a remote repository, and runs according to a defined schedule to synchronize repositories (local, remote or virtual) at regular intervals.

This provides a convenient way to proactively populate a remote cache, and is very useful when waiting for new artifacts to arrive on demand (when first requested) is not desirable due to network latency.

Pull replication runs as a scheduled task.


  • Many target servers can pull from the same source server efficiently implementing a one-to-many replication.
  • It is safer since each package only has one "hop".
  • It reduces traffic on target servers since they do not have to pass on artifacts in a replication chain.

When to Use Pull Replication

 Pull replication is recommended in the following cases:

  • When you need to replicate a repository to many targets pull replication.
  • When your source repository is located behind a proxy that prevents push replication (e.g. replicating a repository hosted on Artifactory online to a local repository at your site)

Page Contents

Scheduling and Configuring Replication

Using the UI

Replication is configured via the user interface as a scheduled task. Local repositories can be configured for push replication, and remote repositories can be configured for pull replication.

All replication messages are logged in the main Artifactory log file (artifactory.log).

Configuring Push Replication

A push replication task for a Local Repository is configured in the Replication tab of the Edit Local Repository dialog as follows:

Field NameDescription


When set, enables replication of this repository


The URL of the target local repository on a remote Artifactory server.

Cron Expression

Defines the replication task schedule using the a valid cron expression.

Next Replication Time

Relies on the information in the Cron Expression field.

Enable Event Replication

When set, event-based push replication is enabled


The HTTP authentication username.


The HTTP authentication password.


A proxy configuration to use when communicating with the remote instance.

Socket Timeout

The network timeout in milliseconds to use for remote operations.

Sync Deletes

When set, items that were deleted remotely should also be deleted locally (also applies to properties metadata).

Sync Properties

When set, the task also synchronizes the properties of replicated artifacs.

Path Prefix (optional)

A subpath to replicate within the repository.

Push Replication Settings

Configuring Pull Replication

Configuring Pull Replication for a Remote Repository is very similar to configuring Push Replication for a Local Repository. Please refer to Configuring Push Replication for details.

Pull Replication Settings

Regarding credentials of the remote repository configuration

The remote repository's file listing for replication is retrieved using the repository's credentials defined under the repository's Advanced configuration section.

The remote files retrieved depend on the effective permissions of the configured user on the remote repository (on the other Artifactory instance).

Replicating with REST API

Both Push and Pull Replication are supported by Artifactory's REST API. For details please refer to the following:

Watch the Screencast

To see the Replication in action you can watch the short demo screencast below.

  • No labels