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.
Prerequisites
- The instance uses local disks or is a standard instance that uses cloud disks. For more information, see Comparison between ApsaraDB for Redis instances that use local disks and those that use cloud disks.
- The ApsaraDB for Redis instance has a classic network endpoint or a Virtual Private
Cloud (VPC) endpoint, and does not have the following endpoints.
Notice If the instance has the endpoints that are listed in the following table, release the endpoints before you migrate the instance. Otherwise, the Cross-zone Migration button is dimmed and the operation cannot be performed.
Endpoint Method to release 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
Precautions
- 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 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.
- If you migrate an instance across zones, the virtual IP address (VIP) of the instance is changed. Example: 172.16.88.60. 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
Type | Scenario |
---|---|
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. |
Procedure
Related API operations
Operation | Description |
---|---|
MigrateToOtherZone | Migrates an ApsaraDB for Redis instance across zones within the same region. |