Answers: <p>Yes, you can set up push event-driven replication. Please note that while pull replication prepopulates remote repository in server A from a local repository in server B, push replication replicates between two local repositories. Once you set up a virtual repository it doesn't really matter because you'll have a single point of access anyway, but just something for you to be aware of. </p>
  
  <p>You can read more about push replication and pull replication in <a href="https://www.jfrog.com/confluence/display/RTF/Repository+Replication" rel="nofollow noreferrer">the user guide</a>. Also, please <a href="https://jfrog.com/whitepaper/replication-using-artifactory-to-manage-binaries-across-multi-site-topologies/" rel="nofollow noreferrer">find here a whitepaper on different replication topologies</a> and <a href="https://www.youtube.com/watch?v=-HIwODsETMg" rel="nofollow noreferrer">a webinar on the same topic</a>.</p>
  
Answers: CC BY-SA 4.0
Answers: 2019-01-17T20:06:28.553Z
Answers: 2019-01-17T20:06:28.553Z
Answers: JBaruch
Body: <p>We have two instances of Artifactory for Prod and Non-Prod.</p>
  
  <p>Normal syncing happens via a pull mechanism by the Prod instance.</p>
  
  <p>Is it possible to also have an additional push event sync from Non Prod instance to the Prod that we would use for hotfixes.</p>
  
Tags: <artifactory>
Title: Additional push event syncing between Artifactory instances
UserDisplayName: Rob Wells
ThreadText: # Additional push event syncing between Artifactory instances
  
  (Asked by: username_0 on 2019-01-17)
  
  We have two instances of Artifactory for Prod and Non-Prod.
  
  Normal syncing happens via a pull mechanism by the Prod instance.
  
  Is it possible to also have an additional push event sync from Non Prod instance to the Prod that we would use for hotfixes.
  
  **Tags:** artifactory
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-01-17. Score: 2 | Accepted answer
  
  Yes, you can set up push event-driven replication. Please note that while pull replication prepopulates remote repository in server A from a local repository in server B, push replication replicates between two local repositories. Once you set up a virtual repository it doesn't really matter because you'll have a single point of access anyway, but just something for you to be aware of.
  
  You can read more about push replication and pull replication in [the user guide](https://www.jfrog.com/confluence/display/RTF/Repository+Replication). Also, please [find here a whitepaper on different replication topologies](https://jfrog.com/whitepaper/replication-using-artifactory-to-manage-binaries-across-multi-site-topologies/) and [a webinar on the same topic](https://www.youtube.com/watch?v=-HIwODsETMg).
  
  
  ---
  
  