Skip to main content

Nexus Repository 3 Upgrade Wizard

Nexus Repository includes the Upgrade Wizard capabilities to migrate Nexus Repository 2 to a new Nexus Repository 3 instance. Upgrading to Nexus Repository 3 using the Upgrade Wizard is the preferred method.

  1. Meet the prerequisites for upgrading.

  2. Understand the Upgrade Process

  3. Determine the data transfer method

  4. Take steps to optimize upgrade performance

  5. Configure the Upgrade Capabilities

  6. Follow the step-by-step guide through the wizard

  7. If you need to start over, reset your upgrade

  8. Configure the legacy URL paths when needed.

Prerequisites for Upgrading

A successful upgrade from Nexus Repository 2 requires planning, decision-making, and testing before attempting the actual upgrade.

  1. The Nexus Repository 3 instance must be a new single-node instance

    The upgrade tool replaces the configuration in Nexus Repository 3. The wizard is expected to only run once. The upgrade tool is not supported with Nexus Repository 3 in a highly available deployment.

  2. Both Nexus Repository 2 and Nexus Repository 3 have the same license type

    When upgrading both versions must have the same licensing setup. Use the same license file in both instances. Instances on the same server share the same license.

  3. The Nexus Repository 2 instance is on the latest version

    • Community Edition (CE): upgrade to the 3.76.0 release with H2. After the upgrade, migrate to the latest release with PostgreSQL.

    • Professional (Pro): upgrade directly to the latest version with the PostgreSQL database.

  4. The work directory and files must be owned by the OS user with no zero-length files

    Use the following Linux command to find files in the work directory not owned by the 'nexus' user as well as zero-length files:

    find . \! -user nexus -print
  5. Nexus Repository 2 repositories must use distinguishable names

    IDs of repositories and repository groups in Nexus Repository 2 that differ only by case will not be accepted during an upgrade to Nexus Repository 3 (example version 2 IDs: myrepoid vs. Myrepoid).

  6. Test the upgrade using a backup in a test environment first

    We recommend running the upgrade wizard in a test environment to see when errors may occur and set expectations.

  7. Set blob stores to outside of the sonatype work directory

    For resilient deployments, we recommend setting the blobstore outside of the default work directory.

    See the Storage Guide)