Where Does Self-Hosted Airbyte Store Data?
Airbyte connection database and sync log volume paths on Linux for self-hosted pipelines. And restore steps.
Last updated
Airbyte splits state across containers. Postgres keeps connections and jobs in a volume like airbyte-db. Workspaces keep sync logs and temp files beside it. Both persist through named volumes, not the app container.
Settings come from a .env file with version and secrets. The compose file maps volumes with prefixed names. Back up both volumes with the env file. Connection configs without job history still restore syncing. Normalization builds tables in destinations. Schedules trigger syncs on cron intervals.
Where Airbyte stores this, by platform
airbyte-db (Postgres volume)
Connection and job database volume. Dump Postgres for portable backups instead of raw copies. Inspect for the host mountpoint.
airbyte-workspace (logs volume)
Sync logs and temp files for connector runs. Larger than the database on busy instances. Back up with the env file.
Frequently asked questions
what do i back up for an Airbyte move
Back up the Postgres and workspace volumes with the .env file. The database holds connections. Workspaces hold sync logs. Both restore pipelines. Keep the env safe.
where are Airbyte volumes on the host
Run docker volume ls to list airbyte volumes, then inspect for mountpoints. Names gain a compose prefix like airbyte_db. The .env file holds version and secrets.
Notice an outdated path? Let us know.