Data Management:Back up an ApsaraDB for MongoDB instance from a secondary database

Supported deployment locations of source instances

• ApsaraDB for MongoDB

  Note

  You need only to configure the MongoDB Instance ID parameter. The system reads data from the secondary database. For more information, see Manage a backup schedule.

• User-Created Database with Public IP Address <IP Address:Port Number>

• Express Connect DB/VPN Gateway/Intelligent Gateway

• No public network IP: Port's self-built database (accessed through the database gateway)

Procedure

In the following example, the deployment location of the source instance is Express Connect DB/VPN Gateway/Intelligent Gateway.

1. Log on to the DMS console V5.0.

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

3. On the Backup Schedules page, find the backup schedule that you want to configure and click Configure Backup Schedule in the Actions column.

4. 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	The access method of the source database. Select Express Connect DB/VPN Gateway/Intelligent Gateway. Note If you set the Database Location parameter to User-Created Database with Public IP Address <IP Address:Port Number>, you do not need to set the Peer VPC parameter.
   	Database Type	The type of the source database. Default value: MongoDB.
   	Peer VPC	The virtual private cloud (VPC) in which the source database is deployed.
   	Configuration of connection address of standby database	Specifies whether to configure the connection address of the secondary database. Set this parameter to Yes. Note If you select No for this parameter, you do not need to set the Alternate address or Alternate port number parameter.
   	Master Address	The endpoint that is used to connect to the primary database.
   	Master Port Number	The port that is used to connect to the primary database.
   	Alternate address	The endpoint that is used to connect to the secondary database.
   	Alternate port number	The port that is used to connect to the secondary database.
   	Database Name	The name of the source database.
   	Master Database Account	The username of the account that is used to connect to the source database.
   	Master Password	The password of the account that is used to connect to the source database. Note After you enter the username and password of the database account, click Test Connection next to the password to check whether information about the source database 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 information about the source 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.
   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 OSS 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 subscription storage plan to offset the fees of Data Disaster Recovery built-in storage. For more information, see Use storage plans. Data Disaster Recovery storage plans are more cost-efficient than the pay-as-you-go billing method.
   	OSS Bucket Name	The name of the OSS bucket in which you want to store data. This parameter is displayed only if you set the Backup Storage Type parameter to OSS For User.
   	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.

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

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

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

8. After the preceding configurations are complete, click Precheck in the lower-right corner of the page.

9. If the Precheck Passed message appears, click Start Task.