SQL Server to SQL Server data migration

The SQL Server to SQL Server migration process involves moving data from one SQL Server (the source) to another (the target.) This process applies to EDDS, distributed, and Invariant SQL Servers. You can also use this methodology when migrating to the cloud.

Note: If you are also planning a new installation of Relativity, see the Relativity installation documentation for detailed steps. This document assumes you have Relativity installed and are now ready to focus on migrating your data to a new or refurbished server.

Staffing and downtime

Staffing for this data migration project primarily falls on your organization's IT staff. System and database administrators prepare the target server by installing and configuring hardware and software prerequisites before migrating data. The downtime for the data migration depends on the database file sizes and your network's bandwidth and speed for transferring large files. We recommend you plan for at least one full weekend of outage.

You will migrate your Relativity data during a time when there are no users logged into Relativity and no jobs running. Typically, this takes place on a weekend or after hours. Downtime includes:

  • Stopping services on the source server.
  • Copying Relativity-specific databases to the target server.
  • Restarting services on the target server.
  • Post-migration configurations on the target server.

Again, there is no hard and fast rule for how long this process takes, as it depends on database file sizes, network bandwidth, and speed. Still, it is a good idea to plan for more time than you would typically expect so that you have time for resolving issues, should any arise.

Pre-migration - new SQL Server

Perform the pre-installation steps for the target database server using the Database server setup instructions found in the Pre-installation documentation. Confirm you have configured the necessary user accounts and permissions. Steps include:

  • Required Windows software
  • Required SQL Server software
  • Required .NET software
  • Configuring distributed transactions
  • Creating SQL Server admin and system accounts
  • Creating shared folders

Source: Pre-installation documentation

Prepare the target SQL Server for data migration

After you complete the database server setup, you can move to configure the SQL Server for the data migration. Take care to follow the instructions exactly when creating accounts and passwords. An overview of the steps involved include:

  • Whitelisting and registering the SQL Server with the Relativity Secret Store.
  • Creating linked servers if using a distributed SQL Server installation.
  • Exporting the authentication token-signing certificate.

Source: Relativity Server 2023 - EDDS Migration Guide

Data migration - new SQL Server

Ensure no users are logged in to Relativity or jobs running during the data migration. The amount of downtime depends on the database file size, along with your network bandwidth and speed. In general, plan for 8-12 hours to migrate your data to the new server. An overview of the steps involved include:

  • Stopping services and processes.
  • Configuring the master key password.
  • Copying the Relativity databases to the target server.

    Note: You can copy and restore databases using protocols such as log shipping or backup and restore. The method you use to migrate data is flexible so long as the data is completely restored to the target server.

  • Running various scripts for updating paths, server names, and resolving orphaned users.
  • Converting the source server to a distributed server.
  • Rerunning the Relativity installer in repair mode, then restarting services.
  • Migrating the Secret Store database.
  • Migrating workspace databases.

Source: Relativity Server 2023 - EDDS Migration Guide

Pre-migration - distributed SQL Server

This section provides an overview of the server-to-server data migration process when migrating from one server (the source) to another server (the target) within a distributed environment. Initially, the source server is the primary until the migration is completed. The target server becomes the primary, while the source server is reinstalled as a distributed server. Steps include:

  • Managing the authentication token-signing certificate on the source server.
  • Importing the authentication token-signing certificate on the target server.

Data migration - distributed SQL Server

Ensure no users are logged in to Relativity or jobs running during the data migration. The amount of downtime depends on the database file size, along with your network bandwidth and speed. In general, plan for 8-12 hours to migrate your data to the new server. An overview of the steps involved include:

  • Stopping services and processes.
  • Configuring the master key password.
  • Uninstalling Relativity from the target server.
  • Reinstalling Relativity on the target server as a primary SQL Server role.
  • Copying the Relativity databases to the target server.

    Note: You can copy and restore databases using protocols such as log shipping or backup and restore. The method you use to migrate data is flexible so long as the data is completely restored to the target server.

  • Updating the Database Master Key (DMK) and resolving orphaned users.
  • Swapping distributed and primary server types for the source and target servers.
  • Running scripts updating paths.
  • Converting the source server to a distributed server.
  • Update views and procedures so they reference the new target server name.
  • Rerunning the Relativity installer in repair mode, then restarting services.
  • Migrating the Secret Store database.
  • Migrating workspace databases.

Source: Relativity Server 2023 - EDDS Migration Guide

Pre-migration – new Invariant SQL Server

Perform the pre-installation steps for the target database server using the Database server setup instructions found in the Pre-installation documentation. Confirm you have configured the necessary user accounts and permissions. Steps include:

  • Required Windows software
  • Required SQL Server software
  • Required .NET software
  • Configuring distributed transactions
  • Creating SQL Server admin and system accounts
  • Creating shared folders

Source: Pre-installation documentation

Prepare the target Invariant SQL Server for data migration

After you complete the database server setup, you can move to configure the SQL Server for the data migration. Take care to follow the instructions exactly when creating accounts and passwords. The steps involved include whitelisting and registering the SQL Server with the Relativity Secret Store.

Source: Relativity Server 2023 - EDDS Migration Guide

Data migration – new Invariant SQL Server

Ensure no users are logged in to Relativity or jobs running during the data migration. The amount of downtime depends on the database file size, along with your network bandwidth and speed. In general, plan for 8-12 hours to migrate your data to the new server. An overview of the steps involved include:

  • Stopping services and processes.
  • Copying the Invariant databases to the target server.

Note: You can copy and restore databases using protocols such as log shipping or backup and restore. The method you use to migrate data is flexible so long as the data is completely restored to the target server.

  • Rerunning the Invariant installer in repair mode, then restarting services.
  • Running various scripts for updating paths, server names, and resolving orphaned users.
  • Migrating the Secret Store database.

Source: Relativity Server 2023 - Migrating the Invariant Databases

Resources

Support

Contact Relativity Support directly for the quickest response to your migration questions and troubleshooting.