Home › Learn › Databricks interview prep › Backup and recovery

Databricks interview prep · data engineering

Backup and recovery on Azure Databricks

What Azure Databricks gives you for backup and recovery (time travel, RESTORE, UNDROP, clones, storage features) and what you must build, with a practical pattern.

Maintenance commandsRow-level securityCompute choiceJoinsSkew and shuffleAQE, Photon, POCost and performance leversDeclarative and semanticAsset BundlesLakeflow ConnectUniFormVector Searchdbt and ODCSEgress and ingressMaintenance in picturesClustering and compactionMaintenance strategySlow writesBackup and recoveryTaggingQuestion bank

Defaults, limits and preview status change often. Check the current Databricks docs before quoting a number.

Data in storageTable copies (Delta)Code and config in Git orTerraformA tested recovery plan

Four layers; Databricks gives you tools for the first two, you build the rest.

Based on documentation and experience, not tested on an Azure workspace here. Storage features change; check Azure and Databricks documentation, especially for ADLS Gen2 with hierarchical namespace.

Short answer

What comes out of the box, and what you build

NeedOut of the boxYou build
Undo a bad write to a tableDelta time travel and RESTORE (limited by retention and VACUUM)Nothing
Recover a dropped managed tableUNDROP for Unity Catalog managed tables within a window (documented as seven days; check)Nothing
Protect against deleted files or a lost folderADLS soft delete for blobs and containers; locks; immutable storagePolicy and testing
Survive a region outage (data)Geo-redundant storage (GRS/GZRS) copies data to the paired region, asynchronouslyValidation: the copy is not guaranteed to be consistent across a table's log and files
A real, consistent copy of a tableDeep clone (copies data and log; can be re-run incrementally)A scheduled job per table or schema, in another account, subscription or region
Recover notebooks and codeGit foldersDiscipline: everything in Git
Recover jobs, pipelines, clusters, permissionsNothing automaticAsset Bundles or Terraform as the source of truth
Recover Unity Catalog objects (catalogs, schemas, grants, external locations)No backup buttonTerraform or scripts as the source of truth
SecretsKey Vault-backed scopes keep secrets in Key VaultKey Vault backup policy
Full workspace failoverNothing one-clickA secondary workspace, replicated data, config redeployed from code, a runbook, and drills

Recommended

A practical pattern

  1. Make everything reproducible from code: notebooks in Git, jobs and pipelines in Asset Bundles or Terraform, Unity Catalog objects in Terraform.
  2. Keep Delta time travel for mistakes: choose a retention period you can afford and do not VACUUM below it.
  3. Protect storage: soft delete, resource locks, and immutable or write-once storage for the backup account.
  4. Copy important tables with deep clone on a schedule to a separate storage account (ideally another subscription and region). Shallow clones are not backups.
  5. For disaster recovery: a secondary workspace, with the same bundles deployed, reading the replicated data. Decide RPO and RTO per data product, not for everything.
  6. Test restores regularly. An untested backup is a guess.

Traps

Things that surprise people

Practice

Questions to rehearse

  1. Time travel, clone and geo-redundancy: which protects against what?
  2. Why is a shallow clone not a backup?
  3. What would you build for a region failure?
  4. How do you recover jobs and Unity Catalog objects?
  5. How often do you test restores, and how?
In an interview, say: Delta handles table mistakes, storage features handle lost files, and everything else is rebuilt from code. Disaster recovery for a whole workspace is something I design and test, not something I switch on.

FAQ

Questions people ask

Is there a built-in Databricks backup?

For tables, time travel and clones. For workspace objects there is no automatic backup, so use Git and infrastructure as code.

Is geo-redundant storage a backup?

No. It replicates, including deletes and corruption.

Next

Where to go next

All Databricks interview topics · All data engineering · Databricks on this site