Method 1:

ARTIFACTORY: What is the best way to migrate a large Artifactory instance with minimal downtime?

AuthorFullName__c
Nir Shervi
articleNumber
000001281
ft:sourceType
Salesforce
FirstPublishedDate
2016-10-06T13:38:06Z
lastModifiedDate
2024-03-10T07:43:50Z
VersionNumber
17
1. At the UI, implement the following directories:
  • In Artifactory 7.X - Admin tab -> Artifactory -> Maintenance -> ‘Garbage Collection’ section.
  • In Artifactory 6.X - Admin tab -> Advanced -> Maintenance -> ‘Garbage Collection’ section
In the Garbage Collection section, edit the ‘Cron Expression’ to schedule the next GC run time far enough so that it won't occur during migration on both servers.
2. Old server: Copy the filestore folder to the new server's filestore folder:
  • In Artifactory 7.X - $JFROG_HOME/artifactory/var/data/artifactory/filestore
  • In Artifactory 6.X - $JFROG_HOME/artifactory/data/artifactory/filestore 
3. Old server: Take the server off the network to block new requests
4. Old server: Perform full system export with the "Exclude Content" option selected (no other options assigned)
5.  Old server: Shut down
6. Old Server: resync from the filestore folder to the new server's filestore folder
7. New server: Perform full system import (DO NOT select the Exclude Content option).
8. New server: Turn on network traffic/switch DNS to the new server
9. New Server: At the UI, access the Garbage Collection section, which its location is described above, and edit the ‘Cron Expression’ to the desired values.

Method 1 is fast, as it only has downtime from the final resync and the export/import of metadata. Method 2 will give close to zero downtime but is more complicated.