Nexus Repository Manager 2 cleanup post upgrade from version 2.x to 3.x

[Jason Stanley]

I am in the process of testing out an upgrade of Nexus from version 2.x to version 3.x.

During the upgrade process, I choose the "File System Hard Linking" for a transfer method (description below).

In this transfer method, version 2 tells version 3 the path of the file content to transfer and a file system hard link to the same content is created. This upgrade method works if versions 2 and version 3 are configured to access the same storage system on identically named mount points and hard linking is supported by the file system used. It is the fastest transfer method.

The upgrade appeared to succeed and I am now onto the post upgrade steps.

One of the steps:

• Archiving Nexus Repository Manager 2 and delete the install from the server.

Is the Nexus Repository Manager 2 the nexus directory located under the sonatype-work directory?

Can I archive the nexus directory and free up 178G of space?

du -hs * 
178G nexus 
26G nexus3 

Thanks

[Rich Seddon]

Once you've run Nexus 3 for a bit and are confident it is working for you then yes, you can archive the sonatype-work/nexus directory from Nexus 2.

Note that because you used the hard linking method the files under sonatype-work/nexus/storage were not copied, instead Nexus 3 has hard links to them in it's blob storage.  This means that when you remove sonatype-work/nexus you won't reclaim the space in sonatype-work/nexus/storage. Since the files are hard linked from both locations you'll just be removing the hard links from the nexus 2 storage directory.  But the rest of the space in the nexus directory will be reclaimed.

RIch