It is required to provision a Target Artifactory instance as follows:
Step 1: Install Artifactory
Install the exact same version of Artifactory that's running on your Source server on the Target server (It may be a different install type). Do not start the Artifactory service yet.
Step 2: Copy The Master Key
- Navigate to $JFROG_HOME/artifactory/var/etc/
- Create a security folder if it doesn't already exist
- Inside the security folder, create a file named master.key if it doesn't exist
- Copy the master key content from your Source server located at: $JFROG_HOME/artifactory/var/etc/security/master.key
- Set appropriate file permissions so the user running Artifactory has full access to the master.key file:
chown -R artifactory:artifactory $JFROG_HOME/artifactory/var/etc/security/
Note
Copying the $JFROG_HOME/artifactory/var/etc/security/master.key is a critical step in the import process - for both single node and HA imports. The master.key is an AES secret key (128 or 256 bit) that is used by Artifactory for encrypting and decrypting the shared data in the database and is, therefore, required for the import process.
Step 3: Configure System Settings
- Configure the system.yaml file with your desired settings, including the database connection details
Location: $JFROG_HOME/artifactory/var/etc/system.yaml - Verify that binarystore.xml is configured according to your requirements.
Step 4: Start and Validate
- Start the Artifactory service
- Insert your Artifactory license
- Confirm that Artifactory starts successfully and is functioning properly
(Optional) Step 5: Configure Garbage Collection
This step is only required if you will use the same external filestore on your source and target instance.
Adjust the Garbage Collection (GC) schedule on both the source and target instances to prevent interference during migration:
-
Navigate to Administration → Artifactory Settings → Maintenance → Garbage Collection
-
Set the GC schedule to run at a time that won't conflict with your migration process
Example cron expression: 0 0 0 ? 2030/1 * (runs starting in 2030)
-
At the end of the migration process, please set back the GC to run regularly (Default: 0 0 /4 * * ?)
Note
Garbage Collection is a vital maintenance procedure in Artifactory meant to ensure the system does not become clogged with unused binaries. Setting such extended intervals is not recommended as part of the day-to-day Artifactory maintenance and should be utilized for the migration period