Skip to main content

Official Support Articles

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Have an amazing Qlik Success Story? Share it at QlikWorld! Submit Proposal

How to Move the Data Directory to a Different Replicate Server

Showing results for 
Search instead for 
Did you mean: 

How to Move the Data Directory to a Different Replicate Server

The basic idea behind this procedure is that by default, the data repository of Replicate is encrypted by a machine key which is unique for each machine.

This means, you cannot move the data repository to another Replicate server because that server data repository is encrypted by that server’s machine key which is obviously different.

To allow that procedure, you’ll need to re-encrypt the source data repository with a predefined password which is not machine related, and this password can be used on the target machine to access that repository after it is migrated. 




The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

Note: Re-encrypting the data repository requires you to re-enter the endpoint passwords, therefore we strongly recommend encrypting the repository with a predefined key right after installation, before you set endpoints and tasks on the machine.

Since the Server and UI are using 2 different keys, both keys will need to be updated using the following procedure:


  • Assuming both servers are members of the same domain, please make sure you can open the Replicate console with a domain user, otherwise in:

Server->User Permissions


Please add a domain user, grant it “Admin” access level, and save the new settings.

Please reopen the console and make sure you can access the console with the credentials of the domain user.


The above step is needed because otherwise you won’t have a valid user to open the console on the target machine.


  • To set the server repository master key password on the source server, open "as Administrator":

“Attunity Replicate Command line”


Run the following command to set the Replicate server key:

C:\Program Files\Attunity\Replicate\bin>repctl  setmasterkey master_key_scope=1


[setmasterkey command] Succeeded


  • The UI master key password must contain 32 varying characters, you can generate it using the following command:

C:\Program Files\Attunity\Replicate\bin>RepUiCtl.exe utils genpassword



Note: you must save this password in a safe place for future use



Now, you can set the above password using the following command:


C:\Program Files\Attunity\Replicate\bin>RepUiCtl.exe masterukey set -p miBqZuBFg


The master user password has been changed. The change will only take effect after the service is restarted.

Replicate Control Program completed successfully.


  • Restart both services:




  • Open the console. Since the Master key password has been changed, you’ll need to re-enter the password for each endpoint. Please do that and make sure you can test the connection successfully for each endpoint.

  • On the target machine, please stop both Replicate services, and rename the Data directory.

  • Copy the data directory from the source machine to the target machine.

  • On the target Data directory, delete file:


This file refers to the source machine name and is not valid on the target machine, starting the services on the target machine will create the file from scratch, matching localhost.


  • On the target machine run the same password set command for the UI:

C:\Program Files\Attunity\Replicate\bin>RepUiCtl.exe masterukey set -p miBqZuBFg


  • Start both Replicate services and open the console, and make sure tasks can be resumed properly.
Version history
Last update:
‎2022-07-28 06:59 PM
Updated by: