Reverting Back to OrientDB
The migration process is one-way: the migrator utility extracts configuration and component metadata from the Orient database and moves it to H2 or PostgreSQL. The Orient database is unchanged and remains in place as a restoration point.
Once you start a Nexus Repository instance, database and blob storage contents diverge. After this, reverting to Orient requires restoring the blob stores from the backup.
Use the following steps to revert to OrientDB:
Shut down Nexus Repository
Delete the following from the
$data-dir/etc/nexus.properties
file:nexus.datastore.enabled=true
Restart Nexus Repository
We recommend running the blob store reconciliation task after reverting to reconcile changes to the blob store with the database with any binaries that you may have made since the migration.
Legacy Embedded Orient Database
Nexus Repository's legacy embedded Orient database entered extended maintenance in August 2024. All deployments must migrate off of OrientDB to upgrade to newer versions.
Version 3.71.0 and beyond do not support OrientDB.
If you are unable to migrate, you must remain on the 3.70.x version line.