Migrating historical data

Follow the steps below to migrate historical data from a source Plixer Scrutinizer 18.20+ (CentOS) server to a destination server on v19.5.0 or higher (Oracle Linux).

Note

• For source servers on 18.20, the psql commands below must be modified to use the root user (psql -c -> psql -Uroot plixer -c…).

• To maintain reporting continuity after the migration, the destination server should be collecting flows from the same exporters as the source.

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 Plixer Scrutinizer 19.5.0+ 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 data
   

5. Restart the flow collection service:

   sudo systemctl start plixer_flow_collector
   

6. 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 run any report to verify that the historical data was successfully migrated.

Reverting a historical data migration

Run the following on the destination server to revert a previous historical data migration:

scrut_util --migrate revert