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: Perform full system export with the "Exclude Content" option selected (no other options assigned)
4. New server: Perform full system import (DO NOT select the Exclude Content option)
5. Old Server: Set up all local repositories to replicate the repositories on the new server (you may disable the ‘sync delete’ checkbox if needed)
6. New server: Turn on network traffic/switch DNS to the new server
7. Old server: Execute and complete all replication jobs
8. Old server: Shut down
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.
4. New server: Perform full system import (DO NOT select the Exclude Content option)
5. Old Server: Set up all local repositories to replicate the repositories on the new server (you may disable the ‘sync delete’ checkbox if needed)
6. New server: Turn on network traffic/switch DNS to the new server
7. Old server: Execute and complete all replication jobs
8. Old server: Shut down
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.
If you need to roll back, reverse the replication from the new to the old and switch your DNS to the old server. You could also set this up anyway if you need a Disaster Recovery server.
Remember that we highly recommend testing the environment before switching to the new setup. Before switching production traffic to the new setup, verifying the configuration and functionality of the new environment is highly recommended.
In addition, the master key might be overridden during the export/import process; hence, saving it aside before you start is recommended so you can restore it if needed.
A screencast for this procedure can be found in this video.