- Sonatype Help
- Sonatype Nexus Repository
- Planning Your Implementation
- Storage Guide
- Migrating to Shared Blob Storage
Migrating to Shared Blob Storage
Note
Only available in Sonatype Nexus Repository Pro. Interested in a free trial? Start here.
NEW IN 3.50.0
If you require shared blob storage (e.g., for a highly available deployment), you will need to use external tools to copy existing blobs for all repositories to a new shared blob store location. This can be done using vendor-provided tools like those described in Migrating from an On-Premises Blob Store to a Cloud Blob Store, rsync copy, etc.
In the existing Sonatype Nexus Repository instance UI navigate to Administration → Blob Stores and select the existing unshared blob store that you wish to point to the shared location.
Change the path of your existing blob store to point to the new location.
Freeze your existing Sonatype Nexus Repository instance by making it read-only.
Note
Freezing your instance is required because the new shared blob store location must be empty when you change an existing blob store location in your Sonatype Nexus Repository instance to a new shared location as described below.
Navigate to Administration → System → Nodes.
Select Enable read-only mode.
See the Nodes topic for more information on read-only mode.
Copy the blobs to the new shared location using one of the tools described above (e.g., rsync copy, vendor-provided tools, etc.)
Unfreeze your existing Sonatype Nexus Repository instance.
Navigate to Administration → System → Nodes.
Select Disable read-onlymode.
If you want to minimize downtime, you can perform an initial copy to copy blobs to a temporary location (e.g., a temporary directory on the shared server); this can not be the new permanent shared blob store location.This will allow the new shared blob store to remain empty so that you can connect it to the existing Sonatype Nexus Repository instance.
You will then need to freeze your instance and then perform the steps above, including a second copy to capture any changes to the blob store that took place between your initial copy and freezing the instance.