Skip to main content

Configuring Storage (Legacy)


High Availability Clustering is a legacy feature that only works on the Orient database.

All new deployments should use one of our new high availability or resilient deployment options described in Resiliency and High Availability.

This topic covers HA-C-specific information related to storage.

Choosing a Type for Your Blob Stores

Nexus Repository HA-C stores blobs in shared storage, which can be either a shared file system or a cloud object store.

For HA-C, your blob store location must meet both of the following requirements:

  1. Be outside of the sonatype-work directory

  2. Be read-write accessible by all nodes


Do not copy or share the sonatype-work directory used by your Nexus Repository Manager nodes. Each node must be allowed to initialize its own private sonatype-work directory; data generated on first run is unique to each instance.

Your shared file systems, if File based, must exist outside of the sonatype-work directory.

File Systems to Avoid

Using the File Blob Store with Nexus Repository HA-C relies on POSIX semantics. The following file systems are known to be unreliable:

  1. glusterfs

  2. FUSE based user space filesystems

Determining a Backup Solution

Backing up your blob store file systems is covered in detail in the Designing your Cluster Backup/Restore Process section.


Your next step is to review your network configuration with Configuring Hazelcast.