Migrating from Standard Edition to Standard Edition

Complete the following prerequisites:

• Prepare your new host as mentioned in Preparing your single-node environment or Preparing your multi-node environment.
  • 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. If required, upgrade the backend:
  • To upgrade the Instana backend on Classic Edition, see Upgrading Classic Edition . The Instana backend on Classic Edition must be build 271 or later.
  • To upgrade the Instana backend on Standard Edition, see Upgrading Standard Edition .
• For air-gapped migration, create an air-gapped package on the bastion host, transfer the package to the air-gapped host, install stanctl on the air-gapped host, and import the package on the air-gapped host.

To migrate the data, complete the following steps:

1. Extract the tenant unit configuration data from the Postgres data store. Run the following command on the old Standard Edition host:

   stanctl dump config-data

   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.

2. Optional: Set the --include-sensitive flag to skip the following dialog dialog ....Do you want to include sensitive information?.

   Sensitive information includes SMTP password, proxy password, and download keys.

   If the --include-sensitive is not set, the following dialog is displayed.

   This operation may include sensitive information (for example, SMTP credentials, proxy credentials, and download key).
   Do you want to include sensitive information?
   Note: Excluding it will require you to reconfigure SMTP and proxy settings in the destination environment during installation.

3. Complete one of the following steps:
   • To include sensitive information in the backup, enter "Yes".
   • To exclude sensitive information from the backup, enter "No".

   A dump-<timestamp>.tar.gz file is created in the current directory. This file contains the tenant unit configuration data in the form of executable SQL queries.

4. Do one of the following steps:

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

5. On your new Standard Edition host, migrate the data from the dump.tar.gz file.

   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>
        

6. The following dialog is displayed.

   Are you migrating from the Classic offering?

7. Enter "No", the original multi-domain or single-domain setup is retained.
   After you run the command, you see the following prompt:

   ? Choose installation type:
   demo <
   production
    

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

   When migration is completed successfully, a confirmation message appears, similar to the following example:

   
      ╭──────────────────────────────────────────────╮ 
      │                                              │ 
      │ Migration completed successfully!            │ 
      │ You can now install Instana Standard Edition.│ 
      │                                              │ 
      ╰──────────────────────────────────────────────╯ 
      

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

   Note: If you want to configure additional settings such as custom certificates, SMTP configuration, proxies, and other settings, see Instana backend configurations. You can use the configuration flags with the stanctl up command.

After the installation is successfully completed, a message similar to the following example is displayed:

*****************************************************************
* Successfully installed Instana Self-Hosted Standard Edition! *
*                                                               *
* URL: https://instana.example.com                              *
* Username: admin@instana.local                                 *
*****************************************************************
 

You can sign in to the new Standard Edition UI by using the same tenant password that you used in your old Standard Editionenvironment.

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. To connect your agents to the old and new backends, see Configuring multiple backends.

• 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.

The following restrictions are applicable for simultaneous reporting into two Instana backends:

• The Kubernetes sensor in the Instana agent does not support two Instana backend configurations. See Report to multiple backends for Kubernetes monitoring.
• The EUM (end user monitoring) clients do not support reporting to two Instana backends.
• Serverless client implementations do not support reporting to two Instana backends.
• Configuration changes made after the migration are not automatically synchronized between the two Instana backends.

You might encounter issues after migration. If you are unable to resolve these issues, contact IBM Support.