Using a RegionlessDB Cluster for Remote DR

1. Log in to the TaurusDB console.
2. Click in the upper left corner and select a region and project.
3. On the RegionlessDB page, click Create RegionlessDB in the upper right corner.
   Figure 2 Creating a RegionlessDB cluster
   

4. In the Create RegionlessDB dialog box, configure RegionlessDB Name, Primary Instance Region, and Primary Instance.
   Figure 3 Configuring the RegionlessDB cluster information
   

   Table 1 Parameter description

   Parameter	Description
   RegionlessDB Name	The name must start with a letter and consist of 4 to 64 characters. Only letters (case-sensitive), digits, hyphens (-), and underscores (_) are allowed.
   Primary Instance Region	Select a region where the primary instance is located.
   Primary Instance	Select an existing pay-per-use or yearly/monthly instance as the primary instance of the RegionlessDB cluster.

5. Click OK.
6. After the primary instance is created, view and manage it.

   During the creation process, the instance status is Creating. To view the detailed progress and result of the creation, go to the Task Center page. After the status of the primary instance is Available, you can use the instance.

1. On the RegionlessDB page, locate the RegionlessDB cluster.
2. Click Add Standby Instance in the Operation column.
   Figure 4 Adding a standby instance
   

3. On the displayed page, configure related parameters.

   Table 2 Basic information

   Parameter	Description
   Billing Mode	Yearly/Monthly: a prepaid billing mode in which you pay for resources before using them. Bills are settled based on the subscription period. The longer the subscription, the bigger the discount. This mode is a good option for long-term, stable workloads. Pay-per-use: a postpaid billing mode. You pay as you go and just pay for what you use. The prices are calculated by the second but billed every hour. This mode allows you to adjust resource usage easily. You neither need to prepare for resources in advance, nor end up with excessive or insufficient preset resources.
   Region	Region where the standby instance is deployed. Products in different regions cannot communicate with each other through a private network. After a DB instance is purchased, the region cannot be changed.
   Creation Method	Create new
   DB Instance Name	The name must start with a letter and consist of 4 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
   DB Engine	TaurusDB
   Kernel Version	Kernel version of the standby instance. It must be 2.0.54.240600 or later. For details about the updates in each kernel version, see TaurusDB Kernel Version Release History. NOTE: To specify the kernel version, submit a service ticket.
   DB Instance Type	Only Cluster can be selected. There are 2 to 10 read replicas in a cluster instance in the RegionlessDB cluster.
   Storage Type	Shared
   AZ Type	An AZ is a physical region where resources have their own independent power supply and networks. AZs are physically isolated but interconnected through an internal network. Some regions support both single-AZ and multi-AZ deployment and some only support single-AZ deployment. Single AZ: The primary node and read replicas are deployed in the same AZ. Multi-AZ: The primary node and read replicas are deployed in different AZs to ensure high reliability.
   Time Zone	You need to select a time zone for your instance based on the region hosting your instance. The time zone is selected during instance creation and cannot be changed after the instance is created.
   Instance Specifications	For details about the specifications supported by TaurusDB, see Instance Specifications. TaurusDB is a cloud-native database that uses the shared storage. To ensure workload stability in high read/write pressure, the system controls the read/write peaks of DB instances based on instance specifications. For details about how to select instance specifications, see Performance White Paper.
   CPU Architecture	The CPU architecture can be x86 or Kunpeng. Under a CPU architecture, you need to select vCPUs and memory of the instance.
   Nodes	All nodes of the standby instance are read replicas. You can apply for a maximum of 10 read replicas at once for a pay-per-use instance. After an instance is created, you can add read replicas as required. Up to 15 read replicas can be created for a standby instance in a cluster.
   Storage	Storage will be scaled up dynamically based on the amount of data that needs to be stored, and is billed hourly on a pay-per-use basis.
   VPC	A dedicated virtual network in which your TaurusDB instance is located. It isolates networks for different workloads. You can select an existing VPC or create a VPC. For details about how to create a VPC, see Creating a VPC. If no VPC is available, TaurusDB allocates a VPC to you by default. CAUTION: Ensure that the VPC selected for the standby instance is connected to the VPC selected for the primary instance through a VPN. After a TaurusDB instance is created, the VPC cannot be changed. A subnet provides dedicated network resources that are logically isolated from other networks for network security. A private IP address is automatically assigned when you create a DB instance. You can also enter an idle private IP address in the subnet CIDR block.
   Security Group	It can enhance security by controlling access to TaurusDB from other services. When you select a security group, you must ensure that it allows the client to access instances. If no security group is available or has been created, TaurusDB allocates a security group to you by default. To ensure subsequent database connection and access, you need to allow all IP addresses to access your DB instance through port 3306 and over ICMP. Configure private network security group rules to ensure that the primary and standby instances in a cluster can communicate with each other.
   Parameter Template	Contains engine configuration values that can be applied to one or more instances. You can modify the instance parameters as required after the instance is created. If you use a custom parameter template when creating a DB instance, the specification-related parameters in the custom template will not be applied. Instead, the default values are used. For details, see What Parameters Should I Pay Attention to When Creating a DB Instance? After a DB instance is created, you can adjust its parameters as needed. For details, see Modifying Parameters in a Parameter Template.
   Enterprise Project	An enterprise project provides a way to manage cloud resources and enterprise members on a project-by-project basis. You can select an enterprise project from the drop-down list. The default project is default. To create an enterprise project, click Enterprise > Project Management in the upper right corner of the console. For details, see Creating an Enterprise Project.
   Tag	This parameter is optional. Adding tags helps you better identify and manage your DB instances. Each DB instance can have up to 20 tags. After a DB instance is created, you can view its tag details on the Tags tab. For details, see Tag Management.

   

   The instance password and table name case sensitivity are the same as those of the primary instance. You do not need to set them separately.

4. Click Next.
5. Confirm the information and click Submit.
6. Go to the Instances page to view and manage the instance.

   During the creation process, the instance status is Creating. To view the detailed progress and result of the creation, go to the Task Center page. After the status of the instance is Available, you can use the instance.

   If there is a large amount of data in the primary instance, it may take a long time to complete a full backup during standby instance creation.

Select the nearest standby instance to access the database based on the workload access area.

For example, use a standby instance to access the database and query data.

mysql> select * from mydatabase.orders;
+----------+---------------+------------+
| order_id | customer_name | order_date |
+----------+---------------+------------+
|        1 | UserA         | 2023-12-18 |
|        2 | UserB         | 2023-12-17 |
|        3 | UserC         | 2023-12-16 |
+----------+---------------+------------+