Upgrade_Migrate Job Aid.pdf (371.8 KB)
If you’re treating Nexus Repository like the critical piece of digital infrastructure it is, then you want stability, flexibility, and minimal downtime. The absolute, hands-down best way to get those things is to make migrating to an external PostgreSQL database a priority.
Depending on your current deployment, migrating might take a bit of effort. Here’s the basic workflow.
- Determine your current database.
- Upgrade to 3.70.03, if you’re not there already.
- Download the correct binaries depending on whether you’re currently using OrientDB or H2.
- Prepare a full backup.
- Complete the pre-upgrade checklist.
- Complete the upgrade.
- Migrate to Postgres.
- Review our migration considerations.
- Fetch the migrator tool (for OrientDB or H2).
- Complete the migration procedures. Make sure you follow the correct procedure, depending on whether you’re currently using OrientDB or H2.
- Start Nexus Repository and allow two post-migration tasks to complete.
Attached to this post is a .pdf for you to save, distribute, and reference.