Database backup (DBS) allows you to read data from secondary databases for full backup to reduce the impact on primary databases. This topic describes how to configure a backup schedule to back up a MongoDB instance from a secondary database.

Prerequisites

  • A MongoDB replica set instance is created.
  • A backup schedule is created. For more information, see Create a backup schedule.
    Note The backup method of the backup schedule is logical backup.

Supported deployment locations of source instances

  • ApsaraDB for MongoDB
    Note You need only to specify the MongoDB Instance ID parameter. DBS reads data from the secondary database. For more information, see Configure the 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 DBS console.
  2. In the left-side navigation pane, click Backup Schedules. On the Backup Schedules page, select a region in the upper-left corner.
  3. Find the ID of the backup schedule that you want to configure and click Configure Backup Schedule in the Actions column.
    eddd
  4. In the Configure Backup Source and Destination step of the Configure Backup Schedule wizard, configure the backup source and destination, and click Next in the lower-right corner of the page.
    Configure Backup Source and Destination
    Section Parameter Description
    N/A Schedule Name The name of the backup schedule. DBS generates a backup schedule name. We recommend that you set a descriptive name that is easy to identify. Backup schedule names do not have to be unique.
    Backup Source Information Backup Mode The method that is used to back up data. Set the value to Logical Backup.
    Database Location The deployment location of the database. Set this parameter to 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 database that you want to back up. Default value: MongoDB.
    Peer VPC The virtual private cloud (VPC) in which the database that you want to back up 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 database that you want to back up.
    Master Database Account The username of the account that is used to connect to the database that you want to back up.
    Master Password The password of the account that is used to connect to the database that you want to back up.
    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 database that you want to back up is correct. If the specified parameters are valid, the Test Passed message appears. If the Test Failed message appears, click Check next to Test Failed. Modify the information about the database that you want to back up based on the check results.
    Backup Destination Information Backup Storage Type The type of storage that is used to store backup data. Valid values:
    • DBS Storage (recommended): Backup data is stored in DBS without requiring you to create storage space. 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.

      To reduce storage costs, we recommend that you use subscription storage plans. For more information, see Use storage plans.

    • OSS For User: You must create a bucket in the Object Storage Service (OSS) console in advance. For more information, see Create buckets.
    Note In this example, set this parameter to DBS Storage (recommended). If you set this parameter to OSS For User, you must set the OSS Bucket Name parameter.
    OSS Bucket Name

    This parameter is displayed only when 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. DBS uses AES-256, one of the advanced encryption standard ciphers, 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 backup 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 If you back up an entire database, the permission data and stored procedures are also backed up.
  6. In the Configure Backup Time step, set 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. Select Periodic Backup or Single Backup as needed.

    Note If you set this parameter to Periodic Backup, you must set 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, such as 01:00. We recommend that you set a time during off-peak hours.

    Note If a previous full backup is not finished at the start time of the next full backup, DBS skips the next full backup.
    Incremental Backup

    Specifies whether to enable incremental backup.

    This parameter is displayed only when 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, reduce the number of backup threads to minimize the impact 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?.

  7. In the Edit Lifecycle step, configure the lifecycle for a full backup set in the Configure Full Data Backup Lifecycle section.
    If you set the Incremental Backup parameter to Enable in the previous step, you must also configure the lifecycle for an incremental backup set. For more information about the lifecycle of backup sets, see How do I manage the lifecycle rules of backup sets?
  8. After the configurations are complete, click Precheck in the lower-right corner of the page.
  9. If the Precheck Passed message appears, click Start Task.
    Note When the status of the backup schedule changes to Running, the backup schedule takes effect. You can view the backup task on the Backup Schedules page. For more information, see View backup schedules.

What to do next

Restore MongoDB databases