I am trying to restore a back up from cluster vers...
# replication-troubleshooting
o
I am trying to restore a back up from cluster version 0.39.38 to the latest version 0.40.29 but I am getting an error
Copy code
curl -H "Content-Type: application/x-gzip" -X POST "<http://airbytenew-api.airbyte.svc/api/v1/deployment/import>" --data-binary @/tmp/airbyte_archive.tar.gz 

Object not found.
👍 1
https://github.com/airbytehq/airbyte/pull/16403
Copy code
The previous PR removed access to import / export in the API to get it out of the hands of users faster. This PR, removes all of the code that supported those features.
Was this implemented to promote the cloud version ?
Some Airbyte version below 0.40.10 is the last version which supports the import API it seems 😞
https://github.com/airbytehq/airbyte/pull/16175 Those features were removed in v0.40.5 however I don’t see any updated documentation in the website https://docs.airbyte.com/operator-guides/upgrading-airbyte/ so we don’t shoot ourselves in the foot 👀 and still be able to test out a version update without doing a blind in-place upgrade and end up with a possibly broken environment
Restoring to 0.40.4 is also not working, i guess that’s why it was removed to get rid of the maintenance overhead Any recommendations appreciated on how to test out an upgrade
m
If you need to move your database to another instance you can follow this instructions https://discuss.airbyte.io/t/how-to-import-export-airbyte-to-a-new-instance-docker-to-docker-deploy/3514/3
o
I am deploying to kubernetes using
Copy code
kubectl apply -k kube/overlays/stable-with-resource-limits
The database is created using a PVC I was basically creating a new deployment on a different namespace and restoring the jobs via (backup/restore) there and making sure that everything still works before deleting the old deployment and update the custom defined ingress We are using it in production with over 100 streams and invoking airbyte jobs from Airflow so it is really critical for us to make sure that everything works as expected before we switch over I did this process 2 times in the past to make sure it works . My question would be is all the the connections / states/ secrets stored in the database ? then i can also trying dumping out the database and restoring to the new database in the new namespace
u
Yes, you can dump the database. Please read the guide.
thanku 1