If you restore data from a backup set to a source ApsaraDB for Redis instance, the data in the source instance is overwritten and cannot be restored. As a result, data loss may occur. ApsaraDB for Redis allows you to create an instance from a specified backup set. The data in the new instance is the same as that in the backup set. This feature can be applied in scenarios such as data recovery, quick workload deployment, and data verification.


When you perform the operations described in this topic, an ApsaraDB for Redis instance is created, and you are charged for the ApsaraDB for Redis instance. For more information, see Billable items and prices.


  1. 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.
  2. In the left-side navigation pane, click Backup and Recovery.
  3. Restore backup sets.
    • Standard master-replica instances: Find the backup set that you want to manage and click Recovery in the Action column.
      Figure 1. Restore a standard instance
      Restore an instance
    • Cluster master-replica instances and read/write splitting instances: Select all the backup sets of a specific point in time and click Recovery.
    Note You can also filter backup sets by time range.
  4. In the message that appears, read the content and click OK.
  5. On the Clone Instance page, configure the parameters described in the following table.
    Parameter Description
    Source Type Set the value to Backup Set.
    Clone Backup Set Select the backup set that you want to manage from the drop-down list.
    Region The region where the source ApsaraDB for Redis instance is deployed is automatically selected and cannot be changed.
    Zone The zone in which you want to create the instance. Each region has multiple isolated locations known as zones. Each zone has its own independent power supply and network. To minimize the network latency between an Elastic Compute Service (ECS) instance and an ApsaraDB for Redis instance that are deployed in the same zone, connect them over an internal network.
    Note To implement zone-disaster recovery, you can deploy the ApsaraDB for Redis instance across multiple zones in the same region.
    Network Type
    • VPC (recommended): A virtual private cloud (VPC) is an isolated network with higher security and better performance than the classic network. We recommend that you select the VPC network type.
    • Classic Network: Cloud services in the classic network are not isolated. Unauthorized access to a cloud service is blocked only by using security groups or whitelists.
    • The ApsaraDB for Redis instance must be of the same network type as the ECS instance that you want to connect. Otherwise, these instances cannot communicate over an internal network.
    • If the network type for both the ECS instance and the ApsaraDB for Redis instance is VPC, these instances must be deployed in the same VPC. Otherwise, they cannot communicate with each other over the internal network.
    • You can switch the network type of an ApsaraDB for Redis instance from the classic network to VPC. However, you cannot switch the network type of an ApsaraDB for Redis instance from VPC to classic network. For more information, see Change the network type from classic network to VPC.
    VPC The VPC in which you want to create the instance. If you do not have a VPC, create one first. For more information, see Create and manage a VPC.
    VSwitch The vSwitch that you want to connect to the instance in the VPC. If no vSwitches are available in the VPC in the current zone, create a vSwitch. For more information, see Work with vSwitches.
    • Community Edition: This edition is compatible with the Redis protocol and provides database solutions that use both memory and disks.
    • Enhanced Edition (Tair): This edition is developed based on the ApsaraDB for Redis Community Edition and is optimized in performance, storage, and data structures. For more information, see Overview.
    Series Performance-enhanced: uses a multi-threading model. This parameter is available only if Edition is set to Enhanced Edition (Tair). The performance of this series type is three times that of a Community Edition instance of the same specifications. This series type also provides multiple data structure modules to simplify development. For more information, see Performance-enhanced instances.
    Version The major version of the ApsaraDB for Redis database engine.
    Note The instances that run Redis 2.8 will soon be phased out. We recommend that you create an instance that uses the latest engine version for more features and more stable performance.
    Architecture Type
    • Cluster: eliminates the performance bottleneck that is caused by the single-threading model. You can use the high-performance cluster instance to process large-capacity workloads.
    • Standard: runs in a master-replica architecture, provides high-performance caching services, and ensures high data reliability.
    • Read/Write Splitting: ensures high availability (HA) and high performance and supports multiple specifications. The read/write splitting architecture allows a large number of concurrent reads of hot data from read replicas. This reduces the loads on the master node and minimizes O&M costs.
    For more information, see Overview.
    Shards The number of data shards for the cluster instance. Data is distributed across the data shards in the cluster instance.
    Note This parameter is available only if the Architecture Type parameter is set to Cluster.
    Node Type
    • If you set the Architecture Type parameter to Cluster or Standard, you must set the Node Type parameter to Master-Replica. This creates a dual-node hot-standby architecture that provides HA.
    • If you set the Architecture Type parameter to Read-Write Splitting, you can select the node type based on the number of read replicas.
    Instance Class Each instance type contains a group of specifications. An instance type includes the memory capacity, maximum number of concurrent connections, and maximum bandwidth items. For more information, see Overview.
    Note Database metadata is generated when an ApsaraDB for Redis instance is created. The size of the metadata on each shard of a cluster instance ranges from 30 MB to 50 MB. The total size of the metadata for a cluster instance equals the total size of metadata on all shards of the cluster instance.
    Set Password
    • Later: Set a password after the instance is created. For more information, see Change or reset the password.
    • Now: Specify a password for the instance.
      • The password must be 8 to 32 characters in length.
      • The password must contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters.
      • Special characters include ! @ # $ % ^ & * ( ) _ + - =
    Instance Name The name of the instance, which is used to identify and manage the instance.
    Duration The subscription duration for the instance. You can select one to nine months for a monthly subscription or select one to three years for an annual subscription.
    Note This parameter is available only to subscription instances.
  6. Read and select ApsaraDB for Redis (Subscription) Agreement of Service.
  7. Click Buy Now.
    After the payment is complete, wait for 1 to 5 minutes. Then, you can find the new ApsaraDB for Redis instance in the ApsaraDB for Redis console.

What to do next

After the new instance is created, you can connect to the new instance to verify data. If the instance passes the verification, you can use the new instance to restore your workloads. If you no longer need the source instance, you can release the instance to save resources. For more information, see Release instances.

Related API operations

Operation Description
CreateInstance Creates an instance and restores data from a specified backup set to the instance.