Moving from a High Availability Deployment to a Single Instance
This topic provides instructions to follow should you need to move from a clustered, highly available Sonatype Nexus Repository deployment to a single instance.
This topic covers migration from one of our HA deployment options introduced in release 3.50.0; for instructions on how to move from legacy HA-C to a single instance, see Migrating from Legacy HA-C to a Single Instance.
Container-Based Instructions
- Scale replicas to 0 in the
deployment.yml
or using the kubectl. In your
$data-dir/sonatype-work/nexus3/etc/nexus.properties
, setnexus.datastore.clustered.enabled
tofalse
.- Set
nexus.datastore.enabled
totrue
(required to use the PostgreSQL database). - Set replicas to
1
in thedeployment.yml
or using the kbectl.
Non-Container-Based Instructions
- Stop all Sonatype Nexus Repository instances.
- In the
$data-dir/sonatype-work/nexus3/etc/nexus.properties
file for the instance you want to turn back on, set thenexus.datastore.clustered.enabled
tofalse
. - In this same instance, set
nexus.datastore.enabled
totrue
(required to use the PostgreSQL database). - Start the Sonatype Nexus Repository instance.