Migrating configuration data to a Plixer Scrutinizer 19.5.0+ server on the same version

Follow the steps below to migrate/restore configuration data and user preferences from a configuration backup file on a source Plixer Scrutinizer 19.5.0+ server to a destination server on the same version.

Note

Configuration migrations only include configuration data for the Plixer Scrutinizer application. Settings that are applied to the appliance itself, such as custom listening ports, will need to be manually re-applied on the destination server after the migration.

1. On the source server, create a temporary role for migrations in the Plixer Scrutinizer database:

   psql -c "CREATE USER migrator WITH SUPERUSER ENCRYPTED PASSWORD '<PASSWORD>'"
   

2. Allow migration connections from the destination’s IP address:

   DESTINATION=DESTINATION_IP
   sudo sed -i -e "1ihost plixer migrator $DESTINATION/32 md5" /var/db/big/pgsql/data/pg_hba.conf
   psql -c "SELECT pg_reload_conf()"
   

3. On the destination server, verify that a license has been added and flows are already being received, and then update /etc/migrate.ini with the details of the source server and temporary migration role.

4. Stop the flow collection service and start the migration operation:

   SOURCE=SOURCE_IP
   scp $SOURCE:/etc/plixer.key /etc/plixer.key
   sudo systemctl stop plixer_flow_collector
   scrut_util --migrate restore
   

5. [Optional] Migrate historical data to the destination server:

   scrut_util --migrate data
   

6. Restart the flow collection service:

   sudo systemctl start plixer_flow_collector
   

7. Remove the hba rule and temporary migrator role from the source server:

   sudo sed -i '/migrator/d' /var/db/big/pgsql/data/pg_hba.conf
   psql -c "SELECT pg_reload_conf()"
   psql -c "DROP ROLE migrator"
   

After the operation, access the web interface on the destination server and verify that all configuration data and user preferences have been successfully migrated. If historical data was also migrated, run any report to confirm that the operation was successful.

Migration from a specified backup file

To use a different configuration backup file (instead of the default /tmp/conf.dump) for the migration, add the --dump_file option as follows:

scrut_util --migrate restore --dump_file BACKUP_FILE