Recovery is the only metric that matters
Backup is a means; recovery is the end. The question that matters when something goes wrong in Qlik is not do we have a copy? — it is how fast can we serve the business again? Active Backup for Qlik is engineered around that single outcome.
The vast majority of recoveries we see are not catastrophic infrastructure events. They are everyday operational incidents: a developer overwriting a measure, a deployment promoting an older version of an app, a sheet deleted before an executive review, a Qlik Cloud space reorganised without checking what was inside. The right recovery platform turns each of those from a multi-hour rebuild into a few clicks.
The four-step recovery workflow
- 1
Backup created
Continuous capture creates a recovery point on every change — no schedule to maintain, no nightly window.
- 2
Incident detected
An object is deleted, overwritten, broken by a deployment or removed during a reorganisation.
- 3
Recovery point selected
Search by asset name, owner, space, stream or date. Compare versions side by side when needed.
- 4
Restore complete
Restore in place or into a validation space. Typical elapsed time: minutes.
Real recovery scenarios — and how long they take
Sheet overwritten by a junior developer
Rollback the affected sheet to the previous recovery point. Other sheets in the app — and the work of other developers — remain untouched.
Accidentally deleted application
Full restore including sheets, stories, bookmarks, master items and private objects. The app returns to its original space with owners and assignments preserved.
Bad deployment from dev to prod
Restore the last known-good app version into a validation space, smoke-test the data model, then promote back to the production stream or shared space.
Qlik Cloud space deleted by mistake
Recreate the space with its assignments and recover every analytics app, script app and data flow it contained from the tenant backup.
Reload task or schedule wiped out
Restore tasks, reload schedules, alerts and subscriptions from the most recent recovery point — no manual reconfiguration.
Auditor asks for a 90-day-old version
Surface any historical version of any asset from version history with full attribution: who changed what, when, and from which client.
Granular restore vs full restore — choosing the right scope
The instinct in a panic is to restore everything. That is almost always the wrong call. Full restores overwrite the work other developers did since the last recovery point and disrupt users who were not affected by the original incident. Granular restore is the default choice; full restore is reserved for catastrophic loss of an entire app or space.
| Scope | Use when | Risk to ongoing work | Typical time |
|---|---|---|---|
| Single object (sheet, bookmark, measure) | A specific change broke a specific object. | None — concurrent work is preserved. | Under a minute |
| Full application | The whole app was deleted or corrupted. | Low — restored as an independent copy first. | 1–2 minutes |
| Space or stream | A container and everything inside it was lost. | Medium — review assignments before promotion. | 5 minutes |
| Tenant configuration | Identity, automations or connections must be rebuilt. | Medium — coordinate with platform owners. | 5–15 minutes |
Set RPO and RTO per workload, not per platform
A finance dashboard used at month-end and a self-service exploration sandbox should not share the same recovery objectives. Active Backup for Qlik lets you define a Recovery Point Objective (how much data loss is acceptable, measured in time) and a Recovery Time Objective (how long the business can wait) per stream or per space.
- Tier 1 — business-critical: RPO measured in minutes, RTO under 30 minutes, quarterly drills.
- Tier 2 — operational: RPO under an hour, RTO under four hours, semi-annual drills.
- Tier 3 — exploratory / sandbox: RPO of one day, RTO of one business day, drills as needed.
The decisions that determine recovery quality
- Pick the right recovery point — not the most recent. The most recent often contains the incident itself.
- Restore to a validation space when the incident scope is unclear. Promote back only after smoke tests pass.
- Preserve concurrent work by restoring at the object level whenever possible.
- Log every recovery with operator, asset, recovery point and target — this is your audit trail.
- Run quarterly drills on a non-production tenant to keep operators fluent and prove RTO numbers to leadership.
Recovery FAQs from Qlik administrators
How long does it actually take to recover a deleted Qlik application?+
For a single application with sheets, bookmarks, stories and private objects, a full restore usually completes in one to two minutes. Sheets, master items or bookmarks restored individually are typically back in under a minute. The variable is operator decision time — choosing the correct recovery point — not the platform itself.
Can a Qlik recovery be performed without overwriting concurrent developer work?+
Yes. Recovery is object-aware. Restoring the sheet a developer broke does not roll back the changes their colleagues made elsewhere in the same app. When in doubt, operators restore to a validation space first, review, and then promote back to production.
What is the difference between a backup and a disaster recovery plan for Qlik?+
A backup is the copy. A disaster recovery (DR) plan is the documented workflow, the named owners, the recovery point and recovery time objectives, and the periodic drill that proves the plan works. Active Backup for Qlik provides the backup and the recovery tooling; the DR plan is the operational layer your team owns on top.
How do I recover after a bad deployment from dev to production?+
Identify the impacted application and the timestamp just before the deployment. Select that recovery point in Active Backup for Qlik, restore the app (or only the affected sheets and measures) into a validation space, verify the data model and visualisations, then promote back to the production stream or shared space. Total elapsed time is usually under ten minutes.
Can I recover a Qlik Cloud space that was deleted by mistake?+
Yes. Active Backup for Qlik captures the tenant configuration alongside content, so the space — including its assignments, app assignments, analytics apps, script apps and data flows — can be recreated in its previous state. Identity provider links and API keys can also be restored from the tenant backup.
Does recovery work for automations, data connections and identity providers?+
Yes. The Qlik Cloud tenant backup covers automations, automation connections, data connections, webhooks, themes, identity providers, users, groups and API keys. Sensitive credentials are restored with operator-controlled reconfiguration guidance to respect the principle of least privilege.
What recovery evidence can I show an auditor?+
For every restore, the platform records the asset, the original change time, the recovery point chosen, the operator who performed the restore and the target location. Combined with version history, that produces a complete audit trail of incidents, root causes and recoveries.