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 2 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 3 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: Specifying the kernel version when buying an instance is in the OBT phase. To use this function, submit a service ticket.
     Creation Method	Select Migrate from RDS.
     Source Instance Information	Select the RDS for MySQL instance to be migrated from the drop-down list.
     DB Instance Type	Only cluster instances are supported. A cluster 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. Cluster 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 type of storage. With Huawei Cloud's hardware and network infrastructure technologies, DL5-based instances maintain the same high availability (zero RPO in the 3-AZ deployment) as DL6-based instances. Although the peak performance of DL5-based instances may be a bit less than what you get with DL6-based instances, the cost per unit of capacity is a lot less. DL5-based instances are suitable for CPU-intensive sub-core business systems, or application modules that need to minimize costs. For more information about storage types, see Storage Types.

   • Instance options
     Figure 3 Specifications and storage
     

     Table 4 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 cluster 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 once. You can also add read replicas after an instance is created. Each instance can contain up to 15 read replicas. For details, see Adding Read Replicas to a DB Instance.
     Storage	It contains the file 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 5 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 buy a batch of instances at once, a 4-digit numerical suffix will be added to the instance names, starting with -0001. If you later make another batch purchase, the new instance names will be numbered first using any suffixes missing from the sequence of your existing instances, and then continuing on from where your last batch purchase left off. For example, a batch of 3 instances gets the suffixes -0001, -0002, and -0003. If you deleted instance 0002 and then bought 3 more instances, the new instances would get the suffixes -0002, -0004, and -0005. 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 6 Advanced settings

     Parameter	Description
     Enterprise Project	This parameter is only available for enterprise users. To use it, 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	A parameter template contains the configuration values of a database engine. The parameters can be applied to one or more instances of the same type. In the drop-down list, you can select the default parameter template (Default-TaurusDB V2.0), the high-performance parameter template (Default-TaurusDB V2.0-High Performance), or a custom parameter template in the current region as required. Default-TaurusDB V2.0 contains DB engine defaults and system defaults that are configured based on the engine, compute class, and allocated storage space of an instance. Parameter values in the default template cannot be changed, but you can create a custom template with whatever values you require. Default-TaurusDB V2.0-High Performance is a set of optimized configuration parameters that aim to enhance the performance and reliability of database servers. The parameter settings in the template can be adjusted based on different application scenarios and hardware configurations. For details, see Introducing the High-Performance Parameter Template. You can select a custom parameter template and change the parameter values as required. The changes to parameter values in a custom parameter template are not applied to your instance until you apply the template to the instance. For details, see Applying a Parameter Template. If you select a custom parameter template when creating an 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 an 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	This parameter tags a TaurusDB instance. It is optional. Adding tags helps you better identify and manage your instances. Each instance can have up to 20 tags. After an instance is created, you can click its name and view its tags on the Tags page. For details, see Tag Management.

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 DRS migration task has been created.

1. On the Basic Information page of the TaurusDB instance, wait until the migration status becomes Incremental migration. Then, compare the database data and table data of the source and destination instances.
   Figure 7 Observing the migration status and replication delay
   
   1. On the Instances page of TaurusDB Enterprise Edition, locate an instance and click Log In in the Operation column.

      Alternatively, click the instance name on the Instances page. On the displayed Basic Information page, click Log In in the upper right corner.

      

   2. Enter the login username and password and click Test Connection. After the connection test is successful, click Log In. The DAS page is displayed.
   3. In the database list, check whether all source databases have been migrated to the TaurusDB Enterprise Edition instance.
   4. Click each database name, click SQL Window, and run SQL statements to check whether the table data has been migrated.

      SELECT * FROM table_name;

2. If the data is consistent and the replication latency is less than 60 seconds, 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,

1. click Roll Back Workloads. In the displayed dialog box, confirm the instance information and click OK.
   Figure 11 Rolling back workloads
   

2. 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
   

After data is migrated from an RDS for MySQL instance to a TaurusDB Enterprise Edition instance, if workloads are stable and the source instance is no longer required, you can release the RDS for MySQL instance. For details, see Deleting a Pay-per-Use RDS for MySQL Instance.