Forum Discussion
Post PatronDisaster Recovery in Fabric
Dears,
I have the below architecture in fabric (figure 1)
I need to create the strategy for DR which I will than need to defend at TDA
Not sure very well which topics to cover. I made a quick search and I found this via AI:
I was thinking in considering only the first : Geo-Redundancy
Probably the rest is not relevant
But I would need to understand how GEO works and if it can increase significantly my costs
Questions:
1) Which DR solutions did you implemented on your side? only the first one?
2) This Geo-redundancy option, seems to be bulit-in , can it affect performance?
3) This is activated at which level? capacity level or workspace level?or Item Level?
4) If at capacity level, do I need any specific capacity SKUs? like F16 or above? What does the capacity need to have in order to be able to support this?
4) Probably, this only makes sense for Production environment hence I will only consider production
5) Can we choose the geo-location replica? or when we activate the option , it will automatically choose the region for us to replicate the information and we cannot change it ?
6) Do we know which other region do we have the information replicated to? or we are not able to see it?
7 ) Once a disaster ocurrs what is the time it takes to connect to the other region so that can continue to work?
😎Once the failure ios overcome will we be automatically re-directed to the previous region? or will it stay in the new one?
9) how is the information replicated between GEO locations? via encrypted connection, in transit, so that we people cannot try to compromise it?
10) My capacities and workspaces are in Western Region. Once we activate this option , it will be replicated to where to another location inside europe only, like north europe region , etc... or will it go to another continente?
Thanks a lot,
Pedro
P.S - Are you doing any type of backups in fabric? like the old SQL Server backups that we do it in On-prem solutions? if so, which technology are you using to do the backups?
Figure 1:
Hi fabricpribeiro ,
Fabric DR is different from traditional backup/restore.
> Fabric protects data automatically through OneLake geo-replication (capacity-level, Microsoft-managed, no performance impact).
> This only safeguards the data, it does NOT replicate workspaces, pipelines, or semantic models.So DR in Fabric = Redeploy + Rehydrate, not restore.
In a regional outage:
Microsoft ensures the data is available in the paired region.
Customer redeploys the Fabric environment from Git/source control to resume operations.Minimum recommended setup
Enable Geo-redundancy on Production capacity
Use Git Integration for all Fabric artifacts
Keep a redeployment runbook/scripts ready
Ensure source data can be reprocessed if needed
Test DR periodically.
Hope this helps.
Thank you
3 Replies
fabricpribeiroSorry, just a couple more questions , please:
1 - If I choose geo-redundacy it will be at capacity level that this option is available, right?
2 - The Geo.redundancy means that the data will be replicated inside only Europe regions? or can it be replicated to outside of Europe if my capacity wass created at Western Europe?
3 - If I decide not to activate this option, what do we have as default in fabric for DR? do we have protection at least at data center level with the same data being replicated inside the same data center to multiple different redundant discs?
Thanks,
Pedro
v-echaithraCommunity Support
Hi fabricpribeiro ,
Thank you for your response.Yes, Geo-redundancy (OneLake disaster recovery) is enabled at the Fabric capacity level, not at workspace or item level.
Reference: OneLake Disaster Recovery and Data Protection - Microsoft Fabric | Microsoft LearnReplication follows Azure regional pairing rules. If your capacity is in West Europe, the paired region is North Europe. Azure regional pairing always stays within the same geography (Europe > Europe) for compliance and data residency reasons.
It will not replicate outside Europe. The paired region is automatically selected by Azure and cannot be changed.Even without cross-region Geo-redundancy, Fabric still provides Intra region durability, Redundant storage within the same region, Data replication across fault domains inside Azure datacenters, Encryption at rest and in transit. This protects against Disk failures, Rack failures, Datacenter-level hardware issues inside the same region
However, it does not protect against a full regional outage (e.g., West Europe unavailable).
Even without enabling Geo-redundancy, Microsoft Fabric still provides built-in resiliency within the same region. However, this is High Availability, not full Disaster Recovery.
Hope this helps.
Thank you.
- v-echaithra
Hi fabricpribeiro ,
Fabric DR is different from traditional backup/restore.
> Fabric protects data automatically through OneLake geo-replication (capacity-level, Microsoft-managed, no performance impact).
> This only safeguards the data, it does NOT replicate workspaces, pipelines, or semantic models.So DR in Fabric = Redeploy + Rehydrate, not restore.
In a regional outage:
Microsoft ensures the data is available in the paired region.
Customer redeploys the Fabric environment from Git/source control to resume operations.Minimum recommended setup
Enable Geo-redundancy on Production capacity
Use Git Integration for all Fabric artifacts
Keep a redeployment runbook/scripts ready
Ensure source data can be reprocessed if needed
Test DR periodically.
Hope this helps.
Thank you