Cluster Recycle stores released ApsaraDB PolarDB MySQL-compatible edition clusters. You can restore a cluster that was released to Cluster Recycle accidentally.

Procedure

  1. In the left-side navigation pane in the PolarDB console, click Cluster Recycle.
  2. Find the cluster that you want to restore, and click Restore to New Cluster in the Actions column.
    Restore data to a new cluster
  3. Select Subscription or Pay-As-You-Go in the Product Type section.
    • Subscription: Pay for the compute nodes when you create the cluster. You are charged by hour for the storage space that is occupied by the actual amount of data. The charges are deducted from your account balance on an hourly basis.
    • Pay-As-You-Go: An upfront payment is not required. You are charged by hour for the compute nodes and the storage space that is consumed by the actual amount of data. The charges are deducted from your account balance on an hourly basis.
  4. Configure the following parameters.
    Parameter Description
    Region The region where the cluster resides. You cannot change the region after the cluster is created.
    Note Make sure that the PolarDB cluster and the ECS instance you want to connect to the cluster are deployed in the same region. Otherwise, the cluster and the ECS instance cannot communicate over the internal network, which results in decreased performance.
    Create Type Select Recover from Recycle to restore the released cluster from Cluster Recycle.
    Source Version Select the version of the released cluster.
    Deleted Clusters Select the ID of the released cluster.
    Backup History Select the backup set to restore.
    Note The Backup History drop-down list displays the timestamps of backup sets in UTC. However, the Backups displays timestamps of backup sets in the same time zone as the system time. Make sure that you choose the correct backup set.

    For example, the timestamp of a backup set in the Backup History is 2020-05-08T02:00:00Z. The corresponding timestamp in the backup list is 10:00:00 on May 8, 2020 (UTC+08:00).

    Primary Availability Zone The primary zone where the cluster is deployed.
    • A zone is an independent geographical location that resides in a region. All of the zones in a region provide the same services.
    • You can deploy your PolarDB cluster and ECS instance in the same zone or in different zones.
    • You need to specify only the primary zone. The system automatically selects a secondary zone.
    Network Type This parameter can only be set to VPC.
    VPC

    VSwitch

    Make sure that the PolarDB cluster and the ECS instance you want to connect to the cluster are deployed in the same VPC. Otherwise, the cluster and the ECS instance cannot communicate over the internal network, which results in decreased performance.
    • If you have created a VPC that meets your network plan, select the VPC. For example, if you have created an ECS instance and the VPC where the ECS instance resides meets your network plan, select this VPC.
    • If you do not create a VPC that meets your network plan, use the default VPC and the default vSwitch.
      • Default VPC:
        • The default VPC is a unique VPC in the selected region.
        • The subnet mask consists of 16 bits, such as 172.168.0.0/16. A maximum of 65,536 private IP addresses can be provided.
        • The default VPC is not included in the VPC quota that Alibaba Cloud assigns to you.
      • Default vSwitch:
        • The default vSwitch is a unique vSwitch in your selected zone.
        • The subnet mask consists of 20 bits, such as 172.168.0.0/20. A maximum of 4,096 private IP addresses can be provided.
        • The default vSwitch is not included in the quota of vSwitches that you can create in a VPC.
    • If the default VPC and vSwitch cannot meet your requirements, you can create your own VPC and vSwitch. For more information, see Create a VPC.
    Compatibility By default, the database engine version of the PolarDB cluster is the same as that of the released cluster. You do not need to change this parameter value.
    Edition This parameter can only be set to Cluster (2-16 Nodes) (Recommended).
    Node Specification Select a specification based on your requirements. We recommend that you select a specification that is the same or higher than the node specification of the released cluster. For more information about PolarDB node specifications, see Specifications of compute nodes .
    Nodes You do not need to change this parameter value. By default, the system creates two nodes that have the same specification: a primary node and a read-only node.
    Note If the primary node becomes unavailable, the system uses the read-only node as the primary node and creates another read-only node. For more information, see Architecture .
    Storage Cost You do not need to change this parameter value. You are charged on an hourly basis based on the actual storage that you use. For more information, see Storage pricing .
    Note You do not need to specify a storage capacity when you create a cluster. The system automatically scales up or down the storage capacity when the amount of data is increased or decreased.
    Time Zone The time zone of the cluster. The default value is UTC+08:00.
    Table Name Case Sensitivity Specifies whether table names of the cluster are case-sensitive. The default value is Not Case-sensitive (Default). If the databases in your instance have case-sensitive names, select Case-sensitive. This ensures that the data can be migrated successfully.
    Note This parameter value cannot be changed after the cluster is created. Proceed with caution.
    Release Cluster Specifies the backup retention policy that is used when the cluster is deleted or released. You can select one of the following three policies:
    • Retain Last Automatic Backup (Automatic Backup before Release) (Default): retains the last backup set when you release the cluster.
    • Retain All Backups: retains all the backup sets when you release the cluster.
    • Delete All Backups (Cannot be restored): deletes all backups when you delete the cluster.
    Note If you retain backup sets after you delete or release the cluster, you may be billed for storage costs. You can delete the backup sets to reduce costs. For more information, see Release a cluster.
    Cluster Name The name of the cluster. The name must meet the following requirements:
    • It cannot start with http:// or https://.
    • It must be 2 to 256 characters in length.

    If you do not specify this parameter, the system automatically generates a cluster name. You can change the name after the cluster is created.

    Resource Group Select a resource group that you want to manage. For more information about how to create resource groups, see Create a resource group.
    Note A resource group is a container that contains a group of resources in an Alibaba Cloud account. You can manage these resources in a centralized manner. A resource can belong to only one resource group. For more information, see Use RAM to create and authorize resource groups.
  5. Specify Purchase Plan and Number, and click Buy Now on the right. The Purchase Plan parameter is required only if you purchase a subscription cluster.
  6. On the Confirm Order page, confirm your order information. Read and accept the terms of service, and then click Buy Now.
  7. On the Purchase page, confirm the information of the unpaid order and the payment method and click Purchase.
    Note The amount of time required to restore data to a new cluster depends on the size of the backup set. It takes more time for the system to restore data from a larger backup set.