Redpoint Data Management™ Documentation
Redpoint Data Management™ Documentation
Breadcrumbs

Migrate from one server to another

Overview

This page provides step-by-step instructions on how to migrate an RPDM instance from one machine to another, including the important files that need to be backed up and restored.

We highly recommend that you submit a support ticket at support.redpointglobal.com before the migration to inform the Redpoint Support team and to receive appropriate assistance.

Phase 1: Pre-migration & backup (old server)

These steps focus on preparing the old environment and creating necessary backups before the server transition.

  1. Obtain Installer & Note Version: Obtain the RPDM server installer from Redpoint Support. Note the current version number on the old server you're migrating.

  2. Submit Rehost Form: Complete and submit a rehost form to Redpoint Support.

  3. Disable Automations: On the old RPDM server, disable all automations. Be sure to list or screenshot the automations that need to be re-enabled after the migration.

  4. Create Repository Snapshot: On the old RPDM server, create a snapshot backup of the repository. Review the guide here: Back-up the Repository.

  5. Stop RPDM Services: Stop the RPDM services in the following order: Stop WSP > Exec > Site service. If RPDM is configured with multiple workers (execution servers), stop the Exec services on the workers first.

  6. Back up Key Files: Back up the crypto_keys and the jdbc_drivers folders. Note: Confirm the number of files in the backed-up crypto_keys folder matches the source.

Phase 2: Installation & restore (new server)

This phase covers installing RPDM on the new server and restoring the repository and key files from the backup.

  1. Install RPDM: On the new RPDM server, install RPDM. Ensure that the version matches the old server. If the new environment is a cluster, complete the installation on the workers as well.

  2. Stop RPDM Services: On the new RPDM server, stop the newly installed RPDM services.

  3. Locate Data Directory: Navigate to the RPDM data install directory. (If not sure of the path, check the CoreCfg.properties file for the value of data_directory=).

  4. Rename Existing Folders: Rename the newly installed repository and crypto_keys folders (e.g., to repository_new_install and crypto_keys_new_install).

  5. Copy Snapshot: Copy/move the repository snapshot backup from the old RPDM server to the new RPDM server's data directory.

  6. Rename Snapshot Folder: Rename the snapshot backup folder to repository.

  7. Check Repository Permissions: Review the permissions between the repository_new_install and the repository folder. Update the permissions on the new repository folder to match if needed.

  8. Copy Key Files & Drivers: Copy/move the backed-up crypto_keys and the jdbc_drivers folders from the old RPDM server to the new RPDM server (Site and Workers if running in a cluster). Update the folder permissions to match the source.

Phase 3: Finalization & Validation

  1. Restart RPDM Services: Restart the RPDM services on the new server following this start sequence: Site > Exec > WSP Services on the site server, then Exec Service only on the workers.

  2. Login to Client: Login to the RPDM client on the new server.

  3. Apply License: Apply the Rehost License.

Validation

  • Check repository objects.

  • Check Data Connections.

  • Check Cloud resources (S3, ABS).

  • Check resource maps.

Troubleshooting

If connections to data connections, cloud resources, or resource maps are failing:

  • Review the logs.

  • Review your network configuration.

  • Check if any whitelisting is needed to allow the new RPDM server to connect to your resources.