If the current zone in which your instance is deployed has insufficient resources for a specification upgrade or you want to improve the disaster recovery capability, you can migrate the instance to another zone.
The ApsaraDB for Redis instance has a classic network endpoint or a virtual private cloud (VPC) endpoint, and does not have the following endpoints:
|Classic network endpoint that is retained when the network type is changed to VPC||Release a classic network endpoint|
|Public endpoint||Release a public endpoint for an ApsaraDB for Redis instance|
|Private endpoint||Release a private endpoint for an ApsaraDB for Redis instance|
- When you migrate an instance across zones, the instance may experience transient connections for a few seconds. Make sure that your application is configured with a reconnection mechanism.
- The time that is required for the migration varies based on factors such as the network conditions, task queue status, and data volume. We recommend that you migrate the instance during off-peak hours.
- If you migrate an instance across zones, the virtual IP address (VIP) of the instance such as 172.16.88.60 is changed. However, the endpoint of the instance remains unchanged. We recommend that you connect to the instance by using the endpoint. If you use a VIP to connect to the instance, the connection fails.
- If an instance is deployed in a VPC, you cannot change the VPC when you migrate the instance across zones.
- To ensure better performance and stability, if the minor version of an instance is outdated, the system updates the minor version of the instance to the latest version during the migration.
Supported migration types and scenarios
|Migrate an instance from one zone to another zone||The ApsaraDB for Redis instance is migrated to the zone where an Elastic Compute Service (ECS) instance is deployed. Then, the ECS instance can connect to the ApsaraDB for Redis instance over the internal network with lower network latency.|
|Migrate an instance from multiple zones to multiple different zones|
|Migrate an instance from one zone to multiple zones||You want to implement disaster recovery across data centers for the ApsaraDB for Redis
An ApsaraDB for Redis instance that is deployed in a single zone can tolerate server- and rack-level faults. An ApsaraDB for Redis instance that is deployed in multiple zones can tolerate data center-level faults.
|Migrate an instance from multiple zones to one zone||You want to migrate the ApsaraDB for Redis instance based on your business requirements.|
- Log on to the ApsaraDB for Redis console and go to the Instances page. In the top navigation bar, select the region in which the instance is deployed. Then, find the instance and click the instance ID.
- In the Basic Information section, click Cross-zone Migration.
- In the panel that appears, set the following parameters.
Parameter Description Destination Primary Zone Select the destination zone. VSwitch Select the destination vSwitch. If no vSwitch exists in the destination zone, you must create one. For more information, see Work with vSwitches.Note This parameter appears only when the instance runs in a VPC. Exec Time
- Update Now: After you click OK, the migration immediately starts. When the instance status changes to Running, the instance is migrated.
- Update During Maintenance: After you click OK, the system immediately performs tasks to prepare for the migration and changes the instance to the Migrating to Another Zone state. The instance will not be migrated to another zone until the specified maintenance window starts. For more information about how to modify the maintenance window, see Set a maintenance window.
- Select the check box for the dialog box and click OK.
Related API operations
|MigrateToOtherZone||Migrates an ApsaraDB for Redis instance across zones in the same region.|