Profile migration

Profile migration#

Profile configuration data from a Replicator 19.1.1 appliance can be migrated to a Replicator 20.0.0+ instance using the configuration migration tool included with standalone deployments.

Note

Profile data is automatically migrated when a Replicator deployment is upgraded from v19.1.1 to v20.0.0+.

Migration to a standalone Replicator instance#

The following instructions cover profile data migration from a v19.1.1 deployment to a v20.0.1 standalone instance.

View guide

Requirements

  • Source host - v19.1.1 Replicator appliance

  • Destination host - Fully deployed and licensed standalone Replicator 20.0.1 deployment; must have the same IP address as the migration source

  • Temporary host - A temporary location to use for moving files between the source and destination hosts

  • Migration utility (Replicator-19-conf-tool.sh) - Located in /home/plixer/scrutinizer/files/ on the configuration host

Migration procedure

  1. SSH to the source host as the replicator user and shut it down:

    REPLICATOR> system shutdown

  2. After the source host has been completely shut down, deploy the destination host and assign it the same IP address as the source host.

  3. SSH to the destination host as the plixer user and apply the correct permissions to the utility:

    chmod 755 /home/plixer/scrutinizer/files/Replicator-19-conf-tool.sh

  4. Copy the utility to a temporary host:

    scp /home/plixer/scrutinizer/files/Replicator-19-conf-tool.sh USER@TEMP_HOST_IP:/replicator/

  5. Shut down the destination host:

    scrut_util --system shutdown

  6. Boot up the source host and copy the utility from the temporary host to the source host:

    scp /replicator/Replicator-19-conf-tool.sh replicator@SOURCE_HOST_IP:/tmp/migration/

  7. SSH to the source host as the root user and use the utility to create a backup of its profile data (BACKUP_NAME.tar.gz):

    cd /tmp/migration
./Replicator-19-conf-tool.sh backup <BACKUP_NAME>

  8. Verify the contents of the backup file:

    tar -vztf BACKUP_NAME.tar.gz
ls -l /home/replicator/v19_backup

    The files should not be empty and have the same size.

  9. Copy the backup file to the temporary host, and then shut down the source host:

    scp BACKUP_NAME.tar.gz USER@TEMP_HOST_IP:/replicator/
su replicator
REPLICATOR> system shutdown

  10. Boot up the destination host and copy the backup file from the temporary host to the destination host:

    scp /replicator/BACKUP_NAME.tar.gz plixer@DESTINATION_HOST_IP:/home/plixer/scrutinizer/files/

  11. Use the utility to restore the backup file on the configuration host:

    cd /home/plixer/scrutinizer/files/
./Replicator-19-conf-tool.sh restore BACKUP_NAME.tar.gz

  12. Navigate to the Replicator UI on the destination host and verify that the profile data was successfully restored.

After the migration has been completed, the Replicator service should be updated with the new profile configuration data and start replication within one minute.

Migration to a headless Replicator instance#

The following instructions cover profile data migration from a v19.1.1 deployment to a v20.0.0+ headless Replicator instance.

View guide

Requirements

  • Source host - v19.1.1 Replicator appliance

  • Destination host - Headless Replicator 20.0.1 instance registered and deployed with the same IP address as the migration source after the latter has been backed up and shut down

  • Configuration host - Fully deployed and licensed standalone Replicator 20.0.1 deployment with at least an evaluation license; license must support at least two instances (configuration host and destination headless instance)

  • Migration utility (Replicator-19-conf-tool.sh) - Located in /home/plixer/scrutinizer/files/ on the configuration host

Migration procedure

  1. SSH to the configuration host as the plixer user and apply the correct permissions for the utility:

    chmod 755 /home/plixer/scrutinizer/files/Replicator-19-conf-tool.sh

  2. Copy Replicator-19-conf-tool.sh to the migration source:

    scp /home/plixer/scrutinizer/files/Replicator-19-conf-tool.sh replicator@SOURCE_HOST_IP:/tmp/migration/

  3. SSH to the source host as the root user and use the utility to create a backup of its profile data (BACKUP_NAME.tar.gz):

    cd /tmp/migration
./Replicator-19-conf-tool.sh backup <BACKUP_NAME>

  4. Verify the contents of the backup file:

    tar -vztf BACKUP_NAME.tar.gz
ls -l /home/replicator/v19_backup

    The files should not be empty and have the same size.

  5. Copy the backup file to the configuration host, and then shut down the source host:

    scp BACKUP_NAME.tar.gz plixer@DESTINATION_HOST_IP:/home/plixer/scrutinizer/files/
su replicator
REPLICATOR> system shutdown

  6. On the configuration host, navigate to Admin > Resources > Replicators and register the destination host.

  7. Deploy the destination host appliance and assign it the same IP address previously used by the source host.

  8. Navigate to Admin > Resources > Replicators again and verify that the destination Replicator instance has self-registered and has the correct IP address.

  9. Restore the backup file on the configuration host:

    cd /home/plixer/scrutinizer/files/
./Replicator-19-conf-tool.sh restore BACKUP_NAME.tar.gz

  10. Navigate to the Replicator UI on the configuration host and verify that the restored profile data was correctly associated with the destination Replicator instance.

After the migration has been completed, the Replicator service should be updated with the new profile configuration data and start replication within one minute.

Hint

Profile data from multiple pre-v20.0.0 Replicator instances can be migrated to new Replicator 20.0.0+ headless instances by repeating the steps above and deploying each destination host with an IP address matching a source.

Contents