Edit

Share via

Experience-specific disaster recovery guidance

  • Article

This document provides experience-specific guidance for recovering your Fabric data in the event of a regional disaster.

Sample scenario

A number of the guidance sections in this document use the following sample scenario for purposes of explanation and illustration. Refer back to this scenario as necessary.

Let's say you have a capacity C1 in region A that has a workspace W1. If you've turned on disaster recovery for capacity C1, OneLake data will be replicated to a backup in region B. If region A faces disruptions, the Fabric service in C1 fails over to region B.

The following image illustrates this scenario. The box on the left shows the disrupted region. The box in the middle represents the continued availability of the data after failover, and the box on the right shows the fully covered situation after the customer acts to restore their services to full function.

Diagram showing a scenario for disaster, failover, and full recovery.

Here's the general recovery plan:

  1. Create a new Fabric capacity C2 in a new region.

  2. Create a new W2 workspace in C2, including its corresponding items with same names as in C1.W1.

  3. Copy data from the disrupted C1.W1 to C2.W2.

  4. Follow the dedicated instructions for each component to restore items to their full function.

Experience-specific recovery plans

The following sections provide step-by-step guides for each Fabric experience to help customers through the recovery process.

Data Engineering

This guide walks you through the recovery procedures for the Data Engineering experience. It covers lakehouses, notebooks, and Spark job definitions.

Lakehouse

Lakehouses from the original region remain unavailable to customers. To recover a lakehouse, customers can re-create it in workspace C2.W2. We recommend two approaches for recovering lakehouses:

Approach 1: Using custom script to copy Lakehouse Delta tables and files

Customers can recreate lakehouses by using a custom Scala script.

  1. Create the lakehouse (for example, LH1) in the newly created workspace C2.W2.

  2. Create a new notebook in the workspace C2.W2.

  3. To recover the tables and files from the original lakehouse, refer to the data with OneLake paths such as abfss (see Connecting to Microsoft OneLake). You can use the code example below (see Introduction to Microsoft Spark Utilities) in the notebook to get the ABFS paths of files and tables from the original lakehouse. (Replace C1.W1 with the actual workspace name)

    mssparkutils.fs.ls('abfs[s]://<C1.W1>@onelake.dfs.fabric.microsoft.com/<item>.<itemtype>/<Tables>/<fileName>')

  4. Use the following code example to copy tables and files to the newly created lakehouse.

    1. For Delta tables, you need to copy table one at a time to recover in the new lakehouse. In the case of Lakehouse files, you can copy the complete file structure with all the underlying folders with a single execution.

    2. Reach out to the support team for the timestamp of failover required in the script.

    %%spark
val source="abfs path to original Lakehouse file or table directory"
val destination="abfs path to new Lakehouse file or table directory"
val timestamp= //timestamp provided by Support

mssparkutils.fs.cp(source, destination, true)

val filesToDelete = mssparkutils.fs.ls(s"$source/_delta_log")
    .filter{sf => sf.isFile && sf.modifyTime > timestamp}

for(fileToDelte <- filesToDelete) {
    val destFileToDelete = s"$destination/_delta_log/${fileToDelte.name}"
    println(s"Deleting file $destFileToDelete")
    mssparkutils.fs.rm(destFileToDelete, false)
}

mssparkutils.fs.write(s"$destination/_delta_log/_last_checkpoint", "", true)

  5. Once you run the script, the tables will appear in the new lakehouse.

Approach 2: Use Azure Storage Explorer to copy files and tables

To recover only specific Lakehouse files or tables from the original lakehouse, use Azure Storage Explorer. Refer to Integrate OneLake with Azure Storage Explorer for detailed steps. For large data sizes, use Approach 1.

Note

The two approaches described above recover both the metadata and data for Delta-formatted tables, because the metadata is co-located and stored with the data in OneLake. For non-Delta formatted tables (e.g. CSV, Parquet, etc.) that are created using Spark Data Definition Language (DDL) scripts/commands, the user is responsible for maintaining and re-running the Spark DDL scripts/commands to recover them.

Notebook

Notebooks from the primary region remain unavailable to customers and the code in notebooks won't be replicated to the secondary region. To recover Notebook code in the new region, there are two approaches to recovering Notebook code content.

Approach 1: User-managed redundancy with Git integration (in public preview)

The best way to make this easy and quick is to use Fabric Git integration, then synchronize your notebook with your ADO repo. After the service fails over to another region, you can use the repo to rebuild the notebook in the new workspace you created.

  1. Setup Git integration and select Connect and sync with ADO repo.

    Screenshot showing how to connect and sync notebook with ADO repo.

    The following image shows the synced notebook.

    Screenshot showing notebook synced with ADO repo.

  2. Recover the notebook from the ADO repo.

    1. In the newly created workspace, connect to your Azure ADO repo again.

      Screenshot showing notebook reconnected to ADO repo.

    2. Select the Source control button. Then select the relevant branch of the repo. Then select Update all. The original notebook will appear.

      Screenshot showing how to update all notebooks on a branch.

      Screenshot showing original note recreated.

    3. If the original notebook has a default lakehouse, users can refer to the Lakehouse section to recover the lakehouse and then connect the newly recovered lakehouse to the newly recovered notebook.

      Screenshot showing how to connect a recovered lakehouse to a recovered notebook.

    4. The Git integration doesn't support syncing files, folders, or notebook snapshots in the notebook resource explorer.

      1. If the original notebook has files in the notebook resource explorer:

        1. Be sure to save files or folders to a local disk or to some other place.

        2. Re-upload the file from your local disk or cloud drives to the recovered notebook.

      2. If the original notebook has a notebook snapshot, also save the notebook snapshot to your own version control system or local disk.

        Screenshot showing how to run notebook to save snapshots.

        Screenshot showing how to save notebook snapshots.

For more information about Git integration, see Introduction to Git integration.

Approach 2: Manual approach to backing up code content

If you don't take the Git integration approach, you can save the latest version of your code, files in the resource explorer, and notebook snapshot in a version control system such as Git, and manually recover the notebook content after a disaster:

  1. Use the "Import notebook" feature to import the notebook code you want to recover.

    Screenshot showing how to import notebook code.

  2. After import, go to your desired workspace (for example, "C2.W2") to access it.

  3. If the original notebook has a default lakehouse, refer to the Lakehouse section. Then connect the newly recovered lakehouse (that has the same content as the original default lakehouse) to the newly recovered notebook.

  4. If the original notebook has files or folders in the resource explorer, re-upload the files or folders saved in the user's version control system.

Spark Job Definition

Spark job definitions (SJD) from the primary region remain unavailable to customers, and the main definition file and reference file in the notebook will be replicated to the secondary region via OneLake. If you want to recover the SJD in the new region, you can follow the manual steps described below to recover the SJD. Note that historical runs of the SJD won't be recovered.

You can recover the SJD items by copying the code from the original region by using Azure Storage Explorer and manually reconnecting Lakehouse references after the disaster.

  1. Create a new SJD item (for example, SJD1) in the new workspace C2.W2, with the same settings and configurations as the original SJD item (for example, language, environment, etc.).

  2. Use Azure Storage Explorer to copy Libs, Mains and Snapshots from the original SJD item to the new SJD item.

    Screenshot showing how to copy from the original spark job definition to the new spark job definition.

  3. The code content will appear in the newly created SJD. You'll need to manually add the newly recovered Lakehouse reference to the job (Refer to the Lakehouse recovery steps). Users will need to reenter the original command line arguments manually.

    Screenshot showing command line arguments to recover spark job definition.

Now you can run or schedule your newly recovered SJD.

For details about Azure Storage Explorer, see Integrate OneLake with Azure Storage Explorer.

Data Science

This guide walks you through the recovery procedures for the Data Science experience. It covers ML models and experiments.

ML Model and Experiment

Data Science items from the primary region remain unavailable to customers, and the content and metadata in ML models and experiments won't be replicated to the secondary region. To fully recover them in the new region, save the code content in a version control system (such as Git), and manually rerun the code content after the disaster.

  1. Recover the notebook. Refer to the Notebook recovery steps.

  2. Configuration, historically run metrics, and metadata won't be replicated to the paired region. You'll have to rerun each version of your data science code to fully recover ML models and experiments after the disaster.

Data Warehouse

This guide walks you through the recovery procedures for the Data Warehouse experience. It covers warehouses.

Warehouse

Warehouses from the original region remain unavailable to customers. To recover warehouses, use the following two steps.

  1. Create a new interim lakehouse in workspace C2.W2 for the data you'll copy over from the original warehouse.

  2. Populate the warehouse's Delta tables by leveraging the warehouse Explorer and the T-SQL capabilities (see Tables in data warehousing in Microsoft Fabric).

Note

It's recommended that you keep your Warehouse code (schema, table, view, stored procedure, function definitions, and security codes) versioned and saved in a safe location (such as Git) according to your development practices.

Data ingestion via Lakehouse and T-SQL code

In newly created workspace C2.W2:

  1. Create an interim lakehouse "LH2" in C2.W2.

  2. Recover the Delta tables in the interim lakehouse from the original warehouse by following the Lakehouse recovery steps.

  3. Create a new warehouse "WH2" in C2.W2.

  4. Connect the interim lakehouse in your warehouse explorer.

    Screenshot of warehouse Explorer during warehouse recovery.

  5. Depending on how you're going to deploy table definitions prior to data import, the actual T-SQL used for imports can vary. You can use INSERT INTO, SELECT INTO or CREATE TABLE AS SELECT approach to recover Warehouse tables from lakehouses. Further in the example, we would be using INSERT INTO flavor. (If you use the code below, replace samples with actual table and column names)

    USE WH1

INSERT INTO [dbo].[aggregate_sale_by_date_city]([Date],[City],[StateProvince],[SalesTerritory],[SumOfTotalExcludingTax],[SumOfTaxAmount],[SumOfTotalIncludingTax], [SumOfProfit])

SELECT [Date],[City],[StateProvince],[SalesTerritory],[SumOfTotalExcludingTax],[SumOfTaxAmount],[SumOfTotalIncludingTax], [SumOfProfit]
FROM  [LH11].[dbo].[aggregate_sale_by_date_city] 
GO

  6. Lastly, change the connection string in applications using your Fabric warehouse.

Note

For customers who need cross-regional disaster recovery and fully automated business continuity, we recommend keeping two Fabric Warehouse setups in separate Fabric regions and maintaining code and data parity by doing regular deployments and data ingestion to both sites.

Mirrored database

Mirrored databases from the primary region remain unavailable to customers and the settings aren't replicated to the secondary region. To recover it in the event of a regional failure, you need to recreate your mirrored database in another workspace from a different region.

Data Factory

Data Factory items from the primary region remain unavailable to customers and the settings and configuration in data pipelines or dataflow gen2 items won't be replicated to the secondary region. To recover these items in the event of a regional failure, you'll need to recreate your Data Integration items in another workspace from a different region. The following sections outline the details.

Dataflows Gen2

If you want to recover a Dataflow Gen2 item in the new region, you need to export a PQT file to a version control system such as Git and then manually recover the Dataflow Gen2 content after the disaster.

  1. From your Dataflow Gen2 item, in the Home tab of the Power Query editor, select Export template.

    Screenshot showing the Power Query editor, with the Export template option emphasized.

  2. In the Export template dialog, enter a name (mandatory) and description (optional) for this template. When done, select OK.

    Screenshot showing how to export a template.

  3. After the disaster, create a new Dataflow Gen2 item in the new workspace "C2.W2".

  4. From the current view pane of the Power Query editor, select Import from a Power Query template.

    Screenshot showing the current view with Import from a Power Query template emphasized.

  5. In the Open dialog, browse to your default downloads folder and select the .pqt file you saved in the previous steps. Then select Open.

  6. The template is then imported into your new Dataflow Gen2 item.

Data Pipelines

Customers can't access data pipelines in the event of regional disaster, and the configurations aren't replicated to the paired region. We recommend building your critical data pipelines in multiple workspaces across different regions.

Real-Time Intelligence

This guide walks you through the recovery procedures for the Real-Time Intelligence experience. It covers KQL databases/querysets and eventstreams.

KQL Database/Queryset

KQL database/queryset users must undertake proactive measures to protect against a regional disaster. The following approach ensures that, in the event of a regional disaster, data in your KQL databases querysets remains safe and accessible.

Use the following steps to guarantee an effective disaster recovery solution for KQL databases and querysets.

  1. Establish independent KQL databases: Configure two or more independent KQL databases/querysets on dedicated Fabric capacities. These should be set up across two different Azure regions (preferably Azure-paired regions) to maximize resilience.

  2. Replicate management activities: Any management action taken in one KQL database should be mirrored in the other. This ensures that both databases remain in sync. Key activities to replicate include:

    • Tables: Make sure that the table structures and schema definitions are consistent across the databases.

    • Mapping: Duplicate any required mappings. Make sure that data sources and destinations align correctly.

    • Policies: Make sure that both databases have similar data retention, access, and other relevant policies.

  3. Manage authentication and authorization: For each replica, set up the required permissions. Make sure that proper authorization levels are established, granting access to the required personnel while maintaining security standards.

  4. Parallel data ingestion: To keep the data consistent and ready in multiple regions, load the same dataset into each KQL database at the same time as you ingest it.

Eventstream

An eventstream is a centralized place in the Fabric platform for capturing, transforming, and routing real-time events to various destinations (for example, lakehouses, KQL databases/querysets) with a no-code experience. So long as the destinations are supported by disaster recovery, eventstreams won't lose data. Therefore, customers should use the disaster recovery capabilities of those destination systems to guarantee data availability.

Customers can also achieve geo-redundancy by deploying identical Eventstream workloads in multiple Azure regions as part of a multi-site active/active strategy. With a multi-site active/active approach, customers can access their workload in any of the deployed regions. This approach is the most complex and costly approach to disaster recovery, but it can reduce the recovery time to near zero in most situations. To be fully geo-redundant, customers can

  1. Create replicas of their data sources in different regions.

  2. Create Eventstream items in corresponding regions.

  3. Connect these new items to the identical data sources.

  4. Add identical destinations for each eventstream in different regions.