| Clone Source Type |
Select Backup Set. |
| Region |
By default, the region of the new cluster is the same as that of the original cluster. This setting cannot be changed. |
| Clone Source Backup Set |
Select the backup set from which you want to restore data.
Note The
Start Time of each backup set is displayed. You can determine whether to select the backup set based on this backup time.
|
| Primary Availability Zone |
Select the primary zone where the cluster is deployed.
Note In regions that have two or more zones,
PolarDB automatically replicates data to the secondary zone for disaster recovery.
|
| Network Type |
This parameter can only be set to VPC. |
| VPC |
Select a VPC and a VSwitch for the cluster. We recommend that you use the same VPC and VSwitch that are used for the original cluster.
Note 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.
|
| VSwitch |
| Compatibility |
By default, the new cluster has the same compatibility as that of the original cluster. For example, if the compatibility of the original cluster is MySQL 8.0 (fully compatible with MySQL 8.0), the compatibility of the new cluster is also MySQL 8.0. |
| Specification Type |
ApsaraDB PolarDB MySQL-compatible edition Cluster Edition has the following two types of specifications: General Specification and Dedicated Specification.
- Dedicated: The 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 two types of specifications, see Comparison between general-purpose compute nodes and dedicated compute nodes.
Note This parameter is available only when the
edition of the original cluster is
Cluster (2-16 Nodes) (Recommended).
|
| Node Specification |
Select a node specification. The maximum storage capacity and performance of clusters vary based on node specifications. For more information, see Specifications of compute nodes.
Note We recommend that you select a
node specification that is the same or higher than the node specification of the original cluster. This ensures that the new cluster runs as expected.
|
| Nodes |
- The default number of nodes of the Cluster (2-16 Nodes) (Recommended) edition is 2. You do not need to change this parameter value.
Note By default, a new cluster of
Cluster Edition contains one primary node and one read-only node. After a cluster is created, you can add nodes to the cluster. A cluster can contain one primary node and up to 15 read-only nodes. For more information about how to add nodes, see
Add or remove read-only nodes.
- The default number of nodes of the Single Node (Starter) and Archive Database (High Compression Ratio) editions is 1. You do not need to change this parameter value.
|
| Storage Cost |
You do not need to select the storage capacity when you purchase PolarDB clusters. You are charged for the storage capacity used on an hourly basis. You can also purchase a storage plan based on your business requirements. For more information about how to purchase a storage plan, see Purchase a storage plan. |
| 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. |
| Purchase Plan |
Specify Purchase Plan for the cluster.
Note This parameter is available only when the
Billing Method parameter is set to
Subscription.
|
| Number |
Select the number of clusters you want to purchase. |
