How do I back up a MongoDB database by using logical backup? - Database Backup

Database Backup (DBS) provides features such as single-table restoration, geo-redundancy, and long-term archiving for MongoDB databases. This topic describes how to use DBS to automatically back up a MongoDB database.

Features

Feature	Description
SQL file backup	DBS logically backs up data in the JSON format.
Geo-redundancy	DBS supports cross-region backup for a MongoDB database to an Object Storage Service (OSS) bucket that is deployed in the destination region. DBS allows you to restore the backup data to a MongoDB database that is deployed in the source, destination, or another region.
Long-term archiving	DBS can retain your backup data for up to 10 years. After the retention period expires, DBS transfers backup sets to Archive Storage.
Fine-grained backup	DBS allows you to back up a single table, a single database, multiple databases, or an entire MongoDB database instance.
Backup speed limit	DBS allows you to enable throttling for backup to reduce the negative impact of backup operations on database performance. For more information, see How do I change the maximum backup speed?
Single-table restoration	DBS allows you to restore a single table without the need to restore the entire database instance. This way, the restoration time is reduced. When you configure a restoration task, you can specify a table as the restoration object. For more information, see Restore MongoDB databases.

Create a backup schedule

For more information, see Create a backup schedule.

Note

When you purchase a backup schedule, set the Data Source Type parameter to MongoDB and the Backup Method parameter to Logical Backup.
For information about the granularity based on which DBS backs up and restores MongoDB databases, see Database engines and features.

Configure a backup schedule

Log on to the Database Backup (DBS) console.
In the left-side navigation pane, click Backup Schedules. In the top navigation bar, select a region.
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. DBS 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	The location of the database that you want to back up. Valid values: User-Created Database with Public IP Address <IP Address:Port Number> ECS-Hosted Database ApsaraDB for MongoDB Express Connect DB/VPN Gateway/Intelligent Gateway No public network IP: Port's self-built database (accessed through the database gateway) Note If you set the Database Location parameter to ApsaraDB for MongoDB, DBS automatically reads data from the secondary database to perform a full backup. If you set the Database Location parameter to User-Created Database with Public IP Address <IP Address:Port Number> or Express Connect DB/VPN Gateway/Intelligent Gateway, you can specify whether to configure the connection address of the secondary database based on your business requirements.
	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, DBS 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.
	Database Type	The type of the database that you want to back up. 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 database that you want to back up 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 database that you want to back up. 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 database that you want to back up. 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 database that you want to back up 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 database that you want to back up is deployed. Note This parameter is displayed only if you set the Database Location parameter to ApsaraDB for MongoDB.
	Peer VPC	The virtual private cloud (VPC) in which the database that you want to back up 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 database that you want to back up.
	Database Account	The username of the account that is used to connect to the database that you want to back up.
	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 DBS 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 DBS. 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 the volume of data to be backed up is large, we recommend that you purchase subscription storage plans to offset fees. For more information, see Use storage plans. 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. DBS uses AES-256 to encrypt data. The server-side encryption feature is used in OSS. When you upload an object to OSS, 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 backup data is not encrypted.

In the Edit Backup Objects step, find the database or table that you want to back up and add it to the Selected section. Then, click Next.
Note
- DBS allows you to back up a single table, 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 Database engines 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, configure the parameters that are described in the following table and click Next in the lower-right corner of the page.

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 DBS 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, DBS 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. The maximum number of actual concurrent threads varies based on backup schedule specifications. For more information, see How do I change the maximum backup speed?

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 state 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 in DBS? If your issue persists after you use the solution that is provided in the preceding topic, contact technical support in the DBS DingTalk group (ID: 35585947).

Related operations

After a database is backed up, you can view the backup schedule or restore the database. For more information, see View a backup schedule or Restore MongoDB databases.
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 plan.
You can check the fees that 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.