All Products
Search
Document Center

PolarDB:Restore a cluster from Cluster Recycle

Last Updated:Jul 26, 2023

Cluster Recycle stores released PolarDB for MySQL 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.

  3. Select Subscription or Pay-As-You-Go for Product Type parameter.

    • Subscription: When you create a cluster, you must pay for the compute nodes. You are charged for the use of storage resources and the fees are deducted from your account balance on an hourly basis.
    • Pay-as-you-go: An upfront payment is not required. You are charged for the compute nodes and the amount of storage that is consumed by your data. The fees are deducted from your account balance on an hourly basis.
  4. Set the basic settings parameters.

    Parameter

    Description

    Region

    The region of the cluster. After the cluster is created, the region cannot be changed.

    Note

    Make sure that the PolarDB for MySQL cluster and the ECS instance to which you want to connect are deployed in the same region. Otherwise, the PolarDB cluster and the ECS instance can communicate only over the Internet, which results in decreased cluster performance.

    Creation Method

    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

    The backup set.

    Note

    The Backup History drop-down list displays the timestamps of backup sets in UTC. However, the Data 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).

    Database Engine

    By default, the database engine version of the PolarDB for MySQL cluster is the same as that of the released cluster. You do not need to change this parameter value.

    Product Version

    By default, the version of the PolarDB for MySQL cluster is the same as that of the released cluster. You do not need to change this parameter value.

    Edition

    Only Cluster Edition (Recommended) is supported. You do not need to change this parameter value.

    Nodes

    By default, the cluster consists of one primary node and one read-only node. You can select two nodes (one primary node and one read-only node) or one node (primary node).

    Primary Zone

    The primary zone in which the cluster is deployed.

    • A zone is an independent geographical location in a region. All of the zones in a region provide the same level of service performance.

    • You can choose to create your PolarDB for MySQL cluster in the same zone as an ECS instance or in a different zone from the zone of the instance.

    • You need to specify only the primary zone. The system automatically selects a secondary zone.

    Specification Type

    PolarDB for MySQL supports General-purpose and Dedicated.

    • Dedicated: Computing resources such as CPUs that are allocated to each cluster are exclusive to the cluster. This improves the stability and reliability.

    • General-purpose: Idle computing resources such as CPUs are shared among clusters on the same server for cost-effectiveness.

    For more information about the comparison between the types of specifications, see Comparison between general-purpose and dedicated compute nodes.

    Filter

    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 for MySQL node specifications, see Specifications of compute nodes.

    PolarProxy Type

    PolarDB for MySQL supports Standard Enterprise Edition and Dedicated Enterprise Edition.

    • Standard Enterprise Edition: If your cluster is General-purpose, you can select this database proxy type, which shares CPU resources with smart elastic scaling within seconds provided based on business loads.

    • Dedicated Enterprise Edition: If your cluster is Dedicated, you can select this database proxy type, which occupies all allocated CPU resources and provides better stability.

    Storage type

    PolarDB for MySQL supports the PSL5 and PSL4 storage types.

    • PSL5: the storage type supported by historical versions of PolarDB. This was the default storage type for PolarDB clusters purchased before June 7, 2022. It delivers higher performance, reliability, and availability.

    • PSL4: a new storage type for PolarDB for MySQL. Standard Edition uses the Smart-SSD technology developed in-house by Alibaba Cloud to compress and decompress data at the SSD disk level. This storage type can minimize the storage costs of data while maintaining a high disk performance. This storage type is also called PSL4.

      Note

      The storage type of existing clusters cannot be changed to Standard Edition. To use Standard Edition, we recommend that you purchase a new cluster, set the storage type to Standard Edition, and then migrate data to the new cluster.

    For more information about the two storage types, see Comparison between PSL4 and PSL5.

    Storage Billing Method

    PolarDB for MySQL supports the Pay-as-you-go and Subscription billing methods for the storage of your clusters.

    • Pay-as-you-go: The storage capacity is provided based on a serverless architecture. This way, you do not need to specify the storage capacity when you purchase clusters. The storage capacity of the clusters can be automatically scaled up as the volume of data increases. You are charged for the actual data volume. For more information, see Pay-as-you-go.

    • Subscription: You must purchase a specific amount of storage capacity when you create the cluster. For more information, see Subscription.

    Note

    When Product Type is set to Subscription, the Storage Billing Method parameter can be set to Pay-as-you-go or Subscription. When Product Type is set to Pay-as-you-go, the Storage Billing Method parameter is unavailable, and the storage is billed on a pay-as-you-go basis.

    Capacity

    The amount of storage capacity that you want to purchase for your cluster. The value can range from 50 GB to 100 TB, in 5 GB increments.

    Note

    This parameter is available only when Storage Billing Method is set to Subscription.

    Storage Cost

    The storage cost. You do not need to change this parameter value. You are charged for the amount of storage that is consumed by your data on an hourly basis. For more information, see Pay-as-you-go.

    Note
    • You do not need to specify the storage capacity when you create a cluster. The system scales the storage capacity when the amount of data is increased or decreased.

    • This parameter is available only when Storage Billing Method is set to Pay-as-you-go.

  5. Click Next: Cluster Configurations and configure the following parameters.

    Parameter

    Description

    Cluster Name

    You can select Auto-generate or Custom cluster name. If you select Auto-generate, the system automatically generates a cluster name after the cluster is created. You can modify the automatically generated cluster name. If you select Custom, you must enter a cluster name. The name must meet the following requirements:

    • It cannot start with http:// or https://.

    • It must be 2 to 256 characters in length.

    • It must start with a letter and can contain letters, digits, periods (.), underscores (_), and hyphens (-).

    Resource Group

    Select a resource group from the available resource groups. For more information about how to create resource groups, see Create a resource group.

    Note

    A resource group is a group of resources that belong to an Alibaba Cloud account. Resource groups allow you to manage these resources in a centralized manner. A resource belongs to only one resource group. For more information, see Use RAM to create and authorize resource groups.

    Network Type

    This parameter is automatically set to VPC. You do not need to change this value.

    VPC

    vSwitch

    Make sure that the PolarDB for MySQL cluster and the ECS instance to which you want to connect are deployed in the same VPC. Otherwise, the cluster and the ECS instance cannot communicate over a VPC, which degrades cluster performance.

    • If an existing VPC meets your network requirements, select the VPC. For example, if you have created an ECS instance and the VPC to which the ECS instance is connected meets your network requirements, select this VPC.
    • Otherwise, use the default VPC and the default vSwitch.
      • Default VPC:
        • Only one VPC is specified as the default VPC in the region that you select.
        • The CIDR block of the default VPC uses a 16-bit subnet mask. For example, the CIDR block of the default VPC can be 192.168.0.0/16. This CIDR block provides up to 65,536 private IP addresses.
        • The default VPC does not count towards the quota of VPCs that you can create on Alibaba Cloud.
      • Default vSwitch:
        • Only one vSwitch is specified as the default vSwitch in the zone that you select.
        • The CIDR block of the default vSwitch uses a 20-bit subnet mask. For example, the CIDR block of the default vSwitch can be 192.168.0.0/20. This CIDR block provides up to 4,096 private IP addresses.
        • The default vSwitch does not count towards the quota of vSwitches that you can create in a VPC.
    • If the default VPC and vSwitch cannot meet your business requirements, you can create your own VPC and vSwitch. For more information, see Create and manage a VPC.

    Parameter Template

    Select a custom or default system parameter template.

    Note
    • Only parameter templates of PolarDB for MySQL 8.0 are supported.

    • In the parameter template drop-down list, all custom or default system parameter templates available in the current region are displayed. For more information about parameter templates, see Apply a parameter template.

    Time Zone

    The time zone of the cluster. The default value is UTC+08:00.

    Table Name Case Sensitivity

    Specifies whether table names in the cluster are case-sensitive. The default value is Not Case-sensitive (Default). If table names in your on-premises database are case-sensitive, select Case-sensitive. This simplifies the process of data migration.

    Note

    After the cluster is created, you cannot change the value of this parameter. We recommend that you configure this parameter based on your business requirements.

    Release Cluster

    The backup retention policy that is used when the cluster is deleted or released. Default value: Retain Last Automatic Backup (Automatic Backup before Release) (Default). Valid values:

    • Retain Last Automatic Backup (Automatic Backup before Release) (Default): The system retains the last backup when you release the cluster.

    • Retain All Backups: The system retains all backups when you release the cluster.

    • Delete All Backups (Cannot be restored): The system retains no backups when you release the cluster.

    Note

    You may be charged for the backups that are retained after you delete or release a cluster. For more information, see Release a cluster.

  6. Click Next: Confirm Order. In the dialog box that appears, set Purchase Duration and Purchase Quantity.

  7. Confirm your order information, read and accept the terms of service, and then click Buy Now.

  8. On the Purchase page, confirm the 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.