System Migration Process

ARTIFACTORY: Migration Basics

AuthorFullName__c
Shani Attias
articleNumber
000005194
ft:sourceType
Salesforce
FirstPublishedDate
2022-01-03T10:17:17Z
lastModifiedDate
2024-03-10T07:43:51Z
VersionNumber
9

Full system migration includes migration of each of the above components to a new location.

  • Application Server migration is done by a fresh installation of the Artifactory server on a new location.
  • DB (Data) migration DB (Data) migration should be done by performing a full System Export (while checking the "Exclude Content" checkbox) & Import (This time, do NOT check the "Exclude Content" box). In this case, only data that is saved in the DB is migrated, the artifacts themselves will not be migrated.
  • Filestore migration is done by copying the entire data folder to the new location

*** There is an option to migrate the DB and filestore together by performing a full System Export & Import. However, if you have a large instance and require minimal downtime, the recommended migration options are described here

In the described methods, we need a new DB and manually copy the filestore to the new instance as this includes all the binaries.
The reason we are using a new DB for this process is to prevent conflicts with existing data.
We will also do a full system Export & Import (exporting with “Exclude Content” as we have already migrated the binaries). This will populate the DB with the binaries references and will also import Artifactory and Access configurations.
Artifactory configurations refer to Artifactory Skelton configurations such as repositories, replications, Authentication providers (LDAP, SAML...), etc. 
Access configuration refers to Users, Groups, Permissions, and Access Tokens.
If you only need to import Access data, you may refer to this Knowledge Base.