Rafael Felipe
03/27/2026, 12:49 PMkapa.ai
03/27/2026, 12:49 PMkubectl cp ./airbyte_backup.sql airbyte/airbyte-db-0:/tmp/airbyte_backup.sql
2. Drop and recreate the schema:
kubectl exec -n airbyte -it airbyte-db-0 -- bash -c "psql -U airbyte -d db-airbyte -c 'DROP SCHEMA public CASCADE; CREATE SCHEMA public;'"
3. Restore the database:
kubectl exec -n airbyte -it airbyte-db-0 -- bash -c "psql -U airbyte -d db-airbyte < /tmp/airbyte_backup.sql"
[Helm chart V2 restore] Important Caveats Regarding CDC specifically: The knowledge sources do not explicitly confirm that restoring the Airbyte internal database will preserve CDC replication slot state and allow you to resume CDC without a full reload. The Airbyte internal database stores connection configurations and sync states, but CDC replication slots live on the source database side.
Regarding version downgrade: The knowledge sources include a strong warning from an Airbyte team member that database schemas differ significantly between versions, making database dumps unreliable across version gaps:
> "We also tried migrating by performing database dumps between instances, but the schemas appear to differ significantly between versions, which makes this approach unreliable." [abctl migrate discussion]
Regarding CDC and full loads: One knowledge source explicitly states that even with CDC, a full refresh sync is required the first time Airbyte connects. [CDC forum post] Recommendation The knowledge sources do not provide enough information to confidently confirm that restoring a backup will allow you to skip a full CDC reload when downgrading versions. Given the schema differences between versions, this approach carries significant risk. I'd recommend reaching out to the Airbyte community or support for guidance specific to your version downgrade scenario. đ 0 button đ 0 button âšī¸ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.