How To migrate a Qlik Sense environment to a different host after unbundling PostgreSQL

[Filippo_Nicolussi_P]

The process of migrating a Qlik Sense Enterprise for Windows environment after unbundling PostgreSQL is similar to Migrating any other Qlik Sense environment to a different host.

1. Begin with the Verification of all requirements, the Preparation Reading, and Backup as documented in Migrating Qlik Sense Enterprise to a different host 
   
   
2. Then install a supported version of PostgreSQL and prepare databases as documented in Installing and configuring PostgreSQL.

   Select your corresponding Qlik Sense Enterprise for Windows version from the dropdown select box

3. Install the Central Node using the new PostgreSQL instance prepared in step 2.
    
4. Restore the site. For this, we will use Restoring a Qlik Sense site to a machine with a different hostname, as a general guide, but we will follow a set of modified steps: 
   
   
   1. Stop all Qlik Sense Services you have just installed
   2. Drop the following databases:
      
      This step is only necessary if you already have data in the databases. Otherwise, skip this step and move to step d.
      
      
      • QSR
      • SenseServices
      • QSMQ
      • Licenses
        
        Use the command dropdb -h localhost -p 4432 -U postgres <Database>
        
        
   3. Create the same databases you have just dropped:
      
      
      • QSR
      • SenseServices
      • QSMQ
      • Licenses
        
        Use the command createdb -h localhost -p 4432 -U postgres -T template0 <Database> -O qliksenserepository
        
        
   4. Restore the newly created databases:
      
      
      • QSR
      • SenseServices
      • QSMQ
      • Licenses
        
        Use the command pg_restore -h localhost -p 4432 as documented in Restore the repository database 4.c in Restoring a Qlik Sense site to a machine with a different hostname.
        
        
5. Before proceeding with Restoring a Qlik Sense site to a machine with a different hostname steps 5 to 7:
   
   
   1. Evaluate and prepare your file share. If the share needs to be changed, follow the instructions in How to change the share path in Qlik Sense (Service Cluster)
   2. If you have a multi node with rim or worker nodes which will change names (FQDN), follow the instructions in What about my rim nodes? 
      Note that the LocalConfigs table is removed in the most recent Qlik Sense versions. Do not be alarmed if it is missing.
   3. If your Active Directory Domain changes, proceed with Qlik Sense Entrprise moved to a new domain from point 3 onwards, replacing the old domain name with the new domain, especially for RootAdmin users and new Service User Accounts. 
      
      
6. Continue with Restoring a Qlik Sense Site steps 5 to 7.
   
   
7. At this point, the Central node will be up and running and report its worker or rim nodes as down or not contacted. Continue with the Worker Nodes:
   
   
   1. If the Worker nodes are new, simply install Qlik Sense and add them to the central node
   2. If the Worker nodes have already existed, it may be necessary to regenerate and redistribute new certificates: 
      
      
      1. Open the MMC as the Service user account on the Worker Node and add the Certificate for the Local Server and Current User
      2. Back up the current SelfSigned Qlik Sense Certificate issued by the Old Central Node, then delete it.
      3. Back up and then remove files.pem in “C:\ProgramData\Qlik\Sense\Repository\Exported Certificates\.Local Certificates”
      4. Verify connection strings to the new database of the new Central node using the QlikSenseUtil and the scripts described in QlikSenseUtil and the ConfigureScript.ps1 for Qlik Sense Dispatcher subservices
      5. Start the services and after a short delay verify in the QMC if you need to repeat the Redistribution of Certificates.
         
         
   3. Repeat accordingly for remaining Worker Nodes      

Environment

• Qlik Sense Enterprise on Windows