The best practices for upgrading Nexus Repository 3 are as follows:
- Review all release notes up to the version you are upgrading to for any breaking changes, bug fixes and new features.
- Read the documentation Upgrading to Nexus Repository 3.71.0 and Beyond to confirm your upgrade path and requirements.
- Please also review the steps describes in Upgrading a standalone instance or Upgrading Nexus Repository in an HA Environment
- If you have not done so already, it is strongly recommended to migrate from the embedded Orient DB to external Postgres DB. Please refer to the Migrating to a New Database and Nexus Repository Database documentation. Please also refer to the note below.
- Review the Infrastructure-based Best Practices documentation, which includes taking a backup of your database and installation before upgrading.
- For taking backups of a Postgres DB please refer to https://www.postgresql.org/docs/current/backup.html.
- Test your planned upgrade path 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.
- Ensure that you have cleanup policies in place to manage and remove unused components. this helps in keeping the database size manageable to a minimum size. Refer to the Cleanup Policies documentation for more details.
Note: Nexus Repository's legacy embedded OrientDB database is in extended maintenance as of August 2024. Nexus Repository deployments must migrate off OrientDB. You must remain on the 3.70.x version line if you are unable to migrate at this time.