Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
All data in OneLake is accessed through data items. These data items can reside in different regions depending on their workspace, because a workspace is created under a capacity that's tied to a specific region.
OneLake uses zone-redundant storage (ZRS) where that storage type is available. (See Azure regions with availability zones.) Elsewhere, OneLake uses locally redundant storage (LRS). With both LRS and ZRS, your data is resilient to transient hardware failures within a datacenter.
Just like for Azure Storage, LRS replicates data within a single datacenter in the primary region. LRS provides at least 99.999999999% (11 nines) durability of objects over a year. This durability helps protect against server rack and drive failures, but not against datacenter disasters.
Meanwhile, ZRS provides fault tolerance to datacenter failures by copying data synchronously across three Azure availability zones in the primary region. ZRS offers a durability of at least 99.9999999999% (12 nines) over a year.
LRS and ZRS provide data protection within the primary region. To protect your data from a region-wide outage, you can enable disaster recovery to replicate your OneLake data to a secondary geographic region.
Disaster recovery
You can enable or disable disaster recovery (DR) for a specific capacity through the capacity admin portal. If your capacity has DR enabled, your data is duplicated and stored in two geographic regions so that it's geo-redundant. The standard region pairings in Azure determine the choice of the secondary region. You can't modify the secondary region.
Important
Enabling disaster recovery might take an extended period of time depending on current resource demands in the region, data size, and other factors. To check status, go to capacity settings and review Workspaces assigned to this capacity. The OneLake Geo-replication column shows the enablement status for each workspace.
If a disaster makes the primary region unrecoverable, OneLake might initiate a regional failover. After the failover finishes, you can use the OneLake APIs through the global endpoint to read and write data in the secondary region. Data replication to the secondary region is asynchronous and occurs at the file level. As a result, a regional failover can result in data loss and inconsistencies between files. The secondary region might not contain a point-in-time-consistent copy of the data. For example, a newer file might be present while an older file that didn't yet replicate is missing.
Note
This recovery guidance applies only when the primary region has an Azure‑paired secondary region and Fabric is supported in the paired region.
For a comprehensive understanding of the end-to-end experience, see Reliability in Fabric.
Soft delete for OneLake files
OneLake automatically protects your data with soft delete, which retains deleted files for seven days before permanent removal. This built-in protection helps you recover from accidental deletions or user errors.
For step-by-step instructions on how to list and restore soft-deleted files, see Recover deleted files in OneLake.