Disaster recovery for Plan
Experience-Specific Recovery Procedures for Planning in Fabric IQ
This guide walks you through the recovery procedures for the plan experience in IQ. It covers plan templates & app definitions, writeback data, approval workflows & cell-level comments, source data, and semantic models.
Git integration to restore plan items
The preferred approach is to synchronize all plan items with an Azure DevOps (ADO) or GitHub repository using Fabric Git integration. After failover, the repository is used to rebuild items in the new workspace. The diagram illustrates this workflow.
Pre-disaster (proactive steps):
1. In workspace W1, go to Workspace Settings and configure Git integration.
2. Select Connect and sync with your ADO or GitHub repository.
3. Confirm that all plan items appear as synced in the Source Control panel.
4. Establish a commit discipline - commit after every significant change to a plan definition so the repo always reflects the latest state.
Post-disaster (recovery steps):
1. Create a new workspace W2 inside capacity C2 in the healthy region.
2. In W2, go to Workspace Settings and reconnect to the same ADO/GitHub repository.
3. Select Source Control. Select the relevant repository branch and select Update All. All plan items are downloaded to W2.
Tip: Use the same workspace name (W1) in the new region whenever possible. Many plan configurations reference workspace names, and reusing the name minimises the number of reconnection steps.
The following components are restored after recovery:
PowerTable sheets: Source table settings, column configuration, row access, visual properties (layout, formats, etc.), row identification, comment settings, slowly changing dimensions (SCD), approvals, automations, and forms.
Planning sheets: Workload (item), workload entity (sheet), visual properties (formatting, conditional formatting, etc.), comment settings, writeback settings, data input columns, data input rows, scenarios, and bookmarks.
Infobridge: IB sources, IB queries, transformation steps, writeback destinations, writeback settings, linked query mappings, query groups, visual properties (blend). These items can't be recovered: file-based sources (CSV, Excel), cross-workload visuals that use file-based sources.
Intelligence: All charts and matrices, insert sheets
Fabric SQL restore
Plan metadata, tables used in PowerTable, and writeback data are stored in SQL databases and must be considered as part of your disaster recovery strategy.
Restore plan metadata
Each plan item is associated with a __fabric_plan_sys database that stores metadata for planning features, including comments, scenarios, data inputs, and writeback configuration.
The __fabric_plan_sys database is not restored automatically and must be explicitly recovered.
Restore writeback databases
If your plan uses SQL writeback destinations, the associated databases must also be recovered manually. Configured SQL writeback destinations are not restored automatically.
Restore tables used in PowerTable
Any tables created using PowerTable are stored in a Fabric SQL database. These tables must also be recovered during DR.
To recover SQL databases, see the SQL database section.
Related Documentation
Last updated
Was this helpful?