You can migrate an ApsaraDB MyBase instance to another host.
Prerequisites
An ApsaraDB MyBase for MySQL, ApsaraDB MyBase for SQL Server, or ApsaraDB MyBase for
PostgreSQL instance is created. For information about how to create an ApsaraDB MyBase
instance, see the following topics:
Precautions
- After you migrate an instance, the instance remains disconnected for approximately 30 seconds.
- ApsaraDB MyBase for MySQL Master-replica Edition instances and ApsaraDB MyBase for SQL Server instances cannot be migrated to hosts across different zones. Instances of other editions can be migrated to hosts in the same zone and across different zones.
- After you migrate an instance to a host that is not deployed in the same zone, the
following risks may occur:
- The virtual IP address (VIP) of the instance changes after the instance is migrated. We recommend that you use the endpoint of the instance instead of the IP address of the instance to connect your application to the instance.
- If the cache of your client is full and you do not clear the cache, data cannot be written to the cache.
- If a Data Transmission Service (DTS) task is running on the instance, restart the DTS task after you migrate the instance.