Qlik Replicate upgrade on a Windows Cluster from 2022.5 or .11 to 2023.5 and 2023.11

Steve_Nguyen — Tue, 02 Jul 2024 13:42:49 GMT

This article provides the steps needed to successfully upgrade Qlik Replicate installed on a Windows Cluster.

Environment:

Qlik Replicate 2022.5 upgrade to 2023.5
Qlik Replicate 2022.11 upgrade to 2023.11

Resolution

Stop all tasks. Note that some tasks could take up to 20 minutes or more to stop. Monitor the process before you continue.
Assuming we are on Active Node A: from the Cluster Manager, take the Qlik Replicate Server and Qlik Replicate UI server Offline. Note: the services may still be referred to as Attunity Replicate.
Take a backup of all your task definitions on Node A: Replicate Command Line Console as Administrator
Run:
```
repctl -d "YOUR_DATA_DIRECTORY_PATH" exportrepository
```
Example: ~Program Files\Attunity\Replicate\bin> repctl -d "S:\Programs\Qlik\Replicate\data" exportrepository
This example writes the backup to the Replication_Definition.json file.
Back up your data directory by copying it to a folder location outside the Replicate directories. You can skip copying the \logs subfolder.
On Node A: verify the installed version of Replicate. This can be done by reviewing the program installed through the Windows Add/Remove programs feature. Note: attempting to “upgrade” with an identical version will lead to Replicate being uninstalled.
Verify what account the Attunity (or Qlik) Windows Services are run with. Note the account credentials (username and password). After the upgrade, the account may have been switched back to Local System and the account credentials will need to be entered again.
On the active node: perform the upgrade by running a newer version of the Qlik Replicate executable.
- Right-click on the executable and run as administrator.
- Follow the on-screen instructions.
On Node A:
- Verify that the Qlik Replicate Server and Qlik Replicate UI Server are stopped in the Cluster Manager
- Verify that the Qlik Replicate Server and Qlik Replicate UI Server are stopped in the Windows Services
Move the Cluster service (this is the role that manages your share drive/Qlik service/and client access point) to another node (Node B in our example). This is going to move the shared drive and service to the other node (Node B).
On Node B: run the same upgrade as previously done on Node A, repeating steps 8 to 9.
Repeat the upgrade steps on any additional nodes.
Once all Nodes are upgraded from Windows Cluster Manager, verify that Qlik Replicate is referred to as Qlik Replicate Server and Qlik Replicate UI server. If the services are named Attunity, then remove the service and add the Qlik Services to your Windows Cluster Roles and define all dependencies. See Add the Qlik Replicate services or details.
Verify the account running the Qlik Services on all nodes, changing the account back to the account which was used before the upgrade (see step 7).
From the Windows Cluster, bring the Qlik Replicate Server and Qlik Replicate UI Server back online.
Resume the tasks. Note: resume tasks at a rate of five (maximum) at a time until all have been launched.

article Qlik Replicate upgrade on a Windows Cluster from 2022.5 or .11 to 2023.5 and 2023.11 in Official Support Articles

Qlik Replicate upgrade on a Windows Cluster from 2022.5 or .11 to 2023.5 and 2023.11

Environment:

Resolution