Skip to main content
Announcements
UPGRADE ADVISORY for Qlik Replicate 2024.5: Read More
cancel
Showing results for 
Search instead for 
Did you mean: 
Gpoojith
Contributor II
Contributor II

Qlik Replicate Migration to new server

We have two server

Server :: APP447(Windows 2012) has been installed with Qlik Replicate Version Nov 2022 and Enterprise manager Version Nov 2022.
Server :: APP220(Windows 2012) has been installed with Qlik Replicate Version Nov 2022.


As the Nov 2022 Qlik Version is going end of Support by Nov 2024. We are planning to update to Nov 2023.

It is understood Qlik Replicate version Nov2023 doesn't support Windows 2012.


In this case we will have New windows 2019 server ready and install the Qlik Replicate and Enterprise Manager Version Nov 2023 as a fresh installation.

Now Our Concern is, How can we migrate all Jobs/Task/Configuration/persmission and other setting old Environment to new Environment.

What need to be done so that new server reflects same as the old one.

3 Replies
Kent_Feng
Support
Support

Hi @Gpoojith 

You can run this command in the current server to export the repository:

repctl exportrepository

This command will generate a JSON file that contains all task definitions and all endpoint information except the passwords. Then you can import the json to the new server

repctl importrepository json_file=<json file name>

Please refer to below links for more information:

Backing up or Exporting Tasks from Qlik Replicate

Importing tasks

 

Thanks

Kent

*** Greetings from Down Under ***
john_wang
Support
Support

Besides @kent1 , there is a similar topic Safely migrating existing Qlik Replicate tasks.

Hope this helps.

John.

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
Heinvandenheuvel
Specialist III
Specialist III

If you go the export - import route as @Kent_Feng suggest then you'll have a challenge resuming active tasks from the right position. Your only option will be to start by timestamp-tables-already-loaded, saving context in the target.

For these migrations I believe it is better to STOP all,  backup the whole data directory, restore, and start on the new server against a copy of the old server. That should resume all tasks where they stopped. You may want to clean out, or move the old log  files if those are large. And if some tasks have an excessive sorter directory then maybe  look at starting those by timestamp and not copying the sorter directory.

Hein