Upgrading from Nexus Repository Manager 2
Nexus Repository 3 is a complete redesign of the repository manager and does not include any legacy code from Nexus Repository 2.
While Nexus Repository 2 was based on a Maven repository design that was dependant on how components were stored on the file system, Nexus Repository 3 uses blob storage, moving away from the idea of a repository being a folder in a file system. This makes Nexus Repository 3 far more scalable to different ecosystems and deployment environments, avoiding the file system limitations that some Nexus Repository 2 deployments encountered with flat directories containing tens of thousands of components common in some repositories.
Upgrading from Nexus Repository 2 to Nexus Repository 3 requires creating an upgrade plan:
- Begin by Determining and Planning Your Upgrade Path
- Understand Nexus Repository 2 vs. Nexus Repository 3 feature equivalency
- Consider any IQ Server or Firewall integration impacts, especially if using a manual method
- Plan to replace custom plugins and scripts using the Nexus Repository 3 API
- If not already complete, upgrade your Nexus Repository 2 instance to the latest Nexus Repository version using these instructions
- If using the Upgrade Wizard, decide on a data transfer method
- Whether using the Upgrade Wizard or Import, hard linking is always preferred; consider if you can remove any barriers to hard linking
- If using the Upgrade Wizard, complete optimization steps
- Ensure you meet all prerequisites
Once you have made the above decisions and created a plan, you are ready to upgrade!