Backup OneLake data

[denis_makarenko]

In enterprise environment CISO requires to have dat protection against ransomware.

Backup in most cases an obvious choice but currently there is no way to do it fabric except a custom implementation.

Adding support of OneLake objects to Azure Backup seems to be a good option to solve the problem.

Please add it.

[wayne_yan]

It is theoretically possible for a Parqet file to be encrypted with ransomware when using Onelake file explorer. The automaticy synchronization of files between a desktop (the point of compromise) and the abstracted storage is the weak point.

BCDR will then replicate the encrypted file across all zones.

This scenario would support the original request for backup and management of generations.

[chadrenstrom]

Agreed. We need backups. They are necessary to allow customers to recover from things like ransomware (as you mentioned), user accidents and file corruption. Even if something is under source control, reverting does not recover data.

[S_Rahlf]

Following the idea of "Fabric OneLake data gravity" the main pool of data lies in Fabric - If it's "just" linked/shortcutted data the resposibility for bachup/recovery resides at the sources - check! But for anything else streamed/imported/mirrored the responsibility shifts into OneLake (indirect Warehouse/Eventhouse/SQL DB) in Fabric. And a "forever available re-hydrate of data from sources" will not exist or being practicable... The final and longterm "source of truth" will be OneLake for a majority of use cases and this requires a Backup/DR tooling especially for the most common challenge "oops!" errors leading to partial data loss