Skip to content
Baseout Support
Draft — this is a structural skeleton, not documentation. Most pages are empty stubs listing what they will cover. Nothing here is finished, and some of it describes parts of Baseout that are not built yet.

How backups work

A backup run is one execution of the backup process for a Space. It writes a snapshot of the bases you included to your Destination, and it is recorded permanently in the Space’s backup history — a run is a log entry, not something you edit.

This page will explain what a run captures, the difference between a full run and a schema-only run, and the four things that can start one: the schedule, you pressing Run backup now, a webhook, or a trial run.

Questions this page will answer

Section titled “Questions this page will answer”
  • What does a run capture — records, fields, views, attachments, all of it?
  • What is the difference between a Full run and a Schema run?
  • What triggers a run: Scheduled, Manual, Webhook, Trial?
  • Does a backup ever change anything in my Airtable base?
  • What happens if my schema changed since the last run?

Not written yet

Section titled “Not written yet”

Everything past the two paragraphs above. The exact capture boundary — what a run does and does not include — is the part that has to be right and is not drafted.