How to Recover Accidentally Deleted Data in TDSQL Boundless?
In TDSQL Boundless, data recovery is primarily achieved through instance cloning. Cloning creates a new, independent instance based on the backup data of the source instance, and the source instance remains unaffected during the cloning process. Depending on the recovery point in time, cloning supports the following two recovery methods:
By backup set: Recovers data based on a specific full backup set of the source instance, restoring the data to the state when that backup set was created.
By time point: Data can be restored to any point in time within the log retention period by performing incremental replay based on a full backup combined with log backups.
Does Cloning Affect Access to the Source Instance?
No. The cloning operation uses existing backup data for recovery 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 cloned instance automatically inherits the SQL Mode and parameter template configurations from the source instance. Users do not need to manually configure database parameters.
Does the Serverless Instance Support Cloning?
Not supported. The cloning feature currently applies only to provisioned specification instances. Serverless instances are not currently supported as source or target instances for cloning.
What Are the Common Causes of Cloning 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.
The replica configuration (including log replicas) of the source and target instances is inconsistent. For example, an instance with 2 replicas + 1 log replica cannot be cloned with a 3-replica instance.
The source instance is in an abnormal or unavailable state.
The account has insufficient balance or an overdue payment.
Snapshot cloning refers to creating a cloned instance based on snapshot-type backups (snapshot/instant_snapshot), in contrast to cloning based on physical backups. Because snapshot cloning requires the node topology of the target instance to match that of the source instance, the number of nodes and disk capacity of the target instance must not be lower than those of the source instance. Otherwise, the operation will fail due to insufficient specifications.
When Does Billing Start for a Clone Instance?
Billing for the cloned 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 cloning succeeds.
How Is the Selectable 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 of the cloned instance is not automatically inherited from the source instance's configuration. After cloning succeeds, you need to configure a backup policy separately for the cloned instance.
Does the Clone Instance Support Specification Changes?
Supported. After the cloned instance is successfully created, you can modify its specifications based on business requirements, such as scaling out nodes or expanding disk capacity.
Are There Any Limits on the Number of Cloning Operations?
There is no limit on the number of times. You can clone the same source instance multiple times as needed. However, the same source instance cannot be cloned concurrently and must be cloned serially.
Does Cloning Support Cross-Region Disaster Recovery?
Supported. TDSQL Boundless provides instance cloning capability based on the standby link, allowing instances to be cloned to a remote disaster recovery node to meet cross-region disaster recovery and data restoration requirements. For the specific supported scope and configuration methods, refer to the options actually provided in the console.