The best practices for upgrading Nexus Repository 3 are as follows:-
- Review the latest release notes 2025-release-notes.
- Read the documentation for Upgrading to Nexus Repository 3.71.0 and Beyond to confirm your upgrade path and requirements.
- Review the infrastructure-based-best-practices documentation, which includes taking a backup of your database and installation before upgrading.
- Test your upgrade on a copy of your production environment before performing the upgrade live on production. This allows you to test upgrading Nexus Repository 3 before performing it live on a production environment. This can help you resolve any errors that may occur and it will also give you an idea of the time taken to complete the production upgrade.
- If you have not done so already, migrate from the embedded Orient DB to external Postgres DB. Please refer to Configuring-for-External-PostgreSQL. Typically, the database lock timeouts frequently seen with Orient DB and the build up of threads waiting on database are reduced. We have not seen any corruption on the Postgres DB, which we have observed frequently with the embedded Orient DB.
- Taking backups of the Postgres DB using Postgres is very quick, please refer to https://www.postgresql.org/docs/current/backup.html.
- To keep the size of your database to a minimum, which will help with the upgrading of the database, ensure that you have cleanup policies in place, please refer to Cleanup-policies. Note: You will need to execute an Admin - Compact blob store task to reclaim blob store space.
- When using an external Postgres DB, it is crucial to have a low latency network connection between Nexus Repository 3 and the database server.
- Please also refer to the Kb article Upgrading-Nexus-Repository-Manager-3 on upgrading Nexus Repository 3 instances.