Qlik Task Unavailability Post Qlik disaster recovery

Visa_Aaron_Xing — Mon, 10 Feb 2025 17:46:08 GMT

Environment Details:

Qlik Environment:
- Operating System: Windows Server 2022
- Qlik Version: 2024.5.0.144
Data Source Environment:
- Database: SQL Server
- SQL Server Version: 2019
- Operating System: Windows Server 2019

Issue Description:

We are encountering an issue following the recovery process of disaster recovery by moving the file to a different Qlik server.

Steps Followed:

Stopped both active Qlik_SERVER_1 and passive Qlik_SERVER_2 Qlik servers.
Stopped any running tasks (60+ tasks).
Performed Qlik disaster recovery by moving the file from Qlik_SERVER_1 to Qlik_SERVER_2.
Started Qlik services successfully on Qlik_SERVER_2.
Attempted to start the Qlik tasks on the new active Qlik_SERVER_2.
Sometimes the Qlik tasks cannot start with any of the options (Normal Resume, Reload, Reprocess with X LSN).

Additional Observations:

After stopping the Windows process of each Qlik task, we can restart them successfully, but only 2-5 tasks together at a time.

Error Message:

Upon changing the log level to trace, the following error messages were observed:

00002188: 2025-02-10T16:34:35:924215 [IO ]V: combine_path: rootPath=<f:\mware\Attunity\Replicate\data\logs>, addPath=<f:\mware\Attunity\Replicate\data\logs> (at_dir.c:1014)
00002188: 2025-02-10T16:34:35:924215 [IO ]V: combine_path: result before canonize=<f:\mware\Attunity\Replicate\data\logs\clean_old_logs.bat> (at_dir.c:1025)
00002188: 2025-02-10T16:34:35:924215 [IO ]V: combine_path: result=<f:\mware\Attunity\Replicate\data\logs\clean_old_logs.bat> (at_dir.c:1031)
00002188: 2025-02-10T16:34:35:924215 [IO ]V: combine_path: rootPath=<f:\mware\Attunity\Replicate\data\logs>, addPath=<f:\mware\Attunity\Replicate\data\logs> (at_dir.c:1014)
00002188: 2025-02-10T16:34:35:924215 [IO ]V: combine_path: result before canonize=<f:\mware\Attunity\Replicate\data\logs\reptask_UNI-SRC-FSHD-01-TGT-FRPT-UV.log> (at_dir.c:1025)
00002188: 2025-02-10T16:34:35:924215 [IO ]V: combine_path: result=<f:\mware\Attunity\Replicate\data\logs\reptask_UNI-SRC-FSHD-01-TGT-FRPT-UV.log> (at_dir.c:1031)
00002188: 2025-02-10T16:34:35:924215 [IO ]V: combine_path: rootPath=<null>, addPath=<null> (at_dir.c:1014)
00002188: 2025-02-10T16:34:35:924215 [IO ]V: combine_path: result before canonize=<F:\mware\Attunity\Replicate\data\logs\reptask_UNI-SRC-FSHD-01-TGT-FRPT-UV.log> (at_dir.c:1025)
00002188: 2025-02-10T16:34:35:924215 [IO ]V: combine_path: result=<F:\mware\Attunity\Replicate\data\logs\reptask_UNI-SRC-FSHD-01-TGT-FRPT-UV.log> (at_dir.c:1031)
00002188: 2025-02-10T16:34:35:924215 [IO ]V: combine_path: rootPath=<f:\mware\Attunity\Replicate\data\logs>, addPath=<f:\mware\Attunity\Replicate\data\logs> (at_dir.c:1014)
00002188: 2025-02-10T16:34:35:924215 [IO ]V: combine_path: result before canonize=<f:\mware\Attunity\Replicate\data\logs\reptask_UNI-SRC-FSHD-01-TGT-FRPT-UV__250210163435.log> (at_dir.c:1025)
00002188: 2025-02-10T16:34:35:924215 [IO ]V: combine_path: result=<f:\mware\Attunity\Replicate\data\logs\reptask_UNI-SRC-FSHD-01-TGT-FRPT-UV__250210163435.log> (at_dir.c:1031)
00002188: 2025-02-10T16:34:35:924215 [INFRASTRUCTURE ]I: Crypto mode: Standard. (at_logger.c:1573)
00002188: 2025-02-10T16:34:35:924215 [INFRASTRUCTURE ]V: thread allocation for converter <0> (at_text.c:725)
00002188: 2025-02-10T16:34:35:924215 [INFRASTRUCTURE ]V: cloning converter, cd 0 (at_text.c:581)
00002188: 2025-02-10T16:34:38:925173 [IO ]T: rep_net_server_select: Server poll timeout. failed (at_repnet.c:489)
00002188: 2025-02-10T16:34:38:925173 [IO ]V: rep_net_server_select:489: Failed (at_repnet.c:550)
00002188: 2025-02-10T16:34:41:925582 [IO ]T: rep_net_server_select: Server poll timeout. failed (at_repnet.c:489)
00002188: 2025-02-10T16:34:41:925582 [IO ]V: rep_net_server_select:489: Failed (at_repnet.c:550)

Request for Assistance:

We seek assistance in diagnosing and resolving the following:

Understanding why Qlik tasks are not available after the recovery process.
Steps to make the tasks available for startup without manually stopping the Windows process of each task.
Any necessary configurations or checks that we might have missed during the recovery process.

Additional Information:

Environment details (OS, Qlik, and SQL Server versions).
Error messages from the trace log (as provided above).

We appreciate your prompt assistance in resolving this issue.

Re: Qlik Task Unavailability Post Qlik disaster recovery

Dana_Baldwin — Mon, 10 Feb 2025 17:56:39 GMT

Hi @Visa_Aaron_Xing

Is Replicate installed in a fail over cluster as described in the User Guide sections here?: Setting up Qlik Replicate in a cluster environment #Setting up Qlik Replicate in a cluster environment | Qlik Replicate Help

If so, the operating system handles stopping the tasks & services and moving the resources to the other node.

Please attach one of the task logs from a task that will not start. If you are not comfortable posting that in a public forum, please open a support case.

Thanks,

Dana

Re: Qlik Task Unavailability Post Qlik disaster recovery

Visa_Aaron_Xing — Mon, 10 Feb 2025 18:24:34 GMT

Thank you, Dana, for reply! I did created support case

topic Re: Qlik Task Unavailability Post Qlik disaster recovery in Qlik Replicate

Qlik Task Unavailability Post Qlik disaster recovery

Re: Qlik Task Unavailability Post Qlik disaster recovery

Re: Qlik Task Unavailability Post Qlik disaster recovery