Logically back up and restore a MongoDB database hosted on a third-party cloud or a self-managed MongoDB database - Data Management

Data Disaster Recovery provides features for MongoDB databases, such as single-collection restoration, cross-region backup, full or incremental backup, and long-term archiving. This topic describes how to use Data Disaster Recovery to logically back up and restore a MongoDB database hosted on a third-party cloud or a self-managed MongoDB database.

Create a backup schedule

For more information, see Create a backup schedule.

Note

When you purchase a backup schedule, set the source database type to MongoDB and the backup method to Logical Backup.
For information about the granularity based on which Data Disaster Recovery backs up and restores a MongoDB database, see Supported database types and features.

Configure a backup schedule

Log on to the DMS console V5.0.
In the top navigation bar, choose Security and Specifications (DBS) > Disaster Recovery for Data (DBS) > Backup Plan.
Note
If you use the DMS console in simple mode, move the pointer over the icon in the upper-left corner of the DMS console and choose All Features > Security and Specifications (DBS) > Disaster Recovery for Data (DBS) > Backup Plan.
On the Backup Schedules page, find the backup schedule that you want to configure and click Configure Backup Schedule in the Actions column.

In the Configure Backup Source and Destination step, configure the backup source and destination, and click Next in the lower-right corner of the page.

Section	Parameter	Description
N/A	Schedule Name	The name of the backup schedule. Data Disaster Recovery automatically generates a backup schedule name. We recommend that you enter a descriptive name that is easy to identify. Backup schedule names do not need to be unique.
Backup Source Information	Backup Mode	The method that is used to back up data. Set this parameter to Logical Backup.
	Database Location	No public network IP: Port's self-built database (accessed through the database gateway): backs up a self-managed database by using a database gateway. If you select this option, you must configure the Gateway instance ID parameter. Configure a database gateway for the database in advance. User-Created Database with Public IP Address <IP Address:Port Number>: backs up a self-managed database by using the public IP address of the database. If you select this option, you must also configure the Address and Port Number parameters. ECS-Hosted Database: backs up a database hosted on an Elastic Compute Service (ECS) instance. You must also configure the ECS Instance ID and Port Number parameters. Express Connect DB/VPN Gateway/Intelligent Gateway: backs up a self-managed database by using a virtual private cloud (VPC). If you select this option, you must configure the Peer VPC parameter. Configure a VPC for the database in advance.
	Database Type	The type of the source database. By default, the database type that you select when you create the backup schedule is used. Note This parameter is not displayed if you set the Database Location parameter to ApsaraDB for MongoDB.
	Peer VPC	The VPC in which the source database resides. Note This parameter is displayed only if you set the Database Location parameter to Express Connect DB/VPN Gateway/Intelligent Gateway.
	Configuration of connection address of standby database	Specifies whether to configure the connection address of the secondary database. If you select Yes for this parameter, Data Disaster Recovery reads data from the secondary database to perform a full backup. Note For more information, see Back up a MongoDB instance from a secondary database.
	Instance Region	The region in which the source database is deployed. Note This parameter is displayed only if you set the Database Location parameter to ECS-Hosted Database, ApsaraDB for MongoDB, or No public network IP: Port's self-built database (accessed through the database gateway).
	Address	The endpoint that is used to connect to the source database. Note This parameter is displayed only if you set the Database Location parameter to User-Created Database with Public IP Address <IP Address:Port Number>, Express Connect DB/VPN Gateway/Intelligent Gateway, or No public network IP: Port's self-built database (accessed through the database gateway).
	Port Number	The port number that is used to connect to the source database. Note This parameter is not displayed if you set the Database Location parameter to ApsaraDB for MongoDB.
	ECS Instance ID	The ID of the Elastic Compute Service (ECS) instance in which the source database is deployed. Note This parameter is displayed only if you set the Database Location parameter to ECS-Hosted Database.
	Gateway instance ID	The ID of the database gateway. Note This parameter is displayed only if you set the Database Location parameter to No public network IP: Port's self-built database (accessed through the database gateway).
	Database Name	The name of the source database.
	Database Account	The username of the account that is used to connect to the source database. Note Make sure that the account has the read permissions on the local database.
	Password	The password of the account that is used to connect to the database that you want to back up. After you enter the username and password of the database account, click Test Connection next to the password to check whether the information about the database that you want to back up is valid. If the specified parameters are valid, the Test Passed message is displayed. If the Test Failed message is displayed, click Check next to Test Failed. Modify the information about the database that you want to back up based on the check results.
	Compliance warranty regarding cross-border data transfers	Read and agree to the compliance commitment by selecting the check box.
Backup Destination Information	Backup Storage Type	The type of storage that is used to store the backup data. Valid values: DBS Storage (recommended): Backup data is stored in Data Disaster Recovery without the need to create an Object Storage Service (OSS) bucket. You are charged based on the volume of your data that is stored in Data Disaster Recovery. For more information about the billing method, see Storage fees. OSS For User: You must create a bucket in the OSS console in advance. For more information, see Create buckets. Note In this example, DBS Storage (recommended) is selected. If you select OSS For User, you must configure the OSS Bucket Name parameter. Only the standard storage class is supported. If you want to store a large amount of data, we recommend that you purchase a Data Disaster Recovery subscription storage plan to offset built-in storage fees. Data Disaster Recovery storage plans are more cost-efficient than the pay-as-you-go billing method.
Backup Destination Information	Storage Encryption	The method that is used to encrypt the stored data. Valid values: Encrypted: recommended. Data Disaster Recovery uses AES-256 to encrypt the stored data. The server-side encryption feature is used in OSS. When you upload an object to a bucket for which server-side encryption is enabled, OSS encrypts and stores the object. When you download the encrypted object from OSS, OSS decrypts the object and returns the decrypted object to you. For more information, see Server-side encryption. Non-encrypted: The stored data is not encrypted.

In the Edit Backup Objects step, find the database or collection that you want to back up and add it to the Selected section. Then, click Next.
Note
- Data Disaster Recovery allows you to back up a single collection, a single database, or multiple databases. You can click Select All in the lower-left corner of the Available section to select all databases. The supported backup objects vary based on the database types. For more information, see Supported database types and features.
- By default, a backup schedule cannot be used to back up a database that is created after the backup schedule is created. To back up the database, you can add the database to the backup schedule on the Configure Task page of the backup schedule. For more information, see Modify backup objects.

In the Configure Backup Time step, set the parameters that are described in the following table and click Next.

Parameter	Description
Full-scale Backup Frequency	The frequency of the backup schedule. Valid values: Periodic Backup and Single Backup. Note If you select Periodic Backup, you must configure the Full Data Backup Recurrence and Start At parameters.
Full Data Backup Recurrence	The days of the week on which Data Disaster Recovery runs the backup schedule. You can select one or more days of a week. Select at least one day of the week.
Start At	The start time of the backup. We recommend that you set a point in time within off-peak hours. Example: 01:00. Note If a previous full data backup is not finished at the start time of the next backup, Data Disaster Recovery skips the next backup.
Incremental Backup	Specifies whether to enable incremental backup. This parameter is displayed only if you set the Full-scale Backup Frequency parameter to Periodic Backup.
Maximum Concurrent Threads for Full Data Backup	The maximum number of concurrent threads available for a full backup. You can set this parameter to adjust the backup speed. For example, you can reduce the number of backup threads to minimize impacts on the database.

In the Edit Lifecycle step, configure the lifecycle for full backup data in the Configure Full Data Backup Lifecycle section.
If you set the Incremental Backup parameter to Enable in Step 6, you must configure the lifecycle for incremental backup data. For more information about the lifecycle rules of backup data, see How do I manage the lifecycle rules of backup sets?
After the preceding configurations are complete, click Precheck in the lower-right corner of the page.
If the Precheck Passed message appears, click Start Task.
Note
- If the status of the backup schedule changes to Running, the backup schedule takes effect.
- If an exception or error occurs when you start the backup schedule, troubleshoot the exception or error at the earliest opportunity. For more information, see How do I fix errors for an abnormal backup schedule? If the issue persists after you use the solution that is provided in the preceding topic, contact technical support in the DingTalk group (ID: 35585947).

Restore backup data

Log on to the DMS console V5.0.
In the top navigation bar, choose Security and Specifications (DBS) > Disaster Recovery for Data (DBS) > Backup Plan.
Note
If you use the DMS console in simple mode, move the pointer over the icon in the upper-left corner of the DMS console and choose All Features > Security and Specifications (DBS) > Disaster Recovery for Data (DBS) > Backup Plan.
On the Backup Schedules page, find the backup schedule that you want to manage and click Manage in the Actions column.
On the Configure Task page, click Restore Database in the upper-right corner.

In the Set Time Restored To step of the Create Restore Task wizard, configure the parameters that are described in the following table and click Next.

Section	Parameter	Description
N/A	Task Name	The name of the task. Data Disaster Recovery automatically generates a task name. We recommend that you specify a descriptive name that is easy to identify. Task names do not need to be unique.
Set Time Restored To	Time Range Available to Restore	The time range that is available to restore the source database. The source database can be restored to a point in time within the time range.
Set Time Restored To	Restore To	The point in time to which you want to restore the source database. The point in time must be within the time range that is specified by the Time Range Available to Restore parameter.
Configure Destination Database	Database Location	The location of the destination database. Valid values: No public network IP: Port's self-built database (accessed through the database gateway): backs up a self-managed database by using a database gateway. If you select this option, you must configure the Gateway instance ID parameter. Configure a database gateway for the database in advance. User-Created Database with Public IP Address <IP Address:Port Number>: backs up a self-managed database by using the public IP address of the database. If you select this option, you must also configure the Address and Port Number parameters. ECS-Hosted Database: backs up a database hosted on an ECS instance. You must also configure the ECS Instance ID and Port Number parameters. ApsaraDB for MongoDB Express Connect DB/VPN Gateway/Intelligent Gateway: backs up a self-managed database by using a VPC. If you select this option, you must configure the Peer VPC parameter. Configure a VPC for the database in advance.
	Database Type	The type of the destination database. By default, the database type that you select when you create the backup schedule is used. Note This parameter is not displayed if you set the Database Location parameter to ApsaraDB for MongoDB.
	Instance Region	The region in which the destination instance resides. Note This parameter is displayed only if you set the Database Location parameter to ECS-Hosted Database, ApsaraDB for MongoDB, or No public network IP: Port's self-built database (accessed through the database gateway).
	Address	The endpoint that is used to connect to the destination database. Note This parameter is displayed only if you set the Database Location parameter to User-Created Database with Public IP Address <IP Address:Port Number>, Express Connect DB/VPN Gateway/Intelligent Gateway, or No public network IP: Port's self-built database (accessed through the database gateway).
	Port Number	The port number that is used to connect to the destination database. Note This parameter is not displayed if you set the Database Location parameter to ApsaraDB for MongoDB.
	ECS Instance ID	The ID of the ECS instance on which the destination database is deployed. Note This parameter is displayed only if you set the Database Location parameter to ECS-Hosted Database.
	MongoDB Instance ID	The ID of the ApsaraDB for MongoDB instance in which the destination database is deployed. Note This parameter is displayed only if you set the Database Location parameter to ApsaraDB for MongoDB.
	Peer VPC	The VPC in which the destination database resides. Note This parameter is displayed only if you set the Database Location parameter to Express Connect DB/VPN Gateway/Intelligent Gateway.
	Gateway instance ID	The ID of the database gateway. Note This parameter is displayed only if you set the Database Location parameter to No public network IP: Port's self-built database (accessed through the database gateway).
	Database Name	The name of the destination database.
	Database Account	The username of the account that is used to connect to the destination database.
	Password	The password of the account that is used to connect to the destination database. Note After you enter the username and password of the database account, click Test Connection next to the password to check whether the information of the destination database is valid. If the specified information is valid, the "Test Passed" message appears. If the "Test Failed" message appears, click Check next to Test Failed. Modify the information of the destination database based on the check results.
	Compliance warranty regarding cross-border data transfers	Read and agree to the compliance commitment by selecting the check box.

In the Configure Objects to Restore step, configure the parameters described in the following table and click Precheck.

Parameter	Description
Conflict Handling	By default, Rename Object with the Same Name is selected for the Conflict Handling parameter. For example, if the `job_info` table to be restored shares the same name with a table in the destination database, the system renames the restored table in the following format: `job_info_dbs_<Restore task ID>_<Timestamp>`.
Objects to Restore	Select the database or table that you want to restore in the Available section and click the rightwards arrow to add it to the Selected section. Note Data Disaster Recovery allows you to restore some databases by database or collection. This reduces the amount of data to be restored and shortens the recovery time objective (RTO). For more information about the supported restoration granularity, see Supported database types and features.

If the Precheck Passed message appears in the Precheck dialog box, click Start Task.
To view the database restoration progress, click Restore Tasks in the left-side navigation pane.
Note
The restoration duration depends on the specifications of the backup schedule and the size of the database to be restored. The restoration duration is shorter for a backup schedule with higher specifications. For more information, see Performance tests on logical backup and physical backup.

Related operations

You can call the CreateBackupPlan operation to create a backup schedule. You can also call the CreateAndStartBackupPlan operation to create, configure, and start a backup schedule. For more information, see CreateBackupPlan or CreateAndStartBackupPlan.
You can modify the backup source and backup objects of a backup schedule. You can also modify the backup strategies of a backup schedule such as the backup time and backup retention policy. For more information, see Manage a backup schedule.
You can check the fees that you may be charged for a backup schedule. For more information, see Billing FAQ.
To reduce costs, you can pause a backup schedule that you do not need. For more information, see Pause or start a backup schedule.