Download and install the latest Nexus Repository Pro version in two separate environments following regular installation instructions.

Prerequisite Steps for Nexus Repository Instances Note also that the target repository will be read-only to all other requests outside of replication as long as it is used as a target repository. This ensures you can maximize the manageability of the storage requirement of replicated content. As a best practice, do not use a target repository that has previously uploaded binaries.

Ensure the target repository is a newly created hosted repository in one of the supported formats.

The Replicator directory in the Nexus Repository bundle is portable this means you can deploy the Replicator on the source instance, target instance, or even in a separate location as long as it is able to see and communicate with all repositories.

The Replicator must be able to see and communicate with all repository instances.Replicator requires a *nix, or Windows 10 Linux subsystem.The source and target repositories must be locally mounted on the machine where the Replicator (the replication CLI jar) runs for file replication. Repository replication is not compatible with the legacy High Availability Clustering (HA-C) feature.Source repository must be able to send HTTP requests to the target Nexus Repository instance during the initial configuration process.Source and target repository blob stores cannot be part of a blob store group.

Source and target repositories must already be set up before you can create a replication connection.Source and target repositories must be in one of the supported formats: Ensure you are on the latest Nexus Repository Pro version.Įnsure both source and target are on the same Nexus Repository Pro version.Repository replication is only available for Nexus Repository Pro customers you must have a valid Nexus Repository Pro license to proceed.In order to use repository replication, you must meet the following prerequisites: If you need a disaster recovery solution, please see our resilient deployment options and backup and restore procedures. Replication is not appropriate for disaster recovery.

Download the new REPLIKATOR