(Recommended) Option 1: Perform a System Level Import and Export
Before migration, it is recommended to perform a System Level Import and Export. Artifactory can export and import the entire Artifactory server, including configuration, security information, stored data, and metadata. The format used is identical to the System Backup format. This is useful when running manual backups and for migrating and restoring a complete Artifactory instance (as an alternative to using database level backup and restore).
- In the JFrog Platform, click the Administration tab, then navigate to Artifactory > Import & Export > System.
- In the Export System field, enter a location on the pod (
/opt/jfrog/artifactory/var/backup
), for the old release, then click Export. - Install the Platform chart as a new release and copy the exported file to a location (
/opt/jfrog/artifactory/var/backup
). - Export the file from the Platform chart UI.
Option 2: For Advanced Users - Linking the Old PersistentVolumeClaim (PVC)
If an existing installation has a lot of data, manually importing, and exporting may take a lot of time. Therefore, you will want to link to the old PVC to save this time (advanced users only).
Artifactory Single Node
- Link the old PVC of the Artifactory chart to the new JFrog Platform chart release.
- Enable the Artifactory subchart in the JFrog Platform release, and then perform a Helm upgrade. The old PVC should be provided as an existing claim.
Create a
custom-values.yaml
file with the following configuration.global: initDBCreation: false postgresql: enabled: false rabbitmq: enabled: false redis: enabled: false artifactory: enabled: true artifactory: persistence: enabled: true existingClaim: artifactory-volume-<OLD RELEASE NAME>-artifactory-0 artifactory-ha: enabled: false xray: enabled: false distribution: enabled: false mission-control: enabled: false pipelines: enabled: false helm upgrade --install jfrog-platform stable/jfrog-platform -f custom-values.yaml
Verify that the upgrade and old Helm release can be uninstalled. Make sure that the old PVC is not removed.
Artifactory HA
Important
When installing the JFrog Platform chart, make sure to use the <old-release-name>
. This will reuse the existing PVCs of the old release.
Reuse the old PVC of the Artifactory chart in the new JFrog Platform chart release.
The Artifactory HA chart does not have the option of providing an existing claim name for the PVC; instead you will need to create a PVC using a defined name. For more information, see Using an Existing Volume Claim in Helm Charts for Advanced Users.- Uninstall the existing release using
helm uninstall <old-release-name>
. This will uninstall everything except the PVCs; PVCs can exist with names such as volume-<old-release-name>
-artifactory-ha-primary-0
andvolume-<old-release-name>-artifactory-ha-member-<ordinal-number>
, depending upon the number of node replica sets defined. - Enable the Artifactory subchart in the JFrog Platform release and perform a Helm upgrade.
Create a
custom-values.yaml
file with the following configuration.global: initDBCreation: false postgresql: enabled: true rabbitmq: enabled: false redis: enabled: false artifactory: enabled: false artifactory-ha: enabled: true xray: enabled: false distribution: enabled: false mission-control: enabled: false pipelines: enabled: false helm upgrade --install <old-release-name> stable/jfrog-platform -f custom-values.yaml