Forum Discussion
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 the entire Fabric environment (Lakehouses, Warehouses, Pipelines, Dataflows, Notebooks, etc). Here are my main questions:
- Are there native backup options available in Fabric?
If so, how can I restore the infrastructure to a specific point in time? - Are backups granular?
For example, is it possible to restore an individual workspace or a specific Lakehouse? - If Fabric does not currently support backups,
is there any recommended service or approach to implement backups across the entire infrastructure?
I’ve discovered that some backups exist at the BLOB level for Lakehouses. However, managing these becomes extremely difficult when dealing with hundreds or thousands of files changing daily—especially with checkpoint files from Notebooks that are constantly being created and deleted.
Any insights or recommendations would be greatly appreciated!
Best regards,
André Nelson Matias e Silva
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.
9 Replies
Except SQL Database in fabric non of the others support native backup feature. Could you please go through this Microsoft Offcial documentation Automatic backups in SQL database - Microsoft Fabric | Microsoft Learn you will get a fare idea.
If I come to speacifica point in time wrt to SQL Database, as mentioned in documentation 'All new and restored SQL databases in Fabric retain sufficient backups to allow a point-in-time restore (PITR) within the last seven days by default' Please read this documentation Restore a database from a backup - Microsoft Fabric | Microsoft Learn It might helps you.
In granularity sense, as mentioend above except SQL Dataabses non of others are supported. Other stratagies you can follow
- specific disaster recovery method Microsoft Fabric disaster recovery experience specific guidance - Microsoft Fabric | Microsoft Learn
- Version control using git for notebooks, piepliens and manula back up and storing it in Azure services.
Please let me know if it helps you.
Thank you!
Did I answer your question? Mark my post as a solution!
Proud to be a Super User!Hello suparnababu8
Thank you very much for your answer!
If I understood correctly, the recommended approach for backups is to create a new capacity in another region and replicate all the data there. This would essentially serve as a backup for OneLake. For Notebooks, Pipelines, Semantic Models, and Reports, the best practice seems to be using GitHub integration.
So, would it be fair to say that backups in Fabric are the user's responsibility, and not something that Microsoft currently provides as a built-in feature?
Just want to confirm if my interpretation is correct.Thanks again for your help!
André Silva
yes you are correct. Fabric currenly doesn't offering native backup solution, so it should be user responsibilty. May be we can expect this feature in future.
While coming to onelake, yes you can use cross region or disater recovery as mentined in above reply. So, you can create new capacity in another region and you can maiant back up there.
As you said, remaining Fabric notebooks, daatflows, semantic models and report you can use GitHu inyegration method.
Please let me know if it helps you!
Thank you!!
Did I answer your question? Mark my post as a solution!
Proud to be a Super User!
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.
Thank you for submitting your question to the Microsoft Fabric Community Forum, and thanks to suparnababu8 and Shahid12523 for offering helpful suggestions.
Could you let us know if the suggested solution resolved your issue?If you still need help, please share more details so we can assist you further.
Thank you.
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
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.
We have not yet received a response regarding your query. Could you please confirm if your issue has been resolved? If not, kindly provide additional details so we can offer further assistance.
Thank you.
Hi Asilva_Altice
Just checking in as we haven't received a response to our previous message. Were you able to review the information above? Let us know if you have any additional help.
Thank You.
