Forum Discussion
Fabric Backups
- 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.
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.