Migrating to a New Database

Perform a full backup using the backup task.

Shut down Nexus Repository.

Using your system console, change the directory to$data-dir/db.

Run the following command from the $data-dir/db directory. Note that you can also include any of the optional parameters listed in the section below when running this command.

java -jar nexus-db-migrator-*.jar \ 
--migration_type=postgres_to_h2 \ 
--db_url="jdbc:postgresql://<database URL>:<port>/nexus?user=postgresUser&password=secretPassword&currentSchema=nexus"

Edit the $data-dir/etc/nexus.properties file and add the following line:

nexus.datastore.enabled=true

Remove or rename the nexus-store.properties file you used for PostgreSQL so that Nexus Repository will not continue to try and boot to that properties file.

Start Nexus Repository.

Perform a database backup using the Admin - Export Database for backup task. We recommend copying the backup to another filesystem to avoid impacting the production environment.

The migrator uses the following backup files:

component-<timestamp>.bak
config-<timestamp>.bak 
security-<timestamp>.bak

Shut down Nexus Repository.

Run the following command from the location containing your backup.

java -Xmx16G -Xms16G -XX:+UseG1GC \ 
  -XX:MaxDirectMemorySize=28672M \ 
  -jar nexus-db-migrator-*.jar \ 
  --migration_type=h2

Copy the produced nexus.mv.db file to your $data-dir/db directory.

See Directories for details.

Edit the $data-dir/etc/nexus.properties file with the following line:

nexus.datastore.enabled=true

Start Nexus Repository.

Complete the post-migration tasks before upgrading Nexus Repository.

Create a database called nexus on the PostgreSQL server. Use UTF8 as its character set to be compatible with Nexus Repository.

We recommend setting the PostgreSQL autovacuum configuration to be on.

In the sonatype-work/nexus3/etc/fabric/ directory (i.e., $data-dir/etc/fabric), create nexus-store.properties; below is a sample that you will need to update with the appropriate configuration.

username=<postgres_user>
password=<postgres_password> 
jdbcUrl=jdbc\:postgresql\://<database-host>\:<database-port>/nexus

name=nexus
type=jdbc

Servers under heavy load may also need to configure the connection pool size for the database. Nexus Repository uses a default pool of 100, but you may increase this by appending a line like the following example to nexus-store.properties:

advanced=maximumPoolSize\=200

Add the following to $data-dir/etc/nexus.properties

nexus.datastore.enabled=true

Perform a full backup using the backup task

Copy the backup to a clean working location on a different filesystem so that any extraction doesn’t impact the existing production system

Shut down Nexus Repository

Update and run the following command from the location containing your database backup. Use the appropriate values for host, port, username, password, and migrator utility jar file name.

--add-exports java.base/sun.nio.ch=ALL-UNNAMED

java -Xmx16G -Xms16G -XX:+UseG1GC \
-XX:MaxDirectMemorySize=28672M \
-jar nexus-db-migrator-*.jar \
--migration_type=postgres \
--db_url="jdbc:postgresql://<database URL>:<port>/nexus?user=<postgres_user>&password=<postgres_password>"

When using database names and schemas that do not match, you need to add the variable &currentSchema=<name> to the end of the line. This variable is optional as this is not expected in a standard setup.

Run the following command on the Nexus Repository database after migrating but before starting Nexus Repository. This will reclaim storage occupied by obsoleted tuples left from the migration.

VACUUM(FULL, ANALYZE, VERBOSE);

Start Nexus Repository.

Ensure you are still on the same Nexus Repository version you were before the migration (e.g., if you were using 3.70.x, start your newly migrated instance as 3.70.x before upgrading beyond this).

Post-migration tasks must be completed before you can upgrade your Nexus Repository version.