Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Grow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.

Reply
alfBI
Advocate II
Advocate II

Lakehouse/Warehouse Backups ?

Hi,

 

It might looks a stupid question but after some time working with Fabric I have not yet a clear idea about how to handle data recovery in situations such as a mistake deleting a Fabric artifacts (e.g: a warehouse/lakehouse) or try to recover the content of a table on a lakehouse/warehouse that has been accidentally removed or deleted.

 

Using Azure SQL or SQL on premise these questions have an obvious answer because these tools have a plethora of backup mechanism to manage these scenarios. But, what happens in Fabric? 

 

Thx

 

Alfons

1 ACCEPTED SOLUTION
v-gchenna-msft
Community Support
Community Support

Hi @alfBI ,

Thanks for using Fabric Community.
We have Data Recovery option in Fabric Warehouse.  Can you please refer below document?

Docs to refer - 
Restore in-place of a warehouse from a restore point - Microsoft Fabric | Microsoft Learn
The Art of Data warehouse recovery within Microsoft Fabric | Microsoft Fabric Blog | Microsoft Fabri...

Hope this is helpful. Please let me know incase of further queries.

View solution in original post

5 REPLIES 5
frithjof_v
Continued Contributor
Continued Contributor

Can the Data Warehouse recovery actually restore a deleted warehouse?

 

Or only recover old data (old snapshot) of an existing warehouse?

 

It seems you need the warehouse GUID in order to recover data warehouse to an earlier version.

https://blog.fabric.microsoft.com/nb-NO/blog/the-art-of-data-warehouse-recovery-within-microsoft-fab... 

 

How to get the GUID if the data warehouse has already been deleted? 

And will the recovery work if the data warehouse has already been deleted?

NandanHegde
Super User
Super User

Hey,

Based on my understanding, Unfortunately as of today there is no backup aspect for fabric lakehouse
Currently there is no backup support of lakehouses. The best you can do is manually replicate the data to another lakehouse. 

Similar thread : https://community.fabric.microsoft.com/t5/General-Discussion/Lakehouse-Backup/td-p/3657787#:~:text=U....


For fabirc warehouse,you can follow the lniks shared in another reply here and can make use of restore point

v-gchenna-msft
Community Support
Community Support

Hi @alfBI ,

Thanks for using Fabric Community.
We have Data Recovery option in Fabric Warehouse.  Can you please refer below document?

Docs to refer - 
Restore in-place of a warehouse from a restore point - Microsoft Fabric | Microsoft Learn
The Art of Data warehouse recovery within Microsoft Fabric | Microsoft Fabric Blog | Microsoft Fabri...

Hope this is helpful. Please let me know incase of further queries.

Hi v-gchenna-msft,

 

I have been redafing the blog you mentioned aloingside and the official MS docs about Fabric disaster recovery. My conclusion after carefully reading both is that data recovery on Fabric data engineering (WH & LH)) mainly relies on delta table capabilities to restore a table at a specific point in time using time travel. 

To take leverage of delta tables timeline capabilities for managing data recovery scenarios is not bad on its own, but (and this is my main concern) this approach misses other disaster recovery scenarios where  restoration is required at item level (whole warehouse/lakehouse, tables/views/ storeprocedures/notebooks).

 

How to proceed if a table/view/store procedure has been completely removed from the WH? Or even worse , what about the whole WH/LH as has been "accidentally" dropped?

 

In such a cases MS docs provides 2 options

 

1) make use of "Disaster recovery capacity setting" to keep a copy of all Fabric items (which includes WH/LH) on a secondary region. OK, this may work, but sounds to me as using a sledgehammer to crack a nut. (Leaving aside the extra cost)

 

2) Another suggestion option is keep WH code (table, view, stored procedure) versioned and saved in a safe location (such as Git). I certainly prefer this last one, but git is primarily a version control system rather than a traditional backup tool.

 

In summary, imho MS provides workarounds on Fabric for managing disastery recovery scenarios but any of them might be fully considered as "actual" backup methods (at least as I understand them).

 

I firmly belive that MS should consider for future Fabric releases some kind of pure-backup mechanism (not based on tables timeline or versioned git code)

 

Regards,

 

Alfons

 

Thanks,

Hi @alfBI ,

Glad to know that your query got resolved. Please continue using Fabric Community on your further queries.

Helpful resources

Announcements
RTI Forums Carousel3

New forum boards available in Real-Time Intelligence.

Ask questions in Eventhouse and KQL, Eventstream, and Reflex.

Expanding the Synapse Forums

New forum boards available in Synapse

Ask questions in Data Engineering, Data Science, Data Warehouse and General Discussion.

MayFabricCarousel

Fabric Monthly Update - May 2024

Check out the May 2024 Fabric update to learn about new features.

Top Kudoed Authors