Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ TaurusDB/ User Guide/ Data Migration/ Migrating Data to TaurusDB Enterprise Edition (OBT)

Migrating Data to TaurusDB Enterprise Edition (OBT)

Updated on 2025-02-12 GMT+08:00

You can migrate data from RDS for MySQL and TaurusDB Standard Edition to TaurusDB Enterprise Edition.

Constraints

  • To use this function, submit a request by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.
  • To use this function, you must have the DRS Administrator privilege of DRS and the GaussDB FullAccess privilege of TaurusDB.
  • This function is only available for pay-per-use instances.
  • This function only supports the migration from RDS for MySQL and TaurusDB Standard Edition 8.0 to TaurusDB Enterprise Edition 8.0.

Step 1: Create a Migration Task

  1. Go to the Buy DB Instance page.
  2. On the displayed page, configure required information and click Next.
    Table 1 Basic information

    Parameter

    Description

    Billing Mode

    Select Pay-per-use.

    Region

    Region where the instance is deployed

    NOTICE:
    • Regions are geographic areas isolated from each other. Resources are region-specific and cannot be used across regions through internal network connections. For lower network latency and quicker resource access, select the nearest region.
    • You cannot change the region of an instance once it is purchased.

    Creation Method

    Select Migrate from RDS.

    Source Instance Information

    Select the RDS instance to be migrated from the drop-down list.

    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.

    DB Engine

    TaurusDB V2.0

    Kernel Version

    DB kernel version. For details about the updates in each minor kernel version, see TaurusDB Kernel Version Release History.

    NOTE:

    DB Instance Type

    Cluster: 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.

    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.

    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.

    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.

    Table 2 Specifications and storage

    Parameter

    Description

    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 specifications, see Performance White Paper.

    For more information about specifications, see Instance Specifications.

    After an instance is created, you can change its vCPUs and memory. For details, see Changing the vCPUs and Memory of a DB Instance or Node.

    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 a time.
    • You can also add read replicas after an instance is created. 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.

    Table 3 Network

    Parameter

    Description

    Source Instance Administrator Account

    The default username is root.

    Source Instance Administrator Password

    Enter the administrator password of the source instance.

    After entering the username and password, click Test Connection to check that the username and password of the instance are correct.

    Table 4 Other information

    Parameter

    Description

    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.

    NOTICE:
    • If you select 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.

    For more information about parameter templates, see Parameter Template Management. For more information about the high-performance parameter template, see Introducing the High-Performance Parameter Template.

    You can modify the instance parameters as required after a DB instance is created. For details, see Modifying Parameters of a DB Instance.

    Enterprise project

    This parameter is for enterprise users. To specify it, submit a request by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.

    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.

    Table 5 Tag

    Parameter

    Description

    Tag

    Tags a DB instance. This parameter is optional. Adding tags to DB instances helps you better identify and manage the 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.

    NOTE:

    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 system starts to create a DRS migration task.

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

Step 2: Migrate Workloads

  1. On the Basic Information page of the TaurusDB instance, wait until the migration status changes to Incremental migration in progress and the replication latency is less than 60 seconds, and then migrate workloads.
  2. Click Migrate Workloads.

  3. In the displayed dialog box, confirm the instance information and click Yes.

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

    After the migration is complete, you can see that the read/write status of the source and destination instances changed, the private IP address of the source instance changed to the private IP address of the RDS for MySQL instance, and the replication direction changed.

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

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

Step 3: Stop 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 Yes.

    After the migration is stopped, the TaurusDB instance will function like a regular instance.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback