SQL Database Options
Only available in Nexus Repository Pro. Interested in a free trial? Start here.
Database Options for Nexus Repository Pro
Nexus Repository Pro has two database options for new and existing users:
- An external PostgreSQL database
- An embedded H2 database
This topic will explain the benefits of the preferred database options and how to use them. Review the following to stand up or migrate your instance:
- Configuring Nexus Repository Pro for H2 or PostgreSQL (for new instances)
- Migrating to a New Database (for migrating existing instances)
- Unsupported formats will not be migrated; you will not be able to add new formats that your new database does not support. Review Feature Availability for PostgreSQL and H2 Databases and ensure that your new database supports all of your formats before attemping the migration.
- Migration is a one-time process; attempts to migrate again will overwrite data.
Choosing a Database Mode
We recommend that all new and existing Nexus Repository Pro deployments use PostgreSQL or H2. Using PostgreSQL will help organizations meet their resiliency, scaling, and business continuity requirements. PostgreSQL should be used for any centralized repository which require fault tollerant deployments.
The table below can help you choose the appropriate database mode for your deployment:
|Database Mode||Appropriate For|
|New: External PostgreSQL |
(Nexus Repository Pro only)
New: Embedded H2
Benefits of an External Database
There are a number of benefits to using an external database:
- Easier to scale deployment; PostgreSQL will be required for planned HA functionality
- Leverage managed, fault-tolerant cloud databases: AWS Aurora, RDS, Azure, etc.
- Improved container orchestration such as Kubernetes and OpenShift
- Fully available during backups
- Support for multi-AZ cloud deployment models
- Simpler and easier disaster recovery
Embedded Mode for Nexus Repository
Nexus Repository provides an embedded-database mode with improved speed using H2 instead of OrientDB. This mode is appropriate for the following scenarios:
- Teams and smaller organizations with non-mission-critical Nexus Repository needs
- Automatically provisioned, disposable Nexus Repository instances (e.g., pools of proxy-only instances used to shield a primary instance from a heavy read load)
Other Database Options Topics