Migrate Stats Collectors to 9.6.0 On-Prem Orchestrator

If you are upgrading an on-prem Orchestrator deployment to Orchestrator 9.6.0 or later, your statistics data will not be migrated automatically from the Distributed Stats Collector to the new Stats Collector that runs on a single virtual instance. You must manually migrate the statistics from your local and distributed stats collectors to the new Stats Collector after you upgrade to 9.6.0.

NOTE: If you are upgrading an Orchestrator-as-a-Service (OaaS) deployment to 9.6.0, you do not need to migrate your statistics data.

If you are upgrading an EdgeConnect to 9.6.0.0 or later, no additional steps are required.

IMPORTANT: Do not upgrade to Orchestrator 9.6.0 or later if you do not want to migrate to the new Stats Collector.

What Is Migrated?

All historical statistics data will be migrated with the following exceptions:

  • Minute Stats will not be migrated.

  • Stats will not be migrated for reports generated from the Support menu.

  • Peak values will not be migrated for tunnels. Only the source statistics will be migrated (no data will display on the remote side) due to changes in the database schema.

Before You Begin

  • Back up the local Stats Collector and any Distributed Stats Collectors (DSCs). You can schedule a backup or use the CLI to back up Stats Collector on-demand.

    To back up the Stats Collector with the CLI, log in to the CLI and run the following commands:

    cd /home/gms/sc

    ./sc_backup.sh

    The script creates a sc.zip file in the /home/gms/ directory.

  • Upgrade Orchestrator VM to Rocky Linux before upgrading to Orchestrator 9.6 or later.

NOTE: For help upgrading to Rocky Linux, see Move or Restore Orchestrator Using a Backup.

  • Verify that you have the required CPU and memory resources.

  • Depending on your Stats Collector configuration, you will need to migrate the DSC data or the Local Stats Collector data.

Migrate Legacy Stats Collector Data

Run the following script to migrate your statistics data from the legacy Stats Collector to the new Stats Collector introduced in Orchestrator 9.6.0.

  1. Open a CLI session to the Orchestrator VM using the hypervisor console or by creating an SSH shell.

  2. Enter su gms to change the user to gms.

  3. Run the following script located in /home/gms/setup.

    /home/gms/gms/setup/stats_data_migration_from_legacy_new_db.sh

  4. Follow the prompts in the script.

    1. Enter m to migrate the statistics data to the new Stats Collector.

    2. Enter d to delete data from the old/legacy DB without migration.

      Depending on the size of the database, migration may take several hours to complete.

  5. Migration is complete when the “Migration completed successfully!” message displays.

Migrate Distributed Stats Collector Data

Run the following script to migrate your statistics data from Distributed Stats Collectors to the new Stats Collector in Orchestrator 9.6.0. If you have multiple Distributed Stats Collectors, you will repeat the following steps on each Stats Collector VM.

  1. Open a CLI session as root user to the Stats Collector VM using the hypervisor console or by creating an SSH shell.

  2. Run the following commands:

    1. firewall-cmd --zone=public --add-port=8123/tcp --permanent

    2. firewall-cmd --reload

  3. Enter su gms to change the user to gms.

  4. Run the following script located in /home/gms/gms/setup/.

    /home/gms/gms/setup/enable_remote_dsc_for_stats_migration.sh

    After the “Successfully enabled remote DSC for stats migration” message displays, proceed to step 5.

  5. SSH into the Orchestrator VM.

  6. Enter su gms to switch the user to gms.

  7. Enter the following command to run the script:

    /home/gms/gms/setup/stats_data_migration_from_dsc_new_db.sh Orchestrator_previous_version

    For example:
    /home/gms/gms/setup/stats_data_migration_from_dsc_new_db.sh 9.5.3.40112

    Depending on the size of the database, migration may take hours to finish. Migration is complete when the “Migration completed successfully!” message displays.

  8. SSH into the DSC as root user.

    1. firewall-cmd --zone=public --remove-port=8123/tcp --permanent

    2. firewall-cmd --reload

Migration is complete.

Decommission Distributed Stats Collectors and Reallocate Resources

After you migrate your statistics data to the new Stats Collector in Orchestrator 9.6.0, you can decommission the Distributed Stats Collectors and reallocate the resources.

IMPORTANT: Historic statistics cannot be recovered after you decommission a Distributed Stats Collector.

To verify that historic statistics were successfully migrated:

  1. Log in to Orchestrator.

  2. Navigate to Monitoring > Tunnel Health > Other Tunnel Statistics > Tunnels Summary or Monitoring > Bandwidth > Overlays & Interfaces > Interface Summary.

  3. Verify that the historic statistics are displayed.

  4. If historic statistics are displayed, you can decommission the Distributed Stats Collectors and reallocate the resources.