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.1.0+ instance (or a local instance on Scrutinizer 19.8.0+).

Migration to a headless Replicator instance#

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

View guide

Requirements

Source host - Replicator 19.1.1 appliance
Destination host - Headless Replicator 20.1.0+ appliance that has been registered with the configuration host and deployed
Configuration host - Fully deployed and licensed standalone Replicator 20.1.0+ appliance with at least an evaluation license that supports a minimum of two Replicator instances (configuration host and destination headless instance); can also be the local Replicator instance on a Scrutinizer 19.8.0+ server
Migration utility (Replicator-19-conf-tool.sh) - Download from https://files.plixer.com/plixer-repo/scrutinizer/19.8.0/util/Replicator-19-conf-tool.sh or copy from /home/plixer/scrutinizer/files/ on the configuration host

Migration procedure

SSH to the source host as the root user and create a directory for the migration files:
```
mkdir /tmp/migration
```

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.8.0/util/Replicator-19-conf-tool.sh
chmod 755 /tmp/migration/Replicator-19-conf-tool.sh

Run the utility to create the backup file:
```
cd /tmp/migration
./Replicator-19-conf-tool.sh backup <BACKUP_NAME> <DESTINATION_HOST_IP>
```
This will create the profile data backup file BACKUP_NAME.tar.gz.

Important

The IP address of the destination host must match the IP address provided when the script was run.
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.

Copy the backup file from the source host to the configuration host:

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

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
```
Run the utility on the configuration host to restore the backup file to the destination host:
```
cd /home/plixer/scrutinizer/files/
./Replicator-19-conf-tool.sh restore BACKUP_NAME.tar.gz
```
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.1.0+ appliances by repeating the steps above.

Profile migration

Contents

Profile migration#

Migration to a standalone Replicator instance#

Migration to a headless Replicator instance#