Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
nithin_seeni
Contributor II
Contributor II

Qlik Replicate Migration from On Premise server to Cloud Server

Hi,

We have a Qlik replicate currently hosted on an On-Premise server and the client wants to migrate it to a Cloud server. 

What steps and pre-checks/post-checks need to be performed for smooth and correct migration? 

Note: It will be a fresh installation in the new cloud server. 

Labels (4)
4 Replies
john_wang
Support
Support

Hello @nithin_seeni ,

Thanks for reaching out to Qlik Community!

 

It’s difficult to provide a complete answer without more details about the entire environment. However, as a general best practice:

  1. Locate Qlik Replicate near the source database: Ideally, Qlik Replicate should be positioned in close proximity to the source database or data source, preferably on the same LAN as the source database. This helps to reduce latency and improve performance.

  2. Ensure adequate network bandwidth if Qlik Replicate is on a different LAN: If Qlik Replicate must reside on a different LAN from the source or target databases, ensure that the network bandwidth is sufficient to handle the data traffic. Insufficient bandwidth can lead to performance issues.

  3. Migrate tasks from On-Premise to Cloud: You can export existing tasks from an On-Premise server and import them into a Cloud server. After importing, be sure to follow the necessary steps for reconfiguration and testing to ensure smooth operation. Please check out the article: Process to follow after migrating the Qlik Replicate tasks from one server to another server.

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!
Kent_Feng
Support
Support

Hi @nithin_seeni 

Since you will have a brand new installation in the Cloud Replicate Server. I would recommend:

- export the repository from the on-prem Replicate Server.

- import the repository into the Cloud Replicate Server

- check the source and target endpoints one by one, make sure all needed ODBC/clients are installed to the cloud Replicate, update the password, click Test Connection 

- when all endpoints are connected okay, reload the tasks one by one.

The above is just some ideas for your reference.

 

Regards

Kent

*** Greetings from Down Under ***
MoeE
Partner - Specialist
Partner - Specialist

Hi John,

If it is a clone of the current machine to the cloud, but the new machine has a different name, what are the steps? As far as I'm aware, you'd need to alter the QR server name in the QR settings. Are there any other steps required?

Thank you.

Cheers,

Mohammed

john_wang
Support
Support

Hello Mohammed, @MoeE 

You’re absolutely right — you need to run "repuictl configuration set --addressto update the hostname. In addition, make sure the required users are created before performing the clone.

For example, if the original server uses the account old\accountA, and you plan to clone Replicate to a new machine, you’ll need to create new\accountA on the target system in advance.

This ensures the cloned environment works smoothly without permission issues.

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!