Migrating Data to TaurusDB Enterprise Edition (OBT)

1. Go to the Buy DB Instance page.
2. On the displayed Custom Config page, configure required information and click Next.
   • Basic configuration
     Figure 1 Basic configuration
     

     Table 1 Basic configuration

     Parameter	Description
     Billing Mode	Select Pay-per-use.
     Region	Region where an instance is deployed. NOTE: You cannot change the region of an instance once it is purchased.

   • Resource selection
     Figure 2 Resource selection
     

     Table 2 Resource selection

     Parameter	Description
     DB Engine Version	Select TaurusDB V2.0.
     Kernel Version	DB kernel version. For details about the updates in each kernel version, see TaurusDB Kernel Version Release History. NOTE: To specify the kernel version when buying an instance, submit a request by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.
     Creation Method	Select Migrate from RDS.
     Source Instance Information	Select an RDS for MySQL instance or TaurusDB Standard Edition instance from the drop-down list.
     Edition Type	Enterprise: Enterprise Edition is an enterprise-grade cloud-native database with high scalability and performance. It is fully compatible with open-source MySQL 8.0. It decouples compute from storage and uses Huawei-developed Data Function Virtualization (DFV), which scales to up to 128 TB per instance. A failover can be complete within seconds. High-value capabilities such as read/write splitting, operator pushdown, a serverless framework, and HTAP are also supported. It provides the high availability and superior performance of a commercial database at the price of an open-source database.
     DB Instance Type	Only primary/standby instances are supported. A primary/standby instance can contain one primary node and 1 to 15 read replicas. The primary node processes read and write requests, and the read replicas process only read requests. If the primary node becomes unavailable, TaurusDB automatically fails over to a read replica. Primary/Standby instances apply to medium- and large-sized enterprises in the Internet, taxation, banking, and insurance sectors.
     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 achieve higher availability and reliability. It is suitable for workloads that require cross-AZ DR or are insensitive to cross-AZ latency.
     Storage Type	DL6 The original Shared storage. The default storage type of TaurusDB instances created before July 2024 is Shared storage, while that of TaurusDB instances created in July 2024 and beyond is DL6. DL6-based instances achieve zero RPO with a 3-AZ deployment and deliver better performance and higher peak throughput. They are suitable for core application systems that are sensitive to performance and have demanding requirements on storage I/O during peak hours, such as those in finance, e-commerce, government, and gaming. DL5 A new storage type. With Huawei Cloud's hardware and network infrastructure technologies, DL5-based instances maintain the same high availability as DL6-based instances with 3 AZs and zero RPO. Compared with DL6-based instances, although the peak performance of DL5-based instances may decrease, the cost per unit capacity is significantly reduced. DL5-based instances are suitable for CPU-intensive sub-core business systems or application modules that focus on minimal costs. For more information about storage types, see Storage Types.

   • Instance options
     Figure 3 Specifications and storage
     

     Table 3 Specifications and storage

     Parameter	Description
     Resource Type	Select Shared.
     Instance Specifications	TaurusDB is a cloud-native database that uses the shared storage. To ensure that instances run stably under high read/write pressure, TaurusDB controls the read/write peaks of instances based on instance specifications. For details about how to select instance specifications, see Performance White Paper. For more information about instance specifications, see Instance Specifications.
     CPU Architecture	Select x86 or Kunpeng. x86: x86 instances use Intel® Xeon® Scalable processors and feature robust and stable computing performance. When working on high-performance networks, the instances provide the additional performance and stability that enterprise-class applications demand. Kunpeng: Kunpeng instances use Kunpeng 920 processors and 25GE high-speed intelligent NICs for powerful compute and high-performance networks, making them an excellent choice for enterprises needing cost-effective, secure, and reliable cloud services.
     Nodes	This parameter is mandatory for primary/standby instances. By default, each instance can contain one primary node and multiple read replicas. You can create up to 9 read replicas for a pay-per-use instance at a time. After an instance is created, you can add read replicas as required. Up to 15 read replicas can be added to an instance. For details, see Adding Read Replicas to a DB Instance.
     Storage	It contains the system overhead required for inodes, reserved blocks, and database operations. Storage of a pay-per-use instance 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.
     Backup Space	TaurusDB provides free backup space equal to the amount of your used storage. After the free backup space is used up, you will be billed for the additional space on a pay-per-use basis.

     Figure 4 Setting instance information
     

     Table 4 Instance information

     Parameter	Description
     DB Instance Name	Enter the TaurusDB instance name at the destination. The name must start with a letter and consist of 4 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed. If you create multiple instances at a time, a hyphen (-) followed by a number with four digits will be appended to the instance name, starting with -0001. For example, if you enter instance, the first instance will be named instance-0001, the second instance-0002, and so on. The names for instances created in batches must consist of 4 to 59 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
     Source Instance Administrator Password	Enter the administrator password of the source instance. After entering the password, click Test Connection to verify the password.

   • Advanced settings
     Figure 5 Advanced settings
     

     Table 5 Advanced settings

     Parameter	Description
     Enterprise Project	Only available for enterprise users. If you want to use this function, contact customer service. 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.
     Parameter Template	Contains engine configuration values that can be applied to one or more instances. In the drop-down list, you can select the default parameter template, the high-performance parameter template, or a custom parameter template in the current region as required. You can select an appropriate parameter template as required. For more information about parameter templates, see Parameter Management. For more information about the high-performance parameter template, see Introducing the High-Performance Parameter Template. NOTICE: If you use a custom parameter template when creating a DB instance, the following specification-related parameters in the custom template are not applied. Instead, the default values are used. innodb_buffer_pool_size innodb_log_buffer_size max_connections innodb_buffer_pool_instances innodb_page_cleaners innodb_parallel_read_threads innodb_read_io_threads innodb_write_io_threads threadpool_size The value of innodb_parallel_select_count is determined by your instance specifications, instead of the parameter value you configured in the parameter template. The default value is OFF for instance with 16 vCPUs or less and ON for instances with more than 16 vCPUs. After a DB instance is created, you can adjust its parameters as needed. For details, see Modifying Parameters of a DB Instance.
     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.
     Tag	Tags a DB instance. 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.

   If you have any questions about the price, click Pricing details at the bottom of the page.

   

   The performance of a DB instance depends on its configurations. Hardware configuration items include the instance specifications, storage type, and storage space.

3. Confirm your settings.
   • If you need to modify your settings, click Previous.
   • If you do not need to modify your settings, click Submit.
4. After the TaurusDB instance is created, click the instance name to go to the Basic Information page. The instance status becomes Migrating RDS data, which means the system starts to create a DRS migration task.
   Figure 6 Creating a migration task
   

   Wait until the migration status changes to Incremental migration, which means the migration task has been created.

1. On the Basic Information page of the TaurusDB instance, wait until the migration status becomes Incremental migration and the replication delay is less than 60 seconds, and then migrate workloads.
   Figure 7 Observing the migration status and replication delay
   

2. Click Migrate Workloads.
3. In the displayed dialog box, confirm the instance information and click OK.
   Figure 8 Migrating workloads
   

4. On the Basic Information page of the TaurusDB instance, check that the instance status is Migrating RDS data | Switching virtual IP address.
   Figure 9 Checking the TaurusDB instance status
   

   After the migration is complete, the read/write statuses of both the source and destination instances changed, the private IP address changed to that of the source instance, and the replication direction also changed.

   Figure 10 Checking the read/write statuses and replication direction after the migration
   

   If you do not want to use the TaurusDB instance, click Roll Back Workloads. In the displayed dialog box, confirm the instance information and click OK.

   Figure 11 Rolling back workloads
   

   After the workloads are rolled back, related information is restored to the status before the migration.

After the migration is complete, you can stop the migration. After the migration is stopped, the DRS migration task is terminated. Data will not be synchronized between instances, and the migration lock will be released. The TaurusDB instance will be billed and the system triggers a full backup for the instance.

You can perform the following operations to stop the migration:

1. On the Basic Information page of the TaurusDB instance, click Stop Migration.
2. In the displayed dialog box, confirm the instance information and click OK.
   Figure 12 Confirming the instance information