Disaster Recovery plan for Qlik replicate

[ravindraguduru]

Hello Qlik Experts,

We are planning to establish Disaster recovery setup for Qlik replicate on Windows VM server. Can anyone please share  documents/ articles that can help us understand on Disaster Recovery strategy better?

- Ravi

[ravindraguduru]

Hi Experts,

Is there anyone who can help in this area?

-Ravi

[MaheshNayakar]

Hey Ravi, have you established Disaster recovery setup for Qlik?

We also looking for same thing.

[Prabodh]

Hi Ravi,

We are also setting up Qlik Replicate on Windows VM in production. We already have a linux based setup.

For our linux setup we have configured a primary and a hot standby at the DR site. The hot standby has Replicate installed on it and the Replicate service is stopped. The data directory is shared between these two using NFS. We have configured a load balancer URL in QEM. In event of primary failure, we bring up the secondary, update the load balancer and are good to go.

We are facing challenge doing the same on Windows VM as we do not have the ability to mount a network storage to our Windows infrastructure using iSCSI. We have mounted the disk using NAS and Replicate does not identify this drive during install. We are trying to see if we can hack Replicate to store the data directory on a NAS drive on Windows.

If that does not work out, the option would be to setup data replication between the primary and secondary. However, that would mean that we might lose data in event of a failure.

Thanks!

[Ted_Manka]

Hello @Prabodh ,

Nice to see you here too 🙂  I believe we got this worked out with Srishti that you cannot do this on install (unless this is a new scenario).  You need to do the install to a local directory then change the data directory afterwards using the network path.  Let me know if you want to discuss more tomorrow.

Best,

Ted

[DanCarvin]

Hi, we are also using replicate on Windows and are discussing DR strategies.

We have our primary Replicate server hosted in a West Coast data center and a DR Replicate server in an East Coast data center.  We export the Task JSON files from the West Server and Imported them on the East Server. 

In past DR tests (with Replicate version 6) we have stopped the tasks on the West Server and were able to resume the tasks on the East Server.   We are in the process up upgrading to the May 2023 version and I am concerned about State and Swap files on the West server that don't exist on East.

Would it be viable  to build a task that synchronizes the data folder between the West and East Servers so that Tasks can be resumed smoothly?