Migrate setup and configuration

This page contains the following information:

Note: Please note that this should be performed under the guidance of your CX data migration specialist.

Migrate network setup

Refer to RelativityOne network access for comprehensive information on RelativityOne network setup information.

If you plan to use Relativity Migrate, you must allow port 445, 443 traffic to relevant DNS URL (the specific URL you allow should correspond to the Azure region your RelativityOne instance is in). The ports need to be opened on Agent Server only.

Region

Region short

Cosmos DB DNS name

File share DNS name

Australia East

auea

dm-cosmos-db-prod-auea.documents.azure.com

dmsafsprodauea09alf6.file.core.windows.net

Brazil South

brso

dm-cosmos-db-prod-brso.documents.azure.com

dmsafsprodbrso4j71lb.file.core.windows.net

Canada Central

cact

dm-cosmos-db-prod-cact.documents.azure.com

dmsafsprodcact1j4qrq.file.core.windows.net

Switzerland North

chno

dm-cosmos-db-prod-chno.documents.azure.com

dmsafsprodchnoc79zmm.file.core.windows.net

Central US

ctus

dm-cosmos-db-prod-ctus.documents.azure.com

dmsafsprodctuszezqxk.file.core.windows.net

Germany West Central

dect

dm-cosmos-db-prod-dect.documents.azure.com

dmsafsproddectil29ua.file.core.windows.net

East Asia

esas

dm-cosmos-db-prod-esas.documents.azure.com

dmsafsprodesaskigrwz.file.core.windows.net

East US

esus

dm-cosmos-db-prod-esus.documents.azure.com

dmsafsprodesusfz7kos.file.core.windows.net

Korea Central

krct

dm-cosmos-db-prod-krct.documents.azure.com

dmsafsprodkrcthxep4x.file.core.windows.net

Southeast Asia

seas

dm-cosmos-db-prod-seas.documents.azure.com

dmsafsprodseasaog6hz.file.core.windows.net

UK South

ukso

dm-cosmos-db-prod-ukso.documents.azure.com

dmsafsproduksomwqkfp.file.core.windows.net

West Europe

wseu

dm-cosmos-db-prod-wseu.documents.azure.com

dmsafsprodwseusbp5bo.file.core.windows.net

UAE North aeno dm-cosmos-db-prod-aeno.documents.azure.com dmsafsprodaenoh3hm08.file.core.windows.net
North Europe noeu dm-cosmos-db-prod-noeu.documents.azure.com dmsafsprodnoeubwkqm1.file.core.windows.net
Central India inct dm-cosmos-db-prod-inct.documents.azure.com dmsafsprodinctxob00a.file.core.windows.net

Installing and configuring Migrate (RelativityOne)

  1. You need to set the Migrate restore locations by entering values into Value fields for the following instance settings in the Relativity.Migrate section:

    Note: When configuring your Migrate application instance settings in RelativityOne, contact CX to assist.

    • Resource Pool(RelativityOne) -To locate Artifact ID for ResourcePoolID , check the Server & Agent Management > Resource Pools tab.
    • Note: You may need to add ArtifactID column to your view.

    • CacheLocationId- Use the Cache Location Server artifactId associated to the Resource Pool selected above.
    • DatabaseServerId- Use the SQL - Distributed artifactId associated to the Resource Pool selected above.
    • FileRepositoryId- Use the Fileshare artifactId associated to the Resource Pool selected above.
    • Note: To locate Artifact ID for CacheLocationID / DatabaseServerID / FileRepositoryID, check the Server & Agent Management > Servers tab.

  2. Add an OAuth2 Client for the Migrate application.
    • Navigate to the OAuth2 Client tab in RelativityOne.
    • Click Create New OAuth2 Client.
      • Name- Please note this field only supports alpha-numeric characters.
      • Flow Grant Type- Client Credentials
      • Context User- this must be an active system administrator
      • Access Token Lifetime- 100
    • Click Save.
    • Copy the Client ID value and the Client Secret values as they will be needed later in the configuration.

Installing and configuring Migrate (Relativity Server)

Note: Migrate will support Relativity Server 9.6 until 09/30/2021 and Relativity Server 9.7, 10.0 and 10.1 until 12/31/2021. Starting 1/1/2022 the minimum Relativity Server version supported by Migrate will be Relativity Server 10.3. Migrate will continue to be compatible with unsupported Relativity Server versions for 3 months after the version support ends. For example, Relativity Server 10.3 version support ends on March 24, 2022, so Migrate will support Relativity Server 10.3 until June 24, 2022. Starting June 25, 2022 customers using Relativity Server 10.3 will not be able to use Migrate. They would either need to upgrade to a newer Relativity Server version or use ARM and RelativityOne Staging Explorer for data migration.

  1. Download the latest following RAP files located in the Relativity Applications folder from the Community site.

  2. Install the Migrate.Server RAP file to your Relativity Server instance.
  3. Add the following agents (one agent required for each as any additional one will not improve performance).
    • Migrate - Supervisor Agent

    • Migrate - Workspace Crawler Agent

    • Migrate - Archive Builder Agent

    • Migrate - Migration Data Sender Agent

  4. Set the following Migrate instance setting:

    • Name - ArchiveFileSharePath

    • Section - Relativity.Migrate

    • Field Type - String

    • Value - represents the file location for your ARM archives.

  1. Add the following credentials on the Credential tab:

    Note: If the Credential tab is not visible, go to Tabs permissions and set the Is Visible toggle.

  1. Install the Archive Tool application to your Relativity Server instance from the provided RAP file.

  2. Create the Archive Tool Agent agent.

  3. Set the BCP path to the SQL Primary server, by navigating to the Servers tab of your on-premise instance.

  4. Set archive tool configuration by entering the following Migrate instance setting:

    • Name - Diagnostics

    • Section - Relativity.ArchiveTool

    • Field Type - True/False

    • Value - True

Note: Downloading, installing and configuring the Migrate Server RAP file is only needed during the first installation. Relativity will auto-update the Migrate Server RAP file whenever a newer version is available. The auto-update function can be disabled on request by contacting the RelativityOne Customer Experience team. If this function is disabled, Migrate may become inaccessible when a newer version is available. In order to use Migrate, a manual installation will be needed as per the instruction above.