Migrating a Data Transfer transfer and endpoints to a different availability zone
You can migrate transfers from one availability zone to another. The migration method depends on which service is used as the transfer endpoint: a custom DB installation or a Yandex Cloud managed DB. If migrating data between a custom installation and a managed DB, you should first move the endpoint based on a custom installation and then the one based on a managed DB.
Moving an endpoint based on a custom installation
-
If the transfer type is Replication or Snapshot and increment, deactivate the transfer and wait for its status to change to Stopped.
-
Create a subnet in the availability zone you want to move your endpoint to.
-
If your custom installation is hosted on a Yandex Cloud VM, follow these steps:
-
Specify a new subnet in the settings of the endpoint with your custom installation.
-
If you deactivated the transfer earlier, activate it and wait for its status to change to Replicating.
Warning
If your transfer includes an endpoint based on a managed DB, migrate this endpoint to a different availability zone before activating the transfer.
Moving an endpoint based on a managed DB
-
Move your cluster hosts to a different availability zone. For more information, see the documentation for the following services:
-
If the transfer type is Replication or Snapshot and increment, restart the transfer for it to get the information about the new cluster topology. You do not need to restart Snapshot transfers, as information about the new topology is provided automatically while activating them.
To restart a transfer, choose one of the two methods:
- Deactivate the transfer and wait for its status to change to Stopped. Next, reactivate the transfer and wait for its status to change to Replicating.
- Update any setting for the transfer or endpoint.
ClickHouse® is a registered trademark of ClickHouse, Inc.