Migration of LSS/Replication tasks to a new server
Hello Experts,
Our customer is planning to migrate their Qlik Replicate server.
The environment is as follows:
Original Server: 2024.5 New Server: 2024.11
They need to move LSS/Replication tasks to a new server, but they wish to avoid full loading after the migration.
I'm considering the following approach, which seems to work based on our internal testing.
1) Export the task definitions and import them to the new server.
2) Start the LSS Task on the new server Ensure that there are no transactions on the related source tables prior to this timing.
3) Stop the Replication Task on the original server and note the time.
4) Start the Replication Task on the new server using the 'Advanced Run Options', Select 'Tables are already loaded. Start processing changes from:' Specify the time recorded in Step 3) (the time when the task was stopped).
Questions:
I would like to confirm a few points regarding the above migration procedure.
1. Can we consider this approach as a viable solution? Are there any potential issues or any concerns with the above migration approach that we should be aware of?
2. Is there a method to accurately determine the stop time for starting the Replication Task on the new server?
I found the following messages in the log when stopping the previous task.
[SORTER ]I: Final saved task state. Stream position 1;638791688361007800;20250402053108682395, Source id 19, next Target id 13, confirmed Target id 9, last source timestamp 1743572033090335 (sorter.c:782)
Should I convert the timestamp 1743572033090335 using websites like the one mentioned below?
Looks Correct. Check in lower envrionment and LSS never do the Fullload. Fulload done by the rerplicate task. and you have to point the replicate task from the point where its going to read the changes from Staging folder.
disable the Full load in the Full load section and then start the task from 0, or Timestamp where the LSS task is started.
if its help, give ita like and put to solution proposed.
