> For the complete documentation index, see [llms.txt](https://docs.fabricplan.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fabricplan.com/documentation/readme/disaster-recovery-for-plan.md).

# Disaster recovery for Plan

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.

<figure><img src="/files/9MPrXLHh8vz5a7pU7VJA" alt=""><figcaption></figcaption></figure>

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\. Select the plan item(s) to upload to the repository and select **Commit**.

<figure><img src="/files/BUk0R7anK2BLuht1DSCw" alt=""><figcaption></figcaption></figure>

4\. Confirm that the **Git status** of plan items is *Synced*.

5\. 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.

{% hint style="info" %}
Only the planning sheet structure and setting are recovered from Git integration.

Data input values, notes, and comments entered in the planning sheet will not be automatically restored. It requires Fabric SQL restore.

Semantic model data also needs to be recovered separately.
{% endhint %}

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:** Sheet properties (formatting, conditional formatting, etc.), comment settings, writeback settings, data input columns, data input rows, scenarios, and bookmarks.
* **Infobridge:** Infobridge sources, infobridge 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 sheets that use file-based sources.
* **Intelligence:** All charts and matrices, insert sheets.

### Fabric SQL restore

Data inputs and comments in planning sheets, 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](https://learn.microsoft.com/en-us/fabric/security/experience-specific-guidance#sql-database) section.

### Related Documentation

* [Microsoft Fabric disaster recovery guide](https://learn.microsoft.com/en-us/fabric/security/disaster-recovery-guide)
* [Fabric experience-specific DR guide](https://learn.microsoft.com/en-us/fabric/security/experience-specific-guidance)
* [Fabric SQL SqlPackage reference](https://learn.microsoft.com/en-us/fabric/database/sql/sqlpackage)
* [OneLake disaster recovery](https://learn.microsoft.com/en-us/fabric/onelake/onelake-disaster-recovery)
* [Fabric Git integration](https://learn.microsoft.com/en-us/fabric/cicd/git-integration/intro-to-git-integration)
* [Integrate OneLake with Azure storage explorer](https://learn.microsoft.com/en-us/fabric/onelake/onelake-azure-storage-explorer)
* [Fabric Plan documentation](https://learn.microsoft.com/en-us/fabric/iq/plan/overview)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fabricplan.com/documentation/readme/disaster-recovery-for-plan.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.