If the current zone in which your instance is deployed has insufficient resources for a specification upgrade or if you want to improve the disaster recovery capability, you can migrate the instance to another zone.
The amount of time that is required for the migration varies with factors such as the network conditions, task queue state, and data volume. We recommend that you migrate the instance during off-peak hours.
When you migrate an instance across zones, the Domain Name System (DNS) mapping of the instance may change. In this case, make sure that you use the endpoints of the instance such as
r-bp10b3fa3500****.redis.rds.aliyuncs.comto connect to the instance. In addition, Jedis of earlier versions may not be able to obtain valid endpoints of the instance. You must update your Jedis client. For more information, see Notice on Jedis update.
If an instance is deployed in a virtual private cloud (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.
Cloud disk-based cluster instances in direct connection mode cannot be migrated across zones.
Supported migration types and scenarios
|Migrate an instance from one zone to another||The ApsaraDB for Redis instance is migrated to a zone where an Elastic Compute Service (ECS) instance is deployed. Then, the ECS instance can connect to the ApsaraDB for Redis instance over an internal network with lower network latency.|
|Migrate an instance from multiple zones to other zones|
|Migrate an instance from one zone to multiple zones||You want to implement disaster recovery across data centers for the ApsaraDB for Redis instance. |
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 specific business needs.|
This operation may cause transient connections. We recommend that you perform this operation during off-peak hours and make sure that your application is configured to automatically reconnect to your instance.
- 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 that you want to manage resides. Then, find the instance and click its ID.
In the Basic Information section, click Cross-zone Migration.
In the panel that appears, configure the parameters described in the following table.
Destination Primary Zone
The primary destination zone to which you want to migrate the instance.
Destination Secondary Zone (optional)
The secondary destination zone to which you want to migrate the instance. If you set this parameter, the replica node of the instance is migrated to this zone. This achieves disaster recovery across zones.
Typically, the master node is deployed in the primary zone and the replica node in the secondary node. If the master node fails, the system fails the workloads over to the replica node. This improves service continuity. However, the failover may cause cross-zone access between the instance and your other business. To resolve this issue, you must manually change the zone.Note
If you do not set this parameter, both the master node and the replica node of the instance are migrated to the primary zone.
The destination vSwitch. If no vSwitch exists in the destination zone, you must create one. For more information, see Create and manage a vSwitch.Note
This parameter is displayed only if the instance is deployed in a VPC.
Update Now: After you click OK, the migration immediately starts. When the instance state changes to Running, the instance is migrated.
Update During Maintenance (recommended): After you click OK, the pre-migration operations immediately start and the instance state changes to Migrating to Another Zone. During this process, the instance remains fully operational. The migration is not performed until the maintenance window starts.
For more information, see Set a maintenance window.
Read and select the check box. Then, click OK.
Related API operations
|MigrateToOtherZone||Migrates an ApsaraDB for Redis instance across zones within the same region.|