The Nexus Repository feature, High Availability Clustering (HA-C) has been sunsetted and is out of support. Use the following documentation to migrate to the latest functionality offering far superior functionality, quality, and scale.
Before attempting to migrate from HA-C, ensure that a full backup of your system has been recently performed in case of any complications.
Migrating from Legacy HA-C to a Single Instance
We recommend deployments using legacy HA-C migrate to our new High Availability (HA) deployment options. Use the steps below to remove the legacy HA-C capability and revert to a single instance.
To move from HA-C to a single instance, complete the following steps:
- Stop all Nexus Repository instances.
- Remove all but one of your Sonatype Nexus Repository HA-C nodes.
- Within your $data-dir directory, locate and edit the etc/nexus.properties file.
- Remove the nexus.clustered line from the file.
- Start the remaining Nexus Repository instance and ensure it is functioning as expected.
- Upgrade to the latest release following the upgrade instructions.
Migrating to a HA Deployment
New Nexus Repository HA deployment options replace the legacy HA-C deployment. HA-C required OrientDB while our current HA options require PostgreSQL. Follow the instructions below to migrate to a PostgreSQL database.
After moving to PostgreSQL, you may upgrade your deployment to use more resilient highly available deployments found in the help documentation.