Replication Scenarios

Only available in Nexus Repository Pro. Interested in a free trial?  Start here.


NEW IN 3.34.0

 

We are redesigning replication in 2022 to remove Replicator and make it easier to set up and deploy. Once we release the new implementation, we will no longer support the replication method detailed here.

Replication is not appropriate for disaster recovery. If you need a disaster recovery solution, please see our resilient deployment options and backup and restore procedures.

As mentioned in Replication Use Cases, there are multiple use and business cases for repository replication. This topic covers basic configuration steps for these use cases.

One Source Multiple Targets

  1. Ensure you have satisfied all prerequisites.
    1. Follow the prerequisite steps for Nexus Repository instances.
    2. Optionally, follow the additional prerequisite steps for separate replicator instances.
    3. Enable the capability on the source and target instances.
    4. If you have existing components from before you configured replication, create and run the new Replication - Backfill blob store attributes with component metadata task in the source instance.
  2. Create your replication connection to connect your source to one target. 
  3. Test your replication to ensure it is working properly by uploading new components to the source repository. You should see the replicated content appear in your target repository after you have run the Replicator.
  4. Add a second replication connection:
    1. Select the same source repository as in the first step above.
    2. Enter a different target URL that points to a different target instance.
    3. Finish the rest of the configuration as previously documented.
  5. Upload a new component to your source repository, run the Replicator, and you should see the new component replicated to the target repositories.

Bi-Directional Replication

To use bi-directional replication, your team will need to access both the source (for read and write) and target (for read) repositories in their respective instance. A total of four repositories are involved in this setup. The steps below will refer to Instances A and B as illustrated in the diagram above.

  1. Ensure you have satisfied all prerequsites.
    1. Follow the prerequisite steps for Nexus Repository instances.
    2. Optionally, follow the additional prerequisite steps for separate replicator instances.
    3. Enable the capability on the source and target instances.
    4. If you have existing components from before you configured replication, create and run the new Replication - Backfill blob store attributes with component metadata task in the source instance.
  2. Create your replication connection to connect your source repository on Instance A to the target repository on Instance B.
  3. Test your replication to ensure it is working properly by uploading new components to the source repository on Instance A. You should see the replicated content appear in your target repository on Instance B after you have run the Replicator.
  4. Create a new replication connection to connect your source repository on Instance B to the target repository on Instance A.
  5. Test to ensure it is working properly by uploading new components to the source repository on Instance B. You should see the replicated content appear in your target repository on Instance A after you have run the Replicator.