Distributed Database Middleware
Distributed Database Middleware
- What's New
- Service Overview
- Getting Started
-
User Guide
- Function Overview
- Permissions Management
-
Instance Management
- Buying a DDM Instance
- Splitting Read-only and Read-Write Services
- Changing Class of a DDM Node
- Scaling Out a DDM Instance
- Scaling In a DDM Instance
- Changing Billing Mode of a DDM Instance
- Renewing a DDM Instance
- Restarting a DDM Instance
- Unsubscribing from a DDM Instance
- Deleting a DDM Instance
- Modifying Parameters of a DDM Instance
- Splitting Read and Write Requests
- Configuring a Parameter Template
- Connection Management
-
Parameter Template Management
- Creating a Parameter Template
- Editing a Parameter Template
- Comparing Two Parameter Templates
- Viewing Parameter Change History
- Replicating a Parameter Template
- Applying a Parameter Template
- Viewing Application Records of a Parameter Template
- Modifying the Description of a Parameter Template
- Deleting a Parameter Template
- Task Center
- Schema Management
- Shard Configuration
- Data Node Management
- Account Management
- Backups and Restorations
-
Data Migration
- Overview
- Migration Evaluation
- Scenario 1: Migrating Data from Huawei Cloud RDS to DDM
- Scenario 2: Migrating Data from an On-Premises RDS Instance for MySQL to DDM
- Scenario 3: Migrating Data from a Third-Party RDS for MySQL Instance to DDM
- Scenario 4: Migrating Data from a Self-Built MySQL Instance to DDM
- Scenario 5: Migrating Data from Heterogeneous Databases to DDM
- Scenario 6: Exporting Data from a DDM Instance
- Slow Queries
- Monitoring Management
- Auditing
-
SQL Syntax
- Introduction
- DDL
- DML
- Functions
- Use Constraints
- Supported SQL Statements
- Global Sequence
- Database Management Syntax
- Advanced SQL Functions
- Quotas
- Change History
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
APIs (Recommended)
-
DDM Instances
- Buying a DDM instance
- Querying DDM Instances
- Querying Details of a DDM Instance
- Modifying the Name of a DDM Instance
- Modifying the Security Group of a DDM Instance
- Deleting a DDM Instance
- Restarting a DDM Instance
- Reloading Table Data
- Scaling out a DDM instance
- Scaling in a DDM instance
- Modifying the Read Policy of the Associated DB Instance
- Synchronizing Data Node Information
- Querying Nodes of a DDM Instance
- Querying Details of a DDM Instance Node
- Querying Parameters of a Specified DDM Instance
- Modifying Parameters of a DDM Instance
- Querying DDM Engine Information
- Querying DDM Node Classes Available in an AZ
- Changing the Node Class of a DDM Instance
- Schemas
- DDM Accounts
- Monitoring
-
DDM Instances
- APIs (Unavailable Soon)
- Appendix
- Change History
- SDK Reference
-
Best Practices
- Overview
- Formulating Sharding Rules
- Determining the Number of Shards in a Schema
- Using Broadcast and Unsharded Tables
- Transaction Models
- SQL Standards
- Migrating an Entire RDS Database to DDM
- Migrating an Entire MyCat Database to DDM
- Accessing DDM Using a JDBC Connection Pool
- Logging In to a DDM Instance Using Navicat
- Migrating Data from RDS for MySQL to DDM Using DRS
- Performance White Paper
-
FAQs
- General Questions
-
DDM Usage
- How Does DDM Perform Sharding?
- What Do I Do If I Fail to Connect to a DDM Instance Using the JDBC Driver?
- What Version and Parameters Should I Select?
- Why It Takes So Long Time to Export Data from MySQL Using mysqldump?
- What Do I Do If a Duplicate Primary Key Error Occurs When Data Is Imported into DDM?
- What Should I Do If an Error Message Is Returned When I Specify an Auto-Increment Primary Key During Migration?
- What Do I Do If an Error Is Reported When Parameter Configuration Does Not Time Out?
- Which Should I Delete First, a Schema or its Associated RDS Instances?
- Can I Manually Delete Databases and Accounts Remained in Data Nodes After a Schema Is Deleted?
- SQL Syntax
- RDS-related Questions
- Connection Management
- Resource Freezing, Release, Deletion, and Unsubscription
- Change History
- Videos
On this page
Help Center/
Distributed Database Middleware/
User Guide/
Backups and Restorations/
Restoring Data to a New Instance
Restoring Data to a New Instance
Updated on 2022-09-16 GMT+08:00
Overview
DDM allows you to restore data from the current instance to any point in time using an existing backup. This is a good choice for routine service backup and restoration.
Figure 1 Restore to New Instance

This section uses an RDS for MySQL instance as an example to describe how to restore data to a new DDM instance.
Restrictions
- Restoring data to a new DDM instance will overwrite data on it and cause the instance to be unavailable during restoration.
- Ensure that no schemas are created or deleted between the restoration time and the current time.
- The new RDS for MySQL DB instances must have the same or later versions than the original ones, and their storage space must be greater than or equal to that of the original ones.
- Data cannot be restored to a local RDS for MySQL instance.
- Data cannot be restored to an RDS for MySQL instance that uses SSDs for storage.
- Restoration is not supported if the DDM instance is in the primary network and the destination RDS for MySQL instance is in the extended network.
Prerequisites
- You have logged in to the DDM console.
- The current (source) DDM instance is in the Running state.
Procedure
- Create a DDM instance or select an existing DDM instance that meets the requirements in the region where the source DDM instance is located.
NOTE:
Ensure that the new DDM instance or the selected existing DDM instance is not associated with any RDS for MySQL instance and has no schemas or accounts.
- Create as many RDS for MySQL instances as there are in the source DDM instance.
NOTE:
- Ensure that the new RDS instances have the same or later versions than RDS instances associated with the source DDM instance.
- Ensure that each new RDS for MySQL instance has the same or larger storage space than each source RDS instances.
- In the DDM instance list, click the name of the instance created in 1.
- In the navigation pane on the left, choose Backups & Restorations. Click Restore to New Instance.
- On the displayed Restore to New Instance page, specify a time range and a point in time and select the DDM instance created in 1 as the destination DDM instance.
- Select the RDS for MySQL instances created in 2 as destination DB instances and check the confirmation box. Click OK. Wait for 1 to 3 minutes for the data restoration to complete.
Parent topic: Backups and Restorations
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.