This topic describes how to migrate an instance across zones in the ApsaraDB for Redis console. For example, if the current zone has insufficient resources to upgrade instances or you want to improve the disaster recovery feature, you can migrate an instance to another zone.
ApsaraDB for Redis instances provide only the classic network endpoints or the internal endpoints that apply to virtual private clouds (VPCs).
|Classic network endpoints that are reserved when the network type is changed to VPC.||Release classic network endpoints|
|Public endpoints||Release public endpoints|
|Private endpoints||Release a private endpoint|
- When you migrate an instance across zones, the instance may be disconnected for a few seconds. Make sure that your application is configured to reconnect to the instance after the instance is disconnected.
- The amount of time that is consumed in a migration depends on multiple factors, such as the network conditions, task queue status, and data volume. We recommend that you migrate the instance across zones during off-peak hours.
- If you migrate your 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 through the endpoint. If you use a VIP to connect to the ApsaraDB for Redis instance, the connection fails.
- If the instance is deployed in a VPC, you cannot change the VPC when you migrate the instance across zones.
Supported migration types and scenarios
|Migrate instances from one single zone to another single zone||The ApsaraDB for Redis instance is migrated to the zone where an Elastic Compute Service (ECS) instance resides. Then the ECS instance can connect to the ApsaraDB for Redis instance over the internal network with lower network latency.|
|Switch from the single-zone deployment to the multi-zone deployment||You want to achieve disaster recovery across data centers for the ApsaraDB for Redis
An instance that is deployed in a single zone can tolerate server-level and rack-related faults. An instance that is deployed across multiple zones can tolerate data center-related faults.
|Switch from the multi-zone deployment to the single-zone deployment||Applications with specific requirements.|
- Log on to the ApsaraDB for Redis console.
- On the top of the page, select the region where the instance is deployed.
- On the Instances page, click the Instance ID of the instance.
- In the Basic Information section, click Cross-zone Migration.
- In the dialog box that appears, configure the settings of the destination zone.
- Select the destination zone.
- Select the destination vSwitch.
- Specify the migration time and select the check box of the message.Note
- 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 executes tasks to prepare the migration and changes the instance to the Migrating to Another Zone state. The instance will not be migrated to another zone until the maintenance window. For more information about how to modify the maintenance window, see .
- Click OK.
Related API operations
MigrateToOtherZone: migrates an ApsaraDB for Redis instance to another zone in the same region.