https://community.qlik.com/t5/Qlik-Replicate/Replicate-after-database-Migration/m-p/2556135#M16693 <P>I would appreciate your advice regarding the scenario below.</P> <P>As part of our infrastructure refresh, we will be migrating several databases&nbsp; to a new SQL Server due to the end-of-life status of the current hardware. The migration approach will be based on a full database backup and restore to the new server.</P> <P>My main concern is ensuring that the existing Qlik Replicate tasks continue operating without data loss or replication issues after the migration.</P> <P>Can someone please share your recommended approach for handling this type of migration? Specifically, I would like to understand:</P> <UL> <LI>How you would preserve the replication state during the migration.</LI> <LI>Whether stopping the Qlik Replicate tasks before the migration and resuming them afterward would be sufficient.</LI> <LI>Whether it is necessary to use the current LSN position to resume change processing and avoid data loss.</LI> <LI>Any additional precautions or best practices you would recommend based on your experience.</LI> </UL> <P>At the moment, my initial thought is to stop the replication tasks before the migration, perform the database backup and restore, update the endpoints if required, and then resume replication from the appropriate LSN. However, I would appreciate your guidance on the best and safest approach.</P> <P><LI-WRAPPER></LI-WRAPPER></P> Thu, 10 Sep 2026 11:44:17 GMT QuiosaEvaristo 2026-09-10T11:44:17Z https://community.qlik.com/t5/Qlik-Replicate/Replicate-after-database-Migration/m-p/2556135#M16693 <P>I would appreciate your advice regarding the scenario below.</P> <P>As part of our infrastructure refresh, we will be migrating several databases&nbsp; to a new SQL Server due to the end-of-life status of the current hardware. The migration approach will be based on a full database backup and restore to the new server.</P> <P>My main concern is ensuring that the existing Qlik Replicate tasks continue operating without data loss or replication issues after the migration.</P> <P>Can someone please share your recommended approach for handling this type of migration? Specifically, I would like to understand:</P> <UL> <LI>How you would preserve the replication state during the migration.</LI> <LI>Whether stopping the Qlik Replicate tasks before the migration and resuming them afterward would be sufficient.</LI> <LI>Whether it is necessary to use the current LSN position to resume change processing and avoid data loss.</LI> <LI>Any additional precautions or best practices you would recommend based on your experience.</LI> </UL> <P>At the moment, my initial thought is to stop the replication tasks before the migration, perform the database backup and restore, update the endpoints if required, and then resume replication from the appropriate LSN. However, I would appreciate your guidance on the best and safest approach.</P> <P><LI-WRAPPER></LI-WRAPPER></P> Thu, 10 Sep 2026 11:44:17 GMT https://community.qlik.com/t5/Qlik-Replicate/Replicate-after-database-Migration/m-p/2556135#M16693 QuiosaEvaristo 2026-09-10T11:44:17Z https://community.qlik.com/t5/Qlik-Replicate/Replicate-after-database-Migration/m-p/2556144#M16694 <P>Hi</P><P>Just got through this document might help&nbsp;</P><P><A href="https://help.qlik.com/en-US/replicate/May2026/Content/Global_Common/Content/SharedEMReplicate/Tasks%20at%20Runtime/monitor_detailed_run_options.htm" target="_blank">https://help.qlik.com/en-US/replicate/May2026/Content/Global_Common/Content/SharedEMReplicate/Tasks%20at%20Runtime/monitor_detailed_run_options.htm</A>?</P> Thu, 10 Sep 2026 14:08:14 GMT https://community.qlik.com/t5/Qlik-Replicate/Replicate-after-database-Migration/m-p/2556144#M16694 Chanty4u 2026-09-10T14:08:14Z