Skip to main content

Deciding on a Data Transfer Method

When performing the upgrade from Nexus Repository 2 to 3, there are three data transfer methods from which you must choose: HTTP downloading, file system copying, or file system hard linking. Each method has its own pros, cons, and requirements as detailed below.

Data Transfer Method

Description

Pros

Cons

Requirements

File System Hard Linking (Preferred)

Nexus Repository 2 tells Nexus Repository 3 the path of the file content to transfer. Nexus Repository 3 then creates a file system hard link to the same content. Data is not duplicated

  • The fastest method

  • Saves storage space

Nexus Repository 2 and 3 must be installed on the same server

  • Nexus Repository 2 and 3 must be configured to access the same storage system on identically named mount points.

  • The file system must support hard linking.

  • There must be adequate file handles for both Nexus Repository 2 and 3.

File System Copying

Nexus Repository 2 provides Nexus Repository 3 with the necessary path to file content, which Nexus Repository 3 then copies.

  • Faster than HTTP downloading

  • Less impact on performance of Nexus Repository 2

Not as fast as hard linking

  • Nexus Repository 2 and 3 must be configured to access the same storage system on identically named mount points.

  • You must ensure you have enough storage space; upwards of double the original storage space will be needed at least temporarily during data duplication.

HTTP Downloading

Nexus Repository 3 makes HTTP requests to Nexus Repository 2 to transfer configuration and data.

The only method that works for situations where Nexus Repository 2 and 3 are on different machines and do not share access to the same file system storage

The slowest option

  • You must ensure you have enough storage space; upwards of double the original storage space will be needed at least temporarily during data duplication.