Can I just move a backup of the DATA directory to a new Qlik Replicate Instance?

[zacker20]

Looking at creating a DR process, we were thinking that moving the DATA directory from one Qlik Replicate Instance to another would copy all tasks/settings. 

However, after doing so, the Qlik Replicate services are failing to start.  Is this a valid DR process? 

[Dana_Baldwin]

Hi @zacker20 

Please follow this process to move the data directory to a new server. The data is encrypted to only work on the installed server by default.

How to Move the Data Directory to a Different Repl... - Qlik Community - 1962033

Thanks,

Dana

[zacker20]

Hey @Dana_Baldwin -

That is not working for us.   We are unable to start the service in the target Replicate server after following the instructions in that link.

[Dana_Baldwin]

Hi @zacker20 

I see you have opened a support case for this issue. Please work with the assigned engineer via the case.

Thanks,

Dana

[Alan_Wang · Accepted solution]

Hello all,

This issue has been resolved by including the data folder path in the repctl commands. If the data folder has been separated into its own drive, you must specify the path for the commands or the commands will be applied to the wrong files. In this case, the master key updates did not apply to the right files, and starting the service leads to master key mismatches.

Here's an example of including the data directory path
RepUiCtl.exe -d "Data_folder_path" utils genpassword

[MoeyE]

Hi Dana,

I can confirm that we tried this article too and it did not work for us. The ServiceConfiguration.xml file seems to not be recreated after it is deleted.

[Steve_Nguyen]

the serviceconfiguration file is created on install .

[zacker20]

@MoeyE  -- is the Qlik data folder on a different drive on your server?  Ours was on the "D:" drive on our server so we had to include the -d parameter when we were setting the master key that was a direct path to our Data folder.   -d 'D:\Attunity\Qlik\Data'   If that's not included it sets the master key for the C drive path

[MoeyE]

Hi Steve,

"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." 

Starting the services up again doesn't create a new serviceConfiguration file in our environment.

Also the C: drive is where the data folder is located so i dont think that's the issue.

Will placing the target's old ServiceConfiguration file in work?

thanks,

Mohammed

[Heinvandenheuvel]

Folks, I do not see the "master_key_scope" argument to setmasterkey mentioned.

This is critical and must be well understood.  Carefully read "3.6 Protecting Replicate passwords " in the Replicate Users Guide. Notably "The master key scopes are:" .

There it suggests: " (Constant) - The default. The mk.dat file can be used wherever it is copied to. "

This would be a practical, but insecure option, as DB passwords - while still  encrypted and not visible - could be used on an other, less securely configured Replicate Server where a rogue task could be build to suck out data outside the intended protection. It wouldn't surprise me if Replicate changed that in the code to 'Machine', but failed to update the documentation for the default.

What was the master key scope on the source?

Cheers,

Hein