Help Center/
Distributed Database Middleware/
User Guide (ME-Abu Dhabi Region)/
Backup Management/
Restoring from Current Instance
Updated on 2022-02-22 GMT+08:00
Restoring from Current Instance
Prerequisites
- You have logged in to the DDM console.
- The current (source) DDM instance is in the Running state.
- Both GaussDB (for MySQL) and RDS DB instances are supported. The following uses RDS DB instances as an example.
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.
- Create as many RDS DB instances as there are in the source DDM instance.
- The new DDM instance has no RDS DB instances associated.
- The selected existing DDM instance has no schemas or accounts created.
- Select engine version MySQL 5.7 for each new RDS DB instance and ensure that its minor version is not earlier than the RDS DB instance version in the source DDM instance.
- Ensure that the storage space of each new RDS DB instance is not less than that in the source DDM instance.
- In the DDM instance list, click the name of the instance created in 1.
- In the upper right corner of the Basic Information area, click Restore from RDS Backup.
- On the displayed Restore from RDS Backup 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 DB 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.
- Restoring to an existing DDM instance will overwrite data on it and cause the instance to be unavailable during restoration.
- Ensure that no schema has been created or deleted since the time point you specify.
- Ensure that the destination DB instances have the same engines and versions as or later versions than and at least as much as storage space as source DB instances.
Parent topic: Backup Management
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot