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

From DDM to DDM (Single-Active DR)

Updated on 2024-11-30 GMT+08:00

Supported Source and Destination Databases

Table 1 Supported databases

Service database

DR Database

DDM instances

DDM instances

Database Account Permission Requirements

To start a DR task, the service and DR database users must meet the requirements in the following table. Different types of DR tasks require different permissions. For details, see Table 2. DRS automatically checks the database account permissions in the pre-check phase and provides handling suggestions.

Table 2 Database account permission

Type

Permission Required

Service database user

The user of the service database must have at least one permission, for example, SELECT.

DR database user

The user of the DR database must have at least one permission, for example, SELECT.

NOTE:
  • You are advised to create an independent database account for DRS task connection to prevent task failures caused by database account password modification.
  • After changing the account passwords for the service and DR databases, modify the connection information of the DRS task by referring to Modifying Connection Information to prevent automatic retry after a task failure. Automatic retry will lock the database accounts.

Prerequisites

Suggestions

CAUTION:
  • During the DR initialization, do not perform DDL operations on the service database. Otherwise, the task may be abnormal.
  • During DR initialization, ensure that no data is written to the DR database to ensure data consistency before and after DR.
  • The success of DR depends on environment and manual operations. To ensure a smooth DR, perform a DR trial before you start the DR task to help you detect and resolve problems in advance.
  • It is recommended that you start your DR task during off-peak hours to minimize the impact on your services.
    • If the bandwidth is not limited, initialization of DR will increase query workload of the source database by 50 MB/s and occupy 2 to 4 vCPUs.
    • To ensure data consistency, tables without a primary key may be locked for 3s during disaster recovery.
    • The data in the DR process may be locked by other transactions for a long period of time, resulting in read timeout.
    • If DRS concurrently reads data from a database, it will use about 6 to 10 sessions. The impact of the connections on services must be considered.
    • If you read a table, especially a large table, during DR, the exclusive lock on that table may be blocked.
  • Data-Level Comparison

    To obtain accurate comparison results, start data comparison at a specified time point during off-peak hours. If it is needed, select Start at a specified time for Comparison Time. Due to slight time difference and continuous operations on data, data inconsistency may occur, reducing the reliability and validity of the comparison results.

Precautions

Before creating a DR task, read the following precautions:

Table 3 Environment Constraints

Type

Restrictions

Disaster recovery objects

  • Only MyISAM and InnoDB tables support disaster recovery.
  • Accounts that have operation permissions on customized objects in the system database cannot be used for disaster recovery.
  • System tables are not supported.
  • Triggers and events do not support disaster recovery.
  • Disaster recovery cannot be configured for a specific service database.
  • Disaster recovery of DDM account permissions is not supported.
  • Disaster recovery for non-standard floating-point data that can be written in loose mode but cannot be written in strict mode is not supported. Such non-standard floating-point data may fail to be hit, causing data disaster recovery failures.

Service database configuration

  • In the public network, EIPs must be bound to each DDM instance and the associated RDS for MySQL instance.
  • The binlog of the RDS for MySQL instance associated with the DDM instance must be enabled and uses the ROW format and GTID.
  • If the storage space is sufficient, store the service database binlog for as long as possible. The recommended retention period is seven days.
  • The service database name must contain 1 to 64 characters, including only lowercase letters, digits, hyphens (-), and underscores (_).
  • The table name in the service database cannot contain non-ASCII characters, or the following characters: .'<>/\

DR database configuration

  • The DR DB instance is running properly. If the DR DB instance is a primary/standby instance, the replication status must also be normal.
  • The DR DB instance must have sufficient storage space.
  • The binlog and GTID of the RDS instance associated with the DDM instance must be enabled.
  • The minor version of the DR DDM instance must be the same as that of the service DDM instance.
  • The number of DDM DR instances must be the same as that of the RDS instances associated with the DDM service instance.
  • The sharding rules of the DDM DR instance must be the same as those of the DDMservice instance. You are advised to use the schema import and export functions to ensure sharding rule consistency.

Precautions

  • The parameter modification of the service database is not recorded in logs and is not synchronized to the DR database. Therefore, you need to modify the parameters after the DR database is promoted to the primary.
  • If a physically generated column in a table is generated based on a time type, the data in the column may be inconsistent.
  • The service database does not support point-in-time recovery (PITR).
  • Binlogs cannot be forcibly deleted. Otherwise, the DR task fails.
  • Resumable upload is supported, but data may be repeatedly inserted into a table that does not have a primary key.
  • If there is a DR task in a database, you are not allowed to create a migration or synchronization task (The database cannot be used as the source or destination database of the migration or synchronization task).
  • The DR relationship involves only one primary database. If the external database does not provide the superuser permission, it cannot be set to read-only when it acts as a standby database. Ensure that the data of the standby node is synchronized only from the primary node. Any other write operations will pollute the data in the standby database, data conflicts occur in the DR center and cannot be resolved.
  • The DDM DR database cannot create schemas automatically. You need to set the schema rules before disaster recovery.
  • After a task is created, you cannot add schemas to the service database or modify the old schema to associate with the new RDS DB instance. Otherwise, data cannot be backed up and restored or the task fails.
  • During DR, rebalance and reshard operations cannot be performed on DDM schemas.
  • During disaster recovery, if the password of the service database is changed, the DR task will fail. To rectify the fault, you can correct the service database information on the DRS console and retry the task to continue disaster recovery. Generally, you are advised not to modify the preceding information during disaster recovery.
  • If the service database port is changed during disaster recovery, the DR task fails. Generally, you are advised not to modify the service database port during disaster recovery.
  • During the DR initialization, do not perform DDL operations on the source database. Otherwise, the DR task may be abnormal.
  • Do not write data to the source database during the primary/standby switchover. Otherwise, data pollution or table structure inconsistency may occur, resulting in data inconsistency between the service database and DR database.

Procedure

  1. On the Disaster Recovery Management page, click Create Disaster Recovery Task.
  2. On the Create Disaster Recovery Instance page, select a region and project, specify the task name, description, and the DR instance details, and click Create Now.

    • Task information description
      Figure 1 DR task information
      Table 4 Task and recipient description

      Parameter

      Description

      Region

      The region where your service is running. You can change the region.

      Project

      The project corresponds to the current region and can be changed.

      Task Name

      The task name must start with a letter and consist of 4 to 50 characters. It can contain only letters, digits, hyphens (-), and underscores (_).

      Description

      The description consists of a maximum of 256 characters and cannot contain special characters !=<>'&"\

    • DR instance information
      Figure 2 DR instance information
      Table 5 DR instance settings

      Parameter

      Description

      DR Type

      Select Single-active.

      The DR type can be single-active or dual-active. If Dual-active is selected, two subtasks are created by default, a forward DR task and a backward DR task.

      NOTE:

      Only whitelisted users can use dual-active DR. To use this function, submit a service ticket. In the upper right corner of the management console, choose Service Tickets > Create Service Ticket to submit a service ticket.

      Disaster Recovery Relationship

      Select Current cloud as standby. This parameter is available only when you select Single-active.

      By default, Current cloud as standby is selected. You can also select Current cloud as active.

      • Current cloud as standby: The DR database is on the current cloud.
      • Current cloud as active: The service database is on the current cloud.

      Service DB Engine

      Select DDM.

      DR DB Engine

      Select DDM.

      Network Type

      The public network is used as an example.

      Available options: VPN or Direct Connect and Public network. By default, the value is Public network.

      DR DB Instance

      The DDM instance you created.

      Disaster Recovery Instance Subnet

      Select the subnet where the disaster recovery instance is located. You can also click View Subnets to go to the network console to view the subnet where the instance resides.

      By default, the DRS instance and the DR DB instance are in the same subnet. You need to select the subnet where the DRS instance resides and ensure that there are available IP addresses. To ensure that the disaster recovery instance is successfully created, only subnets with DHCP enabled are displayed.

      Destination DB Instance Access

      Select Read-only. This parameter is available only when you select Single-active.

      • During disaster recovery, the entire DR database instance becomes read-only. To change the DR database to Read/Write, you can change the DR database (or destination database) to a service database by clicking Batch Operation > Primary/Standby Switchover on the Disaster Recovery Management page.
      • If a DR task fails, the DR database automatically changes to the read/write state.
      • After the DR task is complete, the DR database changes to Read/Write.
      • When the external database functions as the DR database, the user with the superuser permission can set the database to read-only.
      • If a DRS instance node is rebuilt due to a fault, to ensure data consistency during the DRS task restoration, the current cloud standby database is set to read-only before the task is restored. After the task is restored, the synchronization relationship recovers.

      Specify EIP

      This parameter is available when you select Public network for Network Type. Select an EIP to be bound to the DRS instance. DRS will automatically bind the specified EIP to the DRS instance and unbind the EIP after the task is complete. The number of specified EIPs must be the consistent with that of DB instances.

      For details about the data transfer fee generated using a public network, see EIP Price Calculator.

    • AZ
      Figure 3 AZ
      Table 6 Task AZ

      Parameter

      Description

      AZ

      Select the AZ where you want to create the DRS task. Selecting the one housing the source or destination database can provide better performance.

    • Enterprise Project and Tags
      Figure 4 Enterprise projects and tags
      Table 7 Enterprise Project and Tags

      Parameter

      Description

      Enterprise Project

      An enterprise project you would like to use to centrally manage your cloud resources and members. Select an enterprise project from the drop-down list. The default project is default.

      For more information about enterprise projects, see Enterprise Management User Guide.

      To customize an enterprise project, click Enterprise in the upper right corner of the console. The Enterprise Project Management Service page is displayed. For details, see Creating an Enterprise Project in Enterprise Management User Guide.

      Tags

      • Tags a task. This configuration is optional. Adding tags helps you better identify and manage your tasks. Each task can have up to 20 tags.
      • If your organization has configured tag policies for DRS, add tags to tasks based on the policies. If a tag does not comply with the policies, task creation may fail. Contact your organization administrator to learn more about tag policies.
      • After a task is created, you can view its tag details on the Tags tab. For details, see Tag Management.
    NOTE:

    If a task fails to be created, DRS retains the task for three days by default. After three days, the task automatically stops.

  3. On the Configure Source and Destination Databases page, wait until the DR instance is created. Then, specify source and destination database information and click Test Connection for both the source and destination databases to check whether they have been connected to the DR instance. After the connection tests are successful, select the check box before the agreement and click Next.

    • Select Current cloud as the standby for Disaster Recovery Relationship in 2.
      Figure 5 Service database information

      Table 8 Service database settings

      Parameter

      Description

      Database Type

      Select a service database type.

      Middleware IP Address or Domain Name

      The IP address or domain name of the source DDM middleware.

      Port

      The port of the source DDM middleware. Value range: 1 to 65535

      Middleware Username

      The username of the source DDM instance.

      Middleware Password

      The password for the source DDM instance username.

      SSL Connection

      SSL encrypts the connections between the source and destination databases. If SSL is enabled, upload the SSL CA root certificate.

      NOTE:
      • The maximum size of a single certificate file that can be uploaded is 500 KB.
      • If SSL is disabled, your data may be at risk.

      DB Instance

      Enter the database information based on the actual DN sharded database and data DR relationship of DDM.

      For details, see How Do I Configure Source Database Information for a DDM DR Task?

      Region

      The region where the source database is located. This parameter is available only when Database Type for the source database is set to DDM. The region cannot be the region where the destination database is located.

      DB Instance Name

      The name of the service DB instance. This parameter is available only when the source database is a DDM database.

      Database Username

      The username for accessing the service database. This parameter is available only when the source database is a DDM database.

      Database Password

      The password for the service database username. This parameter is available only when the source database is a DDM database.

      NOTE:

      The IP address, domain name, username, and password of the service database are encrypted and stored in DRS and will be cleared after the task is deleted.

      Figure 6 DR database information

      Table 9 DR database settings

      Parameter

      Description

      DB Instance Name

      The DDM instance you selected when you create the DR task. The instance name cannot be changed.

      Database Username

      The username for accessing the DR database.

      Database Password

      The password for the database username. You can change the password if necessary. To change the password, perform the following operation after the task is created:

      If the task is in the Starting, Initializing, Disaster recovery in progress, or Disaster recovery failed status, in the DR Information area on the Basic Information tab, click Modify Connection Details. In the displayed dialog box, change the password.

      The database username and password are encrypted and stored in the system, and will be cleared after the task is deleted.

      • Select Current cloud as active for Disaster Recovery Relationship in 2.
        Figure 7 Service database information
        Table 10 Service database settings

        Parameter

        Description

        DB Instance Name

        The DDM instance you selected when you create the DR task. The instance name cannot be changed.

        Database Username

        The username for accessing the service database.

        Database Password

        The password for the database username. You can change the password if necessary. To change the password, perform the following operation after the task is created:

        If the task is in the Starting, Initializing, Disaster recovery in progress, or Disaster recovery failed status, in the DR Information area on the Basic Information tab, click Modify Connection Details. In the displayed dialog box, change the password.

        The database username and password are encrypted and stored in the system, and will be cleared after the task is deleted.

        Figure 8 DR database information
        Table 11 DR database settings

        Parameter

        Description

        Database Type

        Type of the DR database.

        Region

        The region where the DDM instance is located.

        DB Instance Name

        Name of the DR instance.

        NOTE:

        When the DB instance is used as the DR database, it is set to read-only. After the task is complete, the DB instance can be readable and writable.

        Database Username

        Username for logging in to the DR database.

        Database Password

        Password for the database username.

        NOTE:

        The username and password of the DR databases are encrypted and stored in DRS, and will be cleared after the task is deleted.

  4. On the Configure DR page, specify flow control and click Next.

    Table 12 DR settings

    Parameter

    Description

    Flow Control

    You can choose whether to control the flow.

    • Yes

      You can customize the maximum disaster recovery speed. During the disaster recovery, the speed of each task (or each subtask in multi-task mode) does not exceed the value of this parameter.

      In addition, you can set the time range based on your service requirements. The traffic rate setting usually includes setting of a rate limiting time period and a traffic rate value. Flow can be controlled all day or during specific time ranges. The default value is Always. A maximum of 10 time ranges can be set, and they cannot overlap.

      The flow rate must be set based on the service scenario and cannot exceed 9,999 MB/s.

      Figure 9 Flow control
    • No
      The DR speed is not limited and the outbound bandwidth of the source database is maximally used, which causes read consumption on the source database accordingly. For example, if the outbound bandwidth of the source database is 100 MB/s and 80% bandwidth is used, the I/O consumption on the source database is 80 MB/s.
      NOTE:
      • Flow control mode takes effect only in the DR initialization phase.
      • You can also change the flow control mode when the task is in the Configuration state. For details, see Modifying the Flow Control Mode.

  5. On the Check Task page, check the DR task.

    • If any check fails, review the failure cause and rectify the fault. After the fault is rectified, click Check Again.

      For details about how to handle check failures, see Solutions to Failed Check Items in Data Replication Service User Guide.

    • If the check is complete and the check success rate is 100%, click Next.
      NOTE:

      You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

  6. On the Confirm Task page, specify Start Time, Send Notifications, SMN Topic, Delay Threshold, RPO Delay Threshold, RTO Delay Threshold, Stop Abnormal Tasks After. After confirming that the configured information about the DR task is correct, click Submit.

    Figure 10 Task startup settings

    Table 13 Task settings

    Parameter

    Description

    Start Time

    Set Start Time to Start upon task creation or Start at a specified time based on site requirements.

    NOTE:

    Starting a DR task may slightly affect the performance of the service and DR databases. You are advised to start a DR task during off-peak hours.

    Send Notifications

    This parameter is optional. After enabled, select a SMN topic. If the status or latency metric of the DR task is abnormal, DRS will send you a notification.

    SMN Topic

    This parameter is available only after you enable Send Notifications and create a topic on the SMN console and add a subscriber.

    For details, see Simple Message Notification User Guide.

    Delay Threshold (s)

    During disaster recovery, a synchronization delay indicates a time difference (in seconds) of synchronization between the service and DR database.

    If the synchronization delay exceeds the threshold you specify, DRS will send alarms to the specified recipients. The value ranges from 0 to 3,600. To avoid repeated alarms caused by the fluctuation of delay, an alarm is sent only after the delay has exceeded the threshold for six minutes.

    NOTE:
    • Before setting the delay threshold, enable Send Notifications.
    • If the delay threshold is set to 0, no notifications will be sent to the recipient.

    RTO Delay Threshold (s)

    If the synchronization delay from the DRS instance to the DR database exceeds the threshold you specify, DRS will notify specified recipients. The value ranges from 0 to 3,600. To avoid repeated alarms caused by the fluctuation of delay, an alarm is sent only after the delay has exceeded the threshold for six minutes.

    NOTE:
    • Before setting the RTO delay threshold, enable Send Notifications.
    • If the delay threshold is set to 0, no notifications will be sent to the recipient.

    RPO Delay Threshold (s)

    If the synchronization delay from the DRS instance to the service database exceeds the threshold you specify, DRS will notify specified recipients. The value ranges from 0 to 3,600. To avoid repeated alarms caused by the fluctuation of delay, an alarm is sent only after the delay has exceeded the threshold for six minutes.

    NOTE:
    • Before setting the delay threshold, enable Send Notifications.
    • If the delay threshold is set to 0, no notifications will be sent to the recipient.
    • In the early stages of an incremental DR, more delay is normal because more data is waiting to be synchronized. In this situation, no notifications will be sent.

    Stop Abnormal Tasks After

    Number of days after which an abnormal task is automatically stopped. The value must range from 14 to 100. The default value is 14.

    NOTE:
    • You can set this parameter only for pay-per-use tasks.
    • Tasks in the abnormal state are still charged. If tasks remain in the abnormal state for a long time, they cannot be resumed. Any task in the abnormal state that has run for longer than the period you set here (in days) will automatically stop to avoid unnecessary fees.

  7. After the task is submitted, view and manage it on the Disaster Recovery Management page.

    • You can view the task status. For more information about task status, see Task Statuses.
    • You can click in the upper-right corner to view the latest task status.
    • By default, DRS retains a task in the Configuration state for three days. After three days, DRS automatically deletes background resources, but the task status remains unchanged. When you reconfigure the task, DRS applies for resources again.
    • For a public network task, DRS needs to delete background resources after you stop the task. The EIP bound to the task cannot be restored to the Unbound state until background resources are deleted.
    • For a task that is in the Disaster recovery in progress state, you can use data comparison to check whether data is consistent before and after the disaster recovery.

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