Hey all. I have a question. I have started a large...
# replication-ask-ai
j
Hey all. I have a question. I have started a large sync on my local machine. Now I want to deploy Airbyte on a VM and have it continue the sync from there. How can I transfer the config so that when I deploy it on a new VM the syncs will continue where they last stopped on my local machine?
k
To transfer your local configurations to your Airbyte instance on a VM, you can use the
octavia apply
command. This command propagates changes in your local configurations to your Airbyte instance. You will be prompted for validation of changes. You can bypass the validation step using the
--force
flag. Here is the command:
Copy code
bash octavia apply
If you want to force apply the changes, use:
Copy code
bash octavia apply --force
Please note that this will only transfer the configurations. The state of the sync (i.e., where it last stopped) might not be transferred. You might need to restart the sync on the new VM. For deploying Airbyte on a VM, you can follow the guide on deploying Airbyte on Azure VM if you are using Microsoft Azure. The instructions have been tested on a standard DS1 v2 (1 vcpu, 3.5 GiB memory) Microsoft Azure VM with Ubuntu 18.04. Please remember to save your configurations before resetting or turning off Airbyte on your local machine. You can use the Octavia CLI to save your configurations. Sources: - [CLI Documentation](https://docs.airbyte.com/cli-documentation) - [Deploy Airbyte on Azure VM Cloud Shell](https://docs.airbyte.com/deploying-airbyte/on-azure-vm-cloud-shell)
j
How do I transfer the current connection state of a connection to a new airbyte deployement?