Skip to main content

​
What this check does

Checks backup. Passes when: Backup enabled.

​
Why this matters

Disaster recovery.

​
How to fix

Back up Databricks workspace content
  1. Sign in to the Azure Portal and open your Azure Databricks workspace to identify its underlying storage — the managed DBFS root storage account and any mounted Azure Storage accounts.
  2. Enable backup for those storage accounts (e.g. Backup center → + Backup → Azure Blobs, or geo-redundant storage replication).
  3. Export notebooks, jobs, and cluster configurations on a schedule using the Databricks REST API (/api/2.0/workspace/export) or the Databricks CLI.
  4. Automate the export with Azure Functions or Logic Apps and write the output to a backed-up storage account.
Once resolved, DSALTA records a 200 (compliant) result on this test’s Source Data tab at the next scheduled run.

​
Frequently asked questions

Once a day, at 02:00 America/New_York, while the integration is connected. A run is skipped entirely if the integration is not in a connected state, or if the test has been deactivated.To see a fix reflected sooner, open the test from Data Library → Tests and click Run in the Run Test row. You need Full Access to run a test on demand.
The Status column answers “did the check run?”, not “did I pass”. Completed means DSALTA reached your system and finished evaluating — a check that ran and found a problem is still Completed.To see what it found, open the test and read the result code on the Source Data tab. 200 means nothing to fix; 204 means the check did not apply to your environment; 207 means it ran and found a compliance gap you need to act on. See Understanding test results.
Usually not. On an integration-powered check, Failed means DSALTA was blocked and could not evaluate it — result code 403 (a missing permission) or 428 (a setting DSALTA still needs from you). Code 500 means the run failed on DSALTA’s side.A genuine compliance gap does not turn the list red — it runs to completion and shows 207.
Deactivate it: open the test from Data Library → Tests, then use the ⋮ menu at the top right of the panel and choose Deactivate Test. It applies immediately, with no confirmation step.Write your justification in the Comments tab before you deactivate. Once deactivated, every other tab is grayed out, so Comments is the only place an auditor can read why — see Test detail.
No. DSALTA only reads. It never creates, modifies, or deletes resources, and every remediation step is performed by your team directly in the third-party product.