You can clone a new instance from a backup file in the ApsaraDB for Redis console to quickly deploy applications.

Procedure

  1. Log on to the ApsaraDB for Redis console.
  2. In the top navigation bar, select the region where the target instance is located.
  3. On the Instances page, click the Instance ID of the target instance.
  4. In the left-side navigation pane, click Backup and Recovery.
  5. On the Backup and Recovery page, click the Data Backup tab, select a data source, and complete the following operations based on the instance type:
    • If the ApsaraDB for Redis instance is a standard instance or a read/write splitting instance, click Clone Instance in the Action column.
    • If the ApsaraDB for Redis instance is a cluster instance, select a data source, and click Clone Instance.
      Note You must select a backup data record for each data shard. For example, a cluster contains two data shards: db-0 and db-1. Before you clone the instance, select a backup data record for each data shard, as shown in the following figure. If you select multiple backup data records for a shard, the system uses the latest record for cloning.
      Select backup data records for the cluster shards and click Clone Instance
  6. In the Clone Instance dialog box that appears, click OK.
  7. On the Clone Instance page, configure the following parameters.
    Parameter Description
    Region The region of the instance. The value is the same as that of the source instance. You cannot modify this parameter.
    Clone Source Type Select Clone Instance.
    Network Type
    • Classic Network: a traditional type of network.
    • VPC: the recommended network type. A virtual private cloud (VPC) is an isolated virtual network that provides higher security and better performance than a classic network.
    Notice
    • The ApsaraDB for Redis instance must be of the same network type as the ECS instance to be connected. Otherwise, these instances cannot communicate over an internal network.
    • If both instances use the VPC network type, to enable connections over an internal network, the instances must be connected to the same VPC.
    • You can change the network type of an ApsaraDB for Redis instance from classic network to VPC. However, you cannot change the network type from VPC to classic network. For more information, see Switch to VPC.
    VSwitch A VSwitch is a basic network module of a VPC. If no VSwitch is available in the VPC, create a VSwitch first. For more information, see Create a VSwitch.
    Edition Type
    • Community Edition: This edition is compatible with the open source Redis protocol and provides database solutions that support hybrid storage in memory and disks.
    • Enhanced Edition (Tair): This edition is developed based on ApsaraDB for Redis Community Edition and is optimized in terms of performance, storage, and data schemas. For more information, see Overview.
    Series Type Enhanced Edition provides the following series types:
    Note If you select Community Edition, this parameter is not supported.
    Version ApsaraDB for Redis supports the following engine versions:
    • 2.8
    • 4.0
    • 5.0
    By default, the version is the same as that of the source instance. You cannot modify this parameter.
    Architecture Type
    • Cluster
    • Standard
    For more information, see Overview.
    Shards The number of shards on a cluster instance.
    Note The number of shards can be specified for cluster instances only.
    Node Type

    Standard instances and cluster instances only support the master-replica type. This type provides a master node and a replica node that are deployed in the hot standby mode to support data persistence.

    Instance Class Each instance type contains a group of configurations, such as the memory, maximum number of concurrent connections, and maximum bandwidth. For more information, see Overview.
    Note After you create an instance, database metadata is automatically generated and consumes a small amount of storage space.
    • A standard instance has about 50 MB of metadata.
    • On each shard of an ApsaraDB for Redis cluster instance, the size of metadata is about 50 MB. In a cluster, the total amount of storage space that metadata uses is the total size of metadata on each shard.
    Password Setting Specify a time to set the password.
    • Now: Set the instance password now.
    • Later: Set the password after the instance is created. For more information, see Change the password.
    Instance Name The name of the ApsaraDB for Redis instance. If this parameter is not specified, the instance ID is used as the instance name.
    Duration Set the subscription duration. This option is not displayed if the billing method is pay-as-you-go.
  8. Click ApsaraDB for KVStore Agreement of Service, and read the agreement.
  9. If you accept the service agreement, click the check box before the service agreement.
  10. Click Activate.