Prepare a Backup

Nexus Repository stores data in blob stores and keeps some metadata and configuration information separately in databases. You must back up the blob stores and metadata databases together. Your backup strategy should involve backing up both your databases and blob stores together to a new location in order to keep the data intact. Complete the steps below to perform a backup:

Blob Store Backup

You must back up the filesystem or object store containing the blobs separately from Nexus Repository.

  • For File blob stores, back up the directory storing the blobs. 
    • For a typical configuration, this will be $data-dir/blobs.  
  • For S3 blob stores, you can use bucket versioning as an alternative to backups. You can also mirror the bucket to another S3 bucket instead.


For cloud-based storage providers (S3, Azure, etc.), refer to their documentation about storage backup options.


Node ID Backup

Each Nexus Repository instance is associated with a distinct ID.  You must back up this ID so that blob storage metrics and Nexus Firewall reports will function in the event of a restore.  The files to back up to preserve the node ID are located in the following location:

$data-dir/keystores/node/​

Database Backup

The databases that you export have pointers to blob stores that contain components and assets potentially across multiple repositories. If you don’t back them up together, the component metadata can point to non-existent blob stores. So, your backup strategy should involve backing up both your databases and blob stores together to a new location in order to keep the data intact.

Here’s a common scenario for backing up custom configurations in tandem with the database export task:

  1. Configure the appropriate backup task to export databases:

    1. Use the Admin - Export databases for backup task for OrientDB databases 

    2. Use the Admin - Backup H2 Database task for H2 databases PRO

  2. Run the task to export the databases to the configured folder.
  3. Back up custom configurations in your installation and data directories at the same time you run the export task.
  4. Back up all blob stores.
  5. Store all backed up configurations and exported data together.


Write access to databases is temporarily suspended until a backup is complete. It’s advised to schedule backup tasks during off-hours.