Forum Discussion

Asilva_Altice's avatar
Asilva_Altice
Regular Visitor
1 year ago
Solved

Fabric Backups

Hello, good morning!   I have a question regarding backup capabilities within the Microsoft Fabric infrastructure. Specifically, I’m looking to understand whether it's possible to create backups of...
admin
  • Shahid12523's avatar
    Shahid12523
    1 year ago

    No native full backup/restore feature exists yet in Microsoft Fabric for entire workspaces (Lakehouses, Warehouses, Pipelines, Dataflows, Notebooks).

     

    Granular recovery: Some automatic redundancy & BLOB-level backups exist (esp. for Lakehouses via OneLake/ADLS under the hood).

     

    Point-in-time restore isn’t supported today for Fabric items.

     

    Workarounds / recommendations:

    Use source control (Git integration) for Notebooks, Dataflows, Pipelines.

    Use OneLake APIs / ADLS Gen2 APIs or Fabric REST APIs to regularly export metadata and data.

    For structured data (Lakehouse/Warehouse), rely on delta tables which inherently support versioning/time travel.

    For enterprise backup, implement Azure Backup / custom scripts against OneLake storage.

    Bottom line: Backups are limited & manual right now; best practice is Git for code + OneLake/Delta for data.

Asilva_Altice's avatar
Asilva_Altice
Regular Visitor
1 year ago

Hello v-karpurapud 

 

First, thank you to suparnababu8  and to Shahid12523 for sharing their insites. The backup of an infrastructure is always a must have in my organization. Is it on the roadmap of Fabric to add that capability?

 

Thank you,

André Silva

v-karpurapud's avatar
v-karpurapud
Community Support
1 year ago

Hi Asilva_Altice 

Microsoft Fabric currently does not offer a native full backup and restore capability for entire workspaces. The only built-in backup feature is automatic point-in-time restore (PITR) for Fabric SQL Databases, which includes weekly full, differential, and transaction log backups with a 7-day retention period. For all other artifacts such as Lakehouses, Pipelines, Dataflows, Notebooks, Reports, and Semantic Models the responsibility for backup and recovery lies with the customer. Microsoft recommends leveraging Delta Lake versioning and OneLake redundancy for data resilience, using Git integration or REST API-based exports for code and metadata, and implementing cross-region replication or Azure Backup for disaster recovery. In essence, while Fabric provides resiliency for select components, a comprehensive backup strategy requires a combination of storage features, source control practices, and automation tailored to the organization’s needs.

 

For the latest updates and roadmap, please refer to the official Microsoft Fabric roadmap here:
Microsoft Fabric Roadmap and Announcing backup storage billing for SQL database.

Regards,

Microsoft Fabric Community Support.