Skip to main content

Creating a New Replication Connection (Legacy)

Note

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

Warning

In release 3.48.0, we introduced Content Replication, which removes Replicator and makes replication easier to set up and deploy. This documentation remains available for current implementations only. We do not recommend implementing this version of replication as we will be completely removing it once the new replication design is available.

Note

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.

  1. Before creating a new replication connection, ensure you have satisfied all Replication Prerequisites (Legacy).

    Warning

    Prerequisites include but are not limited to the following:

    • Source and target instances must be on the same Nexus Repository Pro version.

    • Source and target repositories must be one of the following formats:

      • Docker

      • Maven hosted

      • npm

      • NuGet

      • PyPI

      • Raw

    • Source and target repository blob stores cannot be part of a blob store group.

    • For file-based blob stores, the source and target repository blob stores must be readable/writable on the machine where the Replicator tool (the replication CLI jar) runs

    • Source repository must be able to send HTTP requests to the target Nexus Repository instance during the initial configuration process.

    • Repository replication is not compatible with the legacy High Availability Clustering (HA-C) feature.

  2. In the source instance (the repository from which you want to replicate components), navigate toAdministration→ Repository→ Replication.

  3. ClickNew Replication; the New Replication configuration form displays.

  4. Provide a unique name for the replication.

  5. Select an option for all existing content or only filtered content.

  6. UnderSource Repository Name, select the repository from which you would like content to be replicated.

  7. UnderInstance URL,provide the target instance URL and port to which content should be replicated. The target instance URL is the root URL of the instance.

  8. Provide a username and password for your target instance under User Authentication. This user should have the Replication Administrator role.

  9. If desired, check the checkbox for Use certificate connected to the Nexus Truststore. This tells your source Nexus Repository instance to use the Nexus Truststore for certificates when contacting the remote Nexus Repository. See Configuring SSL for more information on adding Truststore certificates.

  10. Select the Test Repository Connection button. This triggers the source instance to communicate with the target instance using the authentication credentials provided. If the connection is successful, a list of the available target repositories displays inside a drop-down menu on the form.

  11. From the Target Repository Name drop-down menu, select the target repository for the replication.

    Warning

    Ensure the target repository is a newly created hosted repository of the supported formats. As a best practice, do not use a target repository that has previously uploaded binaries. This allows you to more easily manage your storage requirements for replicated content. Note also that the target repository will be read-only to all other requests as long as it is configured as a target repository.

  12. Select Create Replication Connection to finish the configuration.

A newly created replication connection now displays under Current Connections on the Replication page. If configured, any existing data in the repository is queued for replication and content will start replicating once the Replicator is running.

You should proceed to Running Replicator (Legacy).