Adding a Disaster Recovery/Read-Only Instance
Download
Focus Mode
Font Size
This document describes how to add disaster recovery instances to a TDSQL Boundless primary instance. A disaster recovery instance asynchronously replicates data from the primary instance via CLS, providing cross-region or same-region disaster recovery capabilities for your business.
Prerequisites
Before a disaster recovery instance is created, ensure that the primary instance meets the following conditions:
Disaster recovery instances can only be created for a cluster edition primary instance whose status is running.
Note:
Only cluster edition instances support creating disaster recovery instances. Basic edition instances do not support creating disaster recovery instances.
Disaster recovery instances can only be created for instances with a kernel version of V19.0.0 or higher.
Note:
For instances of version V19.X, disaster recovery instances can only be created in the same region by creating a new instance. Furthermore, disaster recovery instances cannot be added for an instance more than five days after its creation.
Instances of version V20.0.0 or higher support creating disaster recovery instances by cloning from a backup set. They also support cross-region disaster recovery.
A primary instance supports creating only one disaster recovery instance.
The following tables cannot be synchronized via CLS. If such tables exist, the primary instance cannot establish a disaster recovery relationship:
Tables containing
HIDDEN PRIMARY KEYTables whose
PRIMARY KEY contains a string prefix indexSteps
1. Log in to the TDSQL Boundless console.
2. In the left sidebar, select Instance List. Click the Instance ID of the target primary instance to go to the Instance Details page.
3. In the Instance Architecture Diagram area, click Add Disaster Recovery/Read-Only Instance to go to the DR/Read-Only Instance purchase page.
4. On the purchase page, configure the disaster recovery instance parameters according to your business requirements.
For basic configuration, node specification configuration, network, and other settings: see Create Instance.
Database Configuration:
Parameter | Description |
Sync Rules | Default is Async. Note: 1. Data is asynchronously replicated to disaster recovery instances via CLS, keeping them synchronized with the primary instance. 2. Creating a disaster recovery/read-only instance triggers immediate data synchronization. The creation duration is affected by the data volume. During this period, console operations on the primary instance will be locked. Please plan your operation time accordingly. 3. Ensure that the primary instance is in the Running state and no tasks are being executed. Otherwise, the synchronization task may fail. |
5. After the configuration information and fees are confirmed, click Buy Now.
6. Return to the Instance List page to view the newly created disaster recovery instance. After creation, the disaster recovery instance will automatically be synchronized with the primary instance.
Limitations
The kernel version of a disaster recovery instance is consistent with that of the primary instance by default.
The number of storage replicas for a disaster recovery instance is consistent with that of the primary instance by default.
During creation, the primary instance status will temporarily change to modifying and will revert to running upon completion.
After a disaster recovery instance is successfully created, isolation or deletion operations cannot be performed individually on the primary instance/disaster recovery instance. You must first remove the disaster recovery relationship before performing isolation or deletion operations individually.
Help and Support
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback