Migrating from Custom Edition to Standard Edition

Make sure that the following prerequisites are met:

• Prepare your new host as mentioned in Preparing your single-node environment or Preparing for a three-node deployment or System requirements for a five-node deployment.
  • For DNS settings, use the tenant and unit names of your old environment. Since the tenant and unit names are part of the unit domain name, these names must be present in the DNS record of the Standard Edition environment. This is also necessary for logging in to Standard Edition by using LDAP authentication, as LDAP configurations are also migrated.
• Install the stanctl binary. For more information, see Installing stanctl command-line tool.
• Ensure that the Instana backend version of your old host and new host is the same.

To migrate the data, complete the following steps:

1. On your Custom Edition host, extract the tenant unit configuration data from the Postgres data store.

   kubectl-instana dump config-data --unit <unitname> --unit-namespace <namespace>
    

   A dump.tar.gz file is created in the ./dump directory. This file contains the tenant unit configuration data in the form of executable SQL queries.

   Table 1. Extraction parameters

   Parameter	Description
   --unit-namespace	Unit Namespace (default: instana-units)
   --postgres-namespace	Namespace (default: instana-postgres)
   --unit	Name of unit (default: unit0-tenant0)
   --include-sensitive	Set this flag to includes SMTP password, proxy password, and download keys in the backup configuration
   --help	See supported options

2. On your new Standard Edition host, complete one of the following steps:

   • Online migration: Transfer the dump.tar.gz package from the old host to your new host to migrate.
   • Air-gapped migration: Transfer the dump.tar.gz package from the old host to your new air-gapped host by using the bastion host.

3. Complete one of the following steps:

   Table 2. Migration parameters

   Parameter	Usage	Example
   --volume-data=<custom-directory>	Specifies the directory to store configuration and operational data for Elasticsearch, PostgreSQL, and Kafka data stores Default: /mnt/instana/stanctl/data	--volume-data=/custom/data/path
   --volume-metrics=<custom-directory>	Specifies the directory to store metrics and time-series data for Cassandra and BeeInstana data stores Default: /mnt/instana/stanctl/metrics	--volume-metrics=/custom/metrics/path
   --volume-analytics=<custom-directory>	Specifies the directory to store analytics data for ClickHouse data store Default: /mnt/instana/stanctl/analytics	--volume-analytics=/custom/analytics/path
   --volume-objects=<custom-directory>	Specifies the directory to store object storage data including traces and monitoring data Default: /mnt/instana/stanctl/objects	--volume-objects=/custom/objects/path

   • For a single-node deployment, run the following commands:
     • Online migration

       stanctl migrate -f </path/to/tar.gz>
        

     • Air-gapped migration

       stanctl migrate --air-gapped -f </path/to/tar.gz>
        

   • For a multi-node deployment, run the following commands:
     • Online migration

       stanctl migrate --file=</path/to/tar.gz> --multi-node-enable --multi-node-ips=<node0IPaddress,node1IPaddress,node2IPaddress>
        

     • Air-gapped migration

       stanctl migrate --air-gapped --file=</path/to/tar.gz> --multi-node-enable --multi-node-ips=<node0IPaddress,node1IPaddress,node2IPaddress>
        

     The following dialog is displayed.

     Are you migrating from the Classic offering?

4. Enter "No". The domain configuration is preserved.

   After you run the command, the following dialog is displayed:

   ? Choose installation type:
   demo <
   production
    

5. Choose your preferred installation type. For multi-node clusters, only the production installation type is supported.

6. Install Standard Edition with the tenant unit configuration data that you migrated from your old host. For more information, see Installing Standard Edition in an online environment or Installing Standard Edition in an air-gapped environment.

If required, you might need to redo some configurations that were on the old host. You can reconfigure as suggested in the following list:

• New Standard Edition instance is not connected to any agent by default. Complete one of the following steps:

  • Connect your agents to old and new backends, see Configuring multiple backends.
  • Connect your agents to the new backend, update the existing DNS records to point to the new Standard Edition instance. The agents automatically start reporting to the new backend.

• After the migration, when the old and new environments are connected to your agents, both the Instana environments generate alerts. To avoid duplicate alerts, you can set a maintenance window on one of your Instana instances. For more information, see Scheduling maintenance windows. /events_alerts/maintenance-window.dita