Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Migration from a Single-Master Setup to a Multi-Master Setup

Paragon Insights does not support an upgrade from a single-master setup to a multi-master setup. With Paragon Insights Release 4.0.0, you can only migrate from a single-master setup to a multi-master setup.

These topics provide information on migration.

Before You Begin

  • For production deployments, it is recommended that you have dedicated master nodes for the Kubernetes control plane.

  • All prerequisites (node-related) provided in the Paragon Insights Installation Requirements topic are met.

Steps for Migration

Follow these steps to migrate from a single-master setup to a multi-master setup

  1. Backup Config data from the single-master setup.

    The Config files must be backed up in a folder other than /var/local/healthbot/ to avoid losing data during uninstallation.

    For more information on backup, see Paragon Insights Configuration – Backup and Restore.

  2. Backup Times Series Database (TSDB) data from the single-master setup.
  3. Uninstall Paragon Insights.
  4. Reinstall Paragon Insights.

    Run healthbot setup, install Kubernetes, and run healthbot start.

    • For more information on installing Paragon Insights, see Using the Interactive Installers to Install or Upgrade to Paragon Insights Release 4.X.

    • When you run healthbot setup, you are prompted to specify hostnames or IP addresses of the master nodes. If you choose to have multiple master nodes, you must also specify the virtual IP address that is required for configuring high availability (HA) between the master nodes. However, if you use the silent installer, you can specify the virtual IP address in the master_virtual_ip field of the configuration file.

    • To add more than one virtual IP during healthbot setup, see Multi-NIC.

  5. Restore TSDB backup.
  6. Restore configuration and helper files.

Multi-NIC

Paragon Insights Release 4.0.0 supports multi-NIC (network interface card).

In a scenario where telemetry information of devices that you are monitoring is generated from one network, and you access the web UI from another network, Paragon Insights allows you to enter multiple virtual IP addresses when you run the healthbot setup. This ensures segregation of traffic between the networks.

For this feature to work, you will need multiple virtual IP addresses for every subnet. Virtual IP addresses for these subnets can be provided when you run healthbot setup.

For example, when you run healthbot setup, you are prompted to enter a virtual IP address. In this case, you must enter more than one virtual IP address. After you run healthbot start, all services will be available on all virtual IP addresses.