0

Tenant migration from a 3.x release to 4.2

This document discusses how to upgrade form a 3.x release to a 4.2 release. To upgrade from 3.x to 4.3, see Migrate from Incorta 3.x to Incorta 4.3.

Incorta Analytics 4.2 includes a major overhaul to the installation architecture and the web UI. The upgrade from 3.x to 4.2 is done by installation of 4.2 and migrating the tenant, Parquet files and Snapshot files  from 3.x to 4.2. If you have a pre-4.0 version of Incorta Analytics, use the following steps to migrate:

Step 1: Export a tenant from the 3.x environment, using the TMT utility

  • Connect via SSH to your 3.x environment

  • Go to the "TMT" directory. In 3.x environments, it exists in the following path:

        cd <INSTALLATION_PATH>/tmt
  • Export the tenant definition, by running the following command:

        ./tmt.sh -ex <TENANT_NAME> <EXPORT_FILE_NAME.zip>
  • Copy the tenant .zip file to  the 4.2 Incorta environment

Step 2: Import a tenant into the 4.2 environment, using the CMC TMT utility

Note: Please make sure that the both loader service and the analytical service are shutdown when importing the tenant into 4.x instance 

  • Connect via SSH to your 4.2 environment

  • Change to the cmc/tmt directory.

       cd <INSTALLATION_PATH>/cmc/tmt
  • Copy the exported zip file into this directory

  • Import the tenant using the following command.

 ./tmt.sh -i <EXPORT_FILE_NAME.zip> -clnm <CLUSTER_NAME> -op <TENANT_SHARED_PATH> 

 

Tip: How to find the cluster name
        cd cmc/cmcData/clusters
        cat index.properties

Step 3: Copy the Data files for your tenant from the 3.x environment to the 4.x environment

  • Connect via SSH to your 3.x environment

  • Navigate to the tenant directory. 

        cd <TENANT_PATH>
  • Copy the following data directory  from 3.x:

        <INSTALLATION_PATH>/tenants/<TENANT_NAME>/data

          to the following directory on 4.2

        <TENANT_SHARED_PATH>/<TENANT_NAME>/data 

Step 4: Copy the Parquet and Compacted folders for your tenant from the 3.x environment to the 4.x environment

  • Connect via SSH to your 3.x environment

  • Navigate to the tenant directory. 

        cd <TENANT_PATH>
  • Copy the following Parquet directory  from 3.x:

        <INSTALLATION_PATH>/tenants/<TENANT_NAME>/parquet

        <INSTALLATION_PATH>/tenants/<TENANT_NAME>/compacted

          to the following directory on 4.x

        <TENANT_SHARED_PATH>/<TENANT_NAME>/parquet 

        <INSTALLATION_PATH>/tenants/<TENANT_NAME>/compacted

 

Step 5: Copy the Snapshot files from the 3.x environment to the 4.2 environment

  • Connect via SSH to your 3.x environment

  • Navigate to the following tenant directory: 

        cd <TENANT_PATH>
  • Copy the following snapshots directory  from 3.x

        <INSTALLATION_PATH>/tenants/<TENANT_NAME>/snapshots

          to the following directory on 4.x

        <TENANT_SHARED_PATH>/<TENANT_NAME>/snapshots

 

Step 6: Run the migration tool. (If the columns do not contain data of text or timestamp data types, jump to Step 7.)

The migration tool migrates the snapshot files from a 3.x to 4.x environment. This helps expedite executing queries after the upgrade to 4.x. Please keep in mind that running the migration tool takes a long time before the process completes.

  • Connect via SSH to your 4.x environment

  • Navigate to the directory:

      <INSTALLATION_PATH>/IncortaNode
    
  • Run the migration tool using the following command:  


  ./migrateSnapshotsTool.sh <3.X_SNAPSHOTS_FILE_PATH> <MAX_OFFHEAP_SIZE_GB(OPTIONAL)>

Note: The "max off-heap size" is an optional parameter referring to the amount of memory allocated for the migration tool during the migration process. If not set, this parameter will use the default value of 50 GB.

  • Wait until this script has completely finished.

Step 7: Start one loader service

  • Connect via SSH to your 4.x environment
  • Navigate to the following IncortaNode directory: 

        cd <INSTALLATION_PATH>/IncortaNode/

• Start the loader service node, by running the following:


        ./startService.sh <LOADER_SERVICE_NAME>
  • Wait until this service has completely started.
  • Start other services (i.e. Analytics services and/or other loader services is using more than one)

 

Note:  Starting the loader service for the first time after migration will take longer than usual to calculate and write the snapshot files for all the formulas and join columns. It is strongly recommended to avoid stopping, interrupting, or killing this process before the migration has been successfully completed, as this may result in unexpected issues.

 

 

Reply Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
Like Follow
  • 2 mths agoLast active
  • 479Views
  • 2 Following