@kapa.ai how can I recover connections from a previous Airbyte-DB connection?

Recovering Connections from a Previous Airbyte Database Recovering connections from a previous Airbyte database involves restoring the Airbyte database backup to a new or existing instance. The approach depends on your deployment type: ------------------------- Docker Deployment 1. Stop all services on the new instance:

docker-compose down

2. Start only the database:

docker-compose up -d db

3. Drop and recreate the database:

docker exec airbyte-db psql -U docker -c 'drop database airbyte';
   docker exec airbyte-db psql -U docker -c 'create database airbyte with owner docker;'

4. Restore from your SQL backup:

cat airbyte_backup.sql | docker exec -i airbyte-db psql -U docker -d airbyte

5. Restart Airbyte:

docker-compose up -d

6. Re-trigger connections — you'll need to trigger all connections again to recreate the Temporal workflows for them. This can be done via the Airbyte API. [Docker migration guide] > Note: Both the source and target instances should be running the same Airbyte version for this to work reliably. [Docker migration guide] ------------------------- Kubernetes Deployment (Helm Chart V2) 1. Copy the SQL backup into the database pod:

kubectl 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"

[Kubernetes restore guide] ------------------------- Important Caveats • Deleted connections cannot be recovered through the UI — deleting a connection is irreversible from the UI perspective. [connection management docs] • If you only need to recover active connections, restoring the full database backup is the most reliable method. • If you don't have a database backup, you would need to manually recreate the connections in the Airbyte UI or via the API. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

cant i check history of previous syncs and check which boards were targeted? @kapa.ai

Yes, you can review the history of previous syncs in Airbyte through a couple of methods: 1. Connection Timeline (UI) Navigate to the Connection Timeline in the Airbyte UI: 1. Click Connections 2. Click the connection you want to inspect 3. Click Timeline The timeline shows historical information including syncs, refreshes, clears, schema changes, and connection settings changes. You can use filters to narrow down by event type and time period. [Connection timeline] 2. Job History & Logs (UI) You can also navigate to a connection's Job History tab to see the latest syncs. From there, you can: • View logs — click the three grey dots next to a sync and select

View logs

• Download logs — for a full local copy, including logs across multiple attempts [Browsing logs] 3. Audit Logging (Self-Managed Enterprise only) If you're on Self-Managed Enterprise, audit logging captures create, update, and delete operations on connections, sources, destinations, and more. These logs are stored as JSON files in a blob storage bucket you configure. [Audit logging] ------------------------- However, the knowledge sources do not explicitly mention whether sync logs include details about specific "boards" (e.g., from a source like Trello or Jira) that were targeted in a sync. The logs primarily cover the sync operations themselves. To see which specific streams/objects were configured, you'd need to check the connection's stream configuration in the UI or review the detailed sync logs. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.