Why Qlik teams need more than the built-in safeguards
Qlik Sense includes a repository backup; Qlik Cloud includes a recycle bin and limited retention. Both help against the smallest accidents, but neither is a recovery platform. Most outages we see at customer sites do not come from infrastructure failure — they come from human mistakes: a sheet deleted before a meeting, a measure overwritten by a junior developer, a deployment that replaces a production app with an older version, a tenant reorganization that drops a space full of shared dashboards.
Active Backup for Qlik is engineered for exactly these situations. It runs in parallel to your Qlik environment, captures every change as an independent restore point, and gives operators the ability to recover the right object, at the right moment, without rebuilding from scratch or losing concurrent developer work.
Continuous, change-driven backup
Traditional schedules — nightly, weekly — are unfit for analytics workloads that change dozens of times a day. Active Backup for Qlik runs continuously and synchronously: when an application, sheet, automation or data connection changes, a new recovery point is created. Developer applications are protected at no extra license cost so experimentation never jeopardises the work itself.
- No cron jobs, no scheduled export windows, no nightly outages to coordinate.
- Incremental capture — only what changed is stored, keeping the footprint predictable.
- Per-stream and per-space retention policies aligned to business and compliance needs.
- Out-of-band: zero impact on developers in the Hub or end users consuming dashboards.
Granular, point-in-time recovery
Recovery in Qlik is rarely about restoring a whole environment. It is almost always about a specific object, at a specific moment, before a specific mistake. Active Backup for Qlik lets operators pick the affected asset — a sheet, a story, a bookmark, a master library measure, a private object, a full application — and the precise recovery point, then restore in place or to a validation space.
Multi-developer co-development is preserved. Restoring a sheet that one developer broke does not roll back the changes their colleagues made on other sheets in the same application. This is the difference between a backup tool and a recovery platform built for the way Qlik teams actually work.
Version history that an auditor can read
Every recovery point is also a version. Operators and auditors can browse the history of any asset, see who changed what and when, compare iterations, and roll back to a known-good version. Version history is the foundation of safe releases, fast troubleshooting and defensible audit evidence — without depending on developer discipline or ad-hoc PowerPoint changelogs.
Disaster recovery, defined per workload
Disaster recovery is not the same as backup. Backup creates the copies; DR is the plan, the owners and the tested workflow that brings critical Qlik workloads back inside an agreed window. Active Backup for Qlik lets you define a Recovery Point Objective (RPO) and a Recovery Time Objective (RTO) per workload — not per platform — and proves those numbers with real recovery drills.
Full Qlik Cloud tenant coverage
When teams talk about backing up Qlik Cloud, they usually mean apps. A tenant is much more. Active Backup for Qlik protects the entire tenant configuration alongside the analytics content, so a recovery is a true recovery — not a rebuild.
- Tenant: users, groups, API keys, identity providers, webhooks, themes, files, email configuration.
- Automation layer: automations, automation connections, data connections.
- Spaces: personal, shared, managed and data spaces with assignments.
- Applications: analytics apps, script apps, data flows, sheets, stories, bookmarks, schedules, alerts and subscriptions.
Qlik Sense Enterprise on Windows
For Qlik Sense Enterprise, Active Backup integrates with the supported repositories (Oracle, MSSQL, MySQL, MariaDB) and captures applications, sheets, stories, bookmarks, master library items, private objects, streams, tasks and data connections — without plug-ins, browser add-ons or developer intervention.
Active Backup for Qlik vs the alternatives
| Capability | Manual export | Native Qlik safeguards | Active Backup for QlikRecommended |
|---|---|---|---|
| Continuous capture | No | Partial | Yes |
| Object-level restore (sheet, bookmark, master item) | No | No | Yes |
| Point-in-time recovery | Only the last export | Limited retention | Any change, any moment |
| Preserves concurrent developer work | No | No | Yes |
| Tenant configuration coverage (Qlik Cloud) | No | Partial | Yes |
| Audit-ready version history | No | No | Yes |
| Operator time per recovery | Hours to days | Hours | Minutes |
Frequently asked questions
Does Qlik Sense or Qlik Cloud include a real backup?+
No. Qlik Sense ships with a repository backup that protects metadata at the database level, and Qlik Cloud offers a recycle bin with limited retention. Neither produces granular, point-in-time restore points for individual sheets, bookmarks, master items, or private objects. Independent backup is required for governance, audit and fast object-level recovery.
How often does Active Backup for Qlik create a recovery point?+
Continuously. Every time an asset changes — a sheet edit, a published app, a new automation, a connection update — a new recovery point is created. There are no schedules to maintain and no nightly export jobs to babysit. Retention is policy-driven per stream or space.
Can a single sheet, bookmark or master item be restored without touching the rest of the app?+
Yes. Granular restore is the core design principle. You select the exact object and the exact point in time, and the platform restores it in place — or into a validation space — without overwriting concurrent developer work. Multi-developer co-development is preserved end-to-end.
What part of a Qlik Cloud tenant is actually protected?+
The full tenant configuration plus all application content: users, groups, API keys, identity providers, webhooks, collections, themes, files, automations, automation connections, data connections, spaces (personal/shared/managed/data), analytics apps, script apps, data flows, sheets, stories, bookmarks, reload schedules, alerts and subscriptions.
How does Active Backup for Qlik support compliance and audit requirements?+
Backups are stored independently from the Qlik service with policy-driven retention. Every change is timestamped, attributed to a user and reversible. Auditors get a verifiable trail of what existed when, who changed it, and how it was recovered — a standard control for SOX, ISO 27001, HIPAA and GDPR-aligned environments.
Will continuous backup slow down Qlik developers or end users?+
No. The platform is zero-touch — developers keep working in the Hub or in Spaces, end users keep consuming dashboards. Backups are out-of-band and incremental, with no plug-ins, no browser add-ons and no manual export step.