Profile migration

Profile migration#

Profile configuration data from a Replicator 19.1.1 server can be migrated to a different Replicator 20.0.0+ appliance/instance using the migration utility included with standalone Replicator appliances and Plixer One/Scrutinizer deployments.

Note

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

The following Replicator 20.0.0+ deployment types are supported as migration destinations:

  • Standalone appliances

  • Headless appliances

  • Local instances on Scrutinizer

Migration to a standalone Replicator instance#

The following instructions cover profile data migration from a Replicator 19.1.1 server to a standalone Replicator 20.0.2+ instance (or a local instance on Scrutinizer 19.7.2+).

View guide

Requirements

  • Source host - Replicator 19.1.1 appliance

  • Destination host - Fully deployed and licensed standalone Replicator 20.0.2+ deployment (or local instance on Scrutinizer 19.7.2+)

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

  • Migration utility (Replicator-19-conf-tool.sh) - Download from https://files.plixer.com/plixer-repo/scrutinizer/19.7.2/util/Replicator-19-conf-tool.sh or copy from /home/plixer/scrutinizer/files/ on the destination host

Important

Profile data can only be migrated between source and destination hosts with the same IP address.

Migration procedure

  1. SSH to the source host as the root user and create a directory for the migration files:

    mkdir /tmp/migration

  2. Download the migration utility and apply the necessary permissions:

    curl -o /tmp/migration/Replicator-19.conf-tool.sh https://files.plixer.com/plixer-repo/scrutinizer/19.7.2/util/Replicator-19-conf-tool.sh
chmod 755 /tmp/migration/Replicator-19-conf-tool.sh

    Note

    If the source host cannot access the Internet, the utility can be copied from the destination host via the temporary host.

  3. Run the utility to create the backup file:

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

    This will create the profile data backup file BACKUP_NAME.tar.gz.

  4. Verify the contents of the backup file:

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

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

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

    scp BACKUP_NAME.tar.gz USER@TEMP_HOST_IP:/DESTINATION_DIR/BACKUP_NAME.tar.gz
shutdown -p now

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

  7. Copy the backup file from the temporary host to the destination host:

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

  8. 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

  9. Run the utility to restore the backup file on the destination host:

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

  10. 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 headless Replicator 20.0.2+ instance.

View guide

Requirements

  • Source host - v19.1.1 Replicator appliance

  • Destination host - Headless Replicator 20.0.0+ instance registered with the configuration host and deployed

  • Configuration host - Fully deployed and licensed standalone Replicator 20.0.0+ 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) - Download from https://files.plixer.com/plixer-repo/scrutinizer/19.7.2/util/Replicator-19-conf-tool.sh or copy from /home/plixer/scrutinizer/files/ on the configuration host

Important

The destination host must be deployed with the same IP address as the source host after the backup file has been created and the source host has been shut down.

Migration procedure

  1. SSH to the source host as the root user and create a directory for the migration files:

    mkdir /tmp/migration

  2. Download the migration utility and apply the necessary permissions:

    curl -o /tmp/migration/Replicator-19.conf-tool.sh https://files.plixer.com/plixer-repo/scrutinizer/19.7.2/util/Replicator-19-conf-tool.sh
chmod 755 /tmp/migration/Replicator-19-conf-tool.sh

    Note

    If the source host cannot access the Internet, copy the utility from the configuration host:

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

  3. Run the utility to create the backup file:

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

    This will create the profile data backup file BACKUP_NAME.tar.gz.

  4. Verify the contents of the backup file:

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

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

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

    scp BACKUP_NAME.tar.gz plixer@CONFIGURATION_HOST_IP:/home/plixer/scrutinizer/files/BACKUP_NAME.tar.gz
shutdown -p now

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

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

  8. SSH to the configuration host as the plixer user and apply the necessary permissions to the utility:

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

  9. Run the utility to restore the backup file to the destination host:

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

  10. Navigate to the Replicator UI/page on the configuration host and verify that the profile data was successfully restored and associated with the destination headless 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 19.1.1 Replicator instances can be migrated to new headless Replicator 20.0.0+ appliances by repeating the steps above and deploying each destination host with an IP address matching a source.

Contents