Lakebase Point-in-Time Recovery
GARestores a Lakebase project's data to any moment within its restore window, for example after an accidental deletion or an unwanted schema change. The restore creates a new root branch holding the data as it was at that moment, while the original branch keeps running unchanged. Lakebase also takes snapshots, instant point-in-time captures of a root branch kept as backups and restored by creating a new branch from them. The snapshots API (Beta from September 15, 2026) and the backup schedule API, which sets daily, weekly or monthly snapshot cadences and how long each is kept (Beta from September 22, 2026), have been generally available since October 26, 2026.
Status history
- GA
Sources (6)
- 2026-10-26Release notes
- 2026-10-01Databricks Blog
- 2026-09-22Release notes
- 2026-09-15Release notes
- 2026-05-15Databricks Blog
- 2026-01-22Release notes GA
Recent coverage
- 2026-11-17Branch, sync, serve: What our Lakebase Hackathon taught us about building on Lakebase news
- 2026-11-17Built on object storage, served from cache news
- 2026-11-16Introducing Lakebase Insights video
- 2026-11-16Lakebase Insights: Find and Fix Postgres Issues Before Your Users Do video
- 2026-11-14Databricks is a Leader and positioned highest in execution in the 2026 Gartner® Magic Quadrant™ for Data Lakehouse Platforms news
- 2026-11-12Dispelling LTAP myths news
Get Tuesday's version of this
What shipped in Databricks and why it matters, once a week. Free, one-click unsubscribe.
Statuses and dates come from public Databricks sources only. We do not see the private roadmap Databricks shares with customers. If something looks wrong, report a correction.