Cloning Instance
Unduh
Mode fokus
Ukuran font
TDSQL Boundless supports the instance cloning feature. Users can restore an instance to any point in time within the log backup retention period or to a specified backup set by cloning. The cloning operation creates a new instance based on the backup data, according to the point in time or backup set selected by the user. After the new instance is verified, users can migrate data back to the source instance via DTS or directly use the cloned new instance.
Cloning Methods
TDSQL Boundless supports the following two cloning and recovery methods:
By time point: Restores an instance to any point in time. The selectable range of time points is determined by the log retention duration.
By backup set: Restores an instance to a specified backup set. The selectable range of backup sets is determined by the data backup retention duration. Users can select a backup set from existing physical backups or snapshot backups for recovery.
Costs for New Instances
The billing mode for the new cloned instance supports selecting pay-as-you-go on the cloning page. For detailed billing information, see Billing Overview.
Billing for the new cloned instance starts only after the cloning process is fully completed.
Prerequisites
The source instance must be in the Running state.
If you select By backup set as the cloning method, the source instance must have completed physical backups or snapshot backups. You can view the backup status in the Data Backup List on the TDSQL Boundless console.
The account balance must be greater than 0.
Limitations
The specification of the new cloned instance must be greater than or equal to that of the source instance.
The total disk capacity of the new cloned instance must be greater than the size of the data to be cloned; otherwise, the cloning operation fails.
When cloning is performed via snapshot backup, the number of nodes and disk capacity of the new instance must not be less than the corresponding values of the source instance.
The database version, SQL Mode, and parameter template of the new cloned instance are automatically inherited from the source instance's configuration, so users do not need to configure them manually.
During the cloning process, the new instance is not displayed in the console instance list and becomes visible only after the cloning is successful.
During the cloning process, operations such as restarting, migrating, or upgrading the version cannot be performed on the source instance. It is recommended to perform these operations after the cloning is completed.
Deploy the cloned instance in the same VPC and subnet as the source instance to reduce network latency and configuration complexity.
Cloning is not supported between instances with different replica configurations. The number of log replicas in the new cloned instance must match that of the source instance (for example, a 2+1 replica instance can only be cloned as a 2+1 replica instance).
Steps
Step 1: Going to the Clone Instance Page
1. Log in to the TDSQL Boundless console. In the Instance List, click the Instance ID to go to the Instance Details page.
2. Navigate to the Backup and Restoration > Cloned Instance List tab and click Create Clone Instance.
Step 2: Select Basic Configuration
Clone Recovery Settings
Parameter | Description |
Clone Recovery Method | Select a clone recovery method: By time point: Restores to any point in time within the log backup retention period. By backup set: Restores to the backup set of a specified physical backup or snapshot backup. |
Time Point | When By time point is selected, specify the specific time point to restore to. The selectable range is determined by the log backup retention period. |
Backup set | When By backup set is selected, select the backup set to restore to from the list. The backup set originates from the physical backup or snapshot backup of the source instance. |
Basic Configuration
Parameter | Description |
Billing Mode | Currently, only the Pay as You Go billing method is supported. If you need a yearly/monthly subscription, you can switch to the yearly/monthly subscription mode after the instance cloning is completed. Billing for the cloned instance starts only after it is fully successful. |
Region | Consistent with the source instance's region by default and cannot be modified. |
Instance Type | Select the architecture type for the cloned instance. |
Deployment Mode | Users can select the number of AZs to deploy. Single-AZ: All resources reside in the same AZ, offering the lowest network latency. Two AZs: The application runs across two AZs and can withstand a single AZ failure. Three AZs: Resources are distributed across three AZs, enabling service continuity and reduced recovery time in the event of a single AZ failure. |
AZ | Select the AZ for instance deployment. Cloud products in different AZs under the same VPC can communicate via the private network. For example, a CVM in Guangzhou Zone 2 under the same VPC can access TDSQL Boundless in Guangzhou Zone 3 via the private network. |
Peer Node Specification Configuration
Parameter | Description |
Node Type | By default, it is the Enhanced type, which is equipped with a new-generation CPU core, delivers robust computing performance and ample computing resources, possesses exceptional data read/write capabilities, and is specifically designed for large-scale website applications, high-concurrency services, and other performance-sensitive workloads. |
Node Disk Type | Enhanced SSD: A CBS is a highly available, highly reliable, low-cost, and customizable block storage device. It provides block-level data storage, employs a distributed three-replica mechanism, and ensures data reliability for the distributed database TDSQL Boundless. Local SSD: A local disk is an NVMe SSD that delivers powerful I/O performance, with IOPS reaching up to 240,000 (the actual IOPS rate depends on configuration, page size, and workload; this value is obtained from tests using the MySQL default 16KB page size and is for reference only). It resides on the same node as the database engine, offers extremely low I/O latency, and provides optimal performance for OLTP workloads. |
Node Disk Capacity | Select the required storage space for each node. Note: When cloning is performed from a local disk instance, the total disk capacity of the target instance must be greater than "backup file size × number of replicas"; otherwise, the cloning operation fails. When cloning is performed from a cloud disk instance, the disk capacity of each node in the target instance must be greater than or equal to the disk capacity of the corresponding node in the source instance; otherwise, the cloning operation fails. |
Number of Nodes | Select the required number of peer nodes. Note: When cloning is initiated from a cloud disk instance, the number of nodes and the disk capacity of the target instance must not be lower than the corresponding values of the source instance; otherwise, the cloning operation will fail. |
Step 3: Set Network and Database
Network and Other Settings
Configuration Item | Description |
Network | Select the VPC and subnet for the new instance. It is recommended to select the same network environment as the source instance to reduce network latency. |
Custom Port | The access port for the database. The default port is 3306. Valid range: 1024 - 65535. |
Tag | Adds Tags to the instance for categorizing and managing instance resources. |
Database Settings
Configuration Item | Description |
Instance Name | Name It Later: Set the instance name after the instance is created. Name It Now: Set the instance name directly during creation. |
Step 4: Confirm Configuration Information
1. Verify all configuration information, carefully read the Terms of Service at the bottom of the page, select I have read and agree to the Terms of Service, and click Buy Now.
2. After the purchase is successful, you can view the cloning progress and results in the following ways:
View the cloning details and progress on the Backup and Restoration > Cloned Instance List page of the source instance.
After cloning is successful, view the newly created clone instance on the Instance List page.
Next Steps
After the clone instance is created, you can perform the following operations:
Directly use the clone instance as a new business instance.
Migrate data from the clone instance back to the source instance via DTS. Applicable scenarios are as follows:
Partial Data Recovery: If a user accidentally updates a large amount of data in table A and the logs have been purged, the user can restore the data on the clone instance and then migrate the data back to the source instance via DTS.
Source Instance Failure Recovery: When the source instance is damaged, you can clone it to a new instance. After the source instance recovers, use DTS to migrate the data generated during the recovery period back to the source instance.
FAQs
Does Cloning Affect Access to the Source Instance?
No. The cloning operation uses existing backup data for restoration and does not affect normal access to the source instance. The source instance can continue to provide read and write services normally during the cloning process.
Are Database Parameters of the Clone Instance Consistent with Those of the Source Instance?
Yes. The clone instance automatically inherits the SQL Mode and parameter template configurations from the source instance. Users do not need to manually configure database parameters.
What Are Common Causes of Clone Failures?
Common causes include:
The total disk capacity of the new instance is insufficient (it must be greater than the backup file size multiplied by the number of replicas).
In snapshot cloning scenarios, the number of nodes or disk capacity is lower than that of the source instance.
Cloning between 2+1 replica and 3 replica instances is not supported (due to inconsistent log replica counts).
The source instance is in an abnormal or unavailable state.
The account has insufficient balance or is in arrears.
When Does Billing Start for a Clone Instance?
Billing for the clone instance starts only after the cloning process is fully completed. No charges are incurred during the cloning process. The billing start time is determined by the time when the cloning succeeds.
How Is the Available Time Range Determined for Point-in-Time Cloning?
The selectable time range is determined by the log backup retention period (7 days by default).
Is the Backup Policy of the Clone Instance Consistent with That of the Source Instance?
The backup policy for the clone instance is not automatically inherited from the source instance's configuration. After the cloning succeeds, users need to configure a backup policy separately for the clone instance.
Does the Clone Instance Support Specification Change?
Yes. After the clone instance is successfully created, you can modify its specifications based on business requirements, such as scaling out nodes or expanding disk capacity.
Is There a Limit on the Number of Clone Operations?
There is no limit on the number of times. Users can clone the same source instance multiple times as needed.
Bantuan dan Dukungan
Apakah halaman ini membantu?
Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.
masukan