STEP by STEP : Qlik Sense Server Migration by Cloning with Hostname Change
Step 1: Prepare and Backup the Source Server
1.1 Stop All Qlik Services
Open Services.msc and stop these in order:
-
Qlik Sense Engine Service
-
Qlik Sense Proxy Service
-
Qlik Sense Repository Service
-
Qlik Sense Scheduler Service
-
Qlik Sense Service Dispatcher
1.2 Backup the Following Folders
Manually copy these folders to a safe location:
1.3 Backup PostgreSQL Databases
Use pg_dump
or Qlik Shared Persistence tools:
Step 2: Clone the Server and Change Hostname
2.1 Clone the Source Server
Use your hypervisor or disk cloning tool to replicate the VM (e.g., VMware, Hyper-V, Veeam).
2.2 Power On and Rename New Server
-
Boot the new server on isolated or test network.
-
Change hostname:
-
System Properties > Computer Name > Change
-
Reboot after change
-
2.3 Ensure Old Server is Offline (to avoid hostname conflicts)
Step 3: Update Qlik Sense Configuration on New Server
- Log in as the service account.
- Stop all the Qlik Sense services, except for the Qlik Sense Repository Database.
- Use Microsoft Management Console(MMC) to backup and then delete all the Qlik Sense related certificates (client, server, trusted root). (From Personal and Local User)
- Delete or rename the folder %ProgramData%\Qlik\Sense\Repository\Exported Certificates\.Local Certificates.
- Make a copy of %ProgramData%\Qlik\Sense\Host.cfg and rename the copy to Host.cfg.old. Host.cfg contains the hostname encoded in base64. You can generate this string for the new hostname using a site such as base64encode or by running the following PowerShell scriptlet:[Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes("yourServerHostname.yourDomain.com"))
- Open Host.cfg and replace the content with the new string.
Step 4: Bootstrap the Repository to Register New Hostname
4.1 Run Bootstrap Command
In Administrator PowerShell:
This:
-
Rebinds the repository to the new hostname
-
Re-registers the node in the Qlik Repository Database (QSR)
-
Uses the value in
host.cfg
Wait for successful completion. Check logs:
Step 5: Apply Qlik Sense License
5.1 Access QMC on New Hostname
-
Open:
https://NewServerName/qmc
-
Navigate to: License Management
-
Apply your license:
-
LEF (old model) or
-
Signed License Key (SLK)
-
Note: If the license is already in use by the old server, you may need to deactivate it via Qlik support or license portal.
Step 6: Validate All Services
-
Ensure all services are running:
-
Use QMC > Service Cluster or
services.msc
-
-
Validate:
-
QRS (Repository)
-
QES (Engine)
-
QPS (Proxy)
-
QSS (Scheduler)
-
-
Check system logs under:
Step 7: Update Environment Configurations
7.1 Update Data Connections
-
QMC > Data Connections
-
Edit any UNC paths or host-based links
7.2 Update UDC (User Directory Connector)
-
QMC > User Directory Connectors
-
Update any host references
7.3 Review and Fix Hardcoded Hostnames
-
App Load Scripts
-
QlikView-style scripts using
lib://
or full paths
- First, connect to the database under the Connect to database tab.
- For Host Name type the new Central node FQDN.
- Use the default postgres Database user and the password created during the Qlik Sense installation.
- In the Service cluster tab, click OK to retrieve the current Share paths.
- Change them to include the new hostname and click Save.
- Click Clear and then OK once more to confirm the new paths have been saved to the database.
Step 8: Validate Platform
Basic Checks
-
Hub access:
https://NewServerName/hub
-
QMC access
-
Reload test apps
-
Access sheets and streams
-
Check for certificate warnings in browser
No comments:
Post a Comment