Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
ALERT: QlikView server communication interruptions following Microsoft Windows Domain Controller security updates

Backing up or Exporting Tasks from Qlik Replicate

67% helpful (2/3)
cancel
Showing results for 
Search instead for 
Did you mean: 
lyka
Support
Support

Backing up or Exporting Tasks from Qlik Replicate

Last Update:

Jun 15, 2023 4:53:59 AM

Updated By:

Sonja_Bauernfeind

Created date:

Mar 24, 2022 5:32:30 PM

Can tasks be exported from Qlik Replicate or is a full ~\data backup required?

You can export all or individual tasks with repctl exportrepository.

To export tasks using the command line:

  1. On the Qlik Replicate host where you want to export the task, open the Start menu and expand Qlik Replicate, then select Qlik Replicate Command Line
    You can also open the Windows command-line console and change the directory to  <product_dir>\Attunity Replicate>\bin
  2. Run the following command:

    repctl connect

  3. To export tasks:

    For exporting all tasks, run: repctl exportrepository
    For exporting a specific task, run: repctl exportrepository task=”task:name”
    Modify either command if you use a custom data directory. Example: repctl -d <custom_data_directory> exportrepository task=task_name
  4. By default, the repository will be exported to the Qlik Replicate directory /imports. In case you want it to be somewhere else, specify the path by adding: folder_name=path at the end of the command.

    Example: repctl -d <custom_data_directory> exportrepository task=task_name [folder_name=<path>]

 

Environment

Qlik Replicate 

 

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

Related Content 

Importing Qlik Replicate Tasks/Repository

Labels (1)
Comments
AlexPolorotov
Partner Ambassador
Partner Ambassador

One problem we ran into with task exports was keeping track of changes between versions. Reusing tasks involved hand-editing exported JSON, and our history depended on someone remembering to save a copy.

A useful next step after the export described here is to keep those definitions in Git: commit the current export before editing a task, then export again, review the diff and commit with a short explanation of why it changed. That gives the next person both the configuration and the reason behind it.

We built this workflow into Gitoqlok, a browser extension that connects Replicate tasks to Git. It lets us review changes made in the Replicate console before committing and restore a saved task definition as a full replacement.

Versioning task definitions complements full backup and recovery; the exported JSON does not preserve the task’s running state.

We wrote up the workflow here: Export/Import with Git for Qlik Replicate Tasks.

Version history
Last update:
‎2023-06-15 04:53 AM
Updated by: