Help Center> Document Database Service> User Guide (Paris Region) > Backup and Restore> Restoring a Replica Set Instance from a Backup
Updated on 2022-02-22 GMT+08:00

Restoring a Replica Set Instance from a Backup

Scenarios

This section describes how to restore a replica set instance from a backup.

Restoration Precautions

  • Currently, DDS replica set instances only support restoring backups to a new DB instance.
  • When you restore the DB instance from a backup file, a full backup file is downloaded from OBS and then restored to the DB instance at an average speed of 40 MB/s.

Method 1

  1. Log in to the DDS console.
  2. On the Instance Management page, click the target replica set instance.
  3. In the navigation pane on the left, click Backups & Restorations.
  4. On the Backups & Restorations page, locate the target backup in the backup list and click Restore in the Operation column. In the displayed dialog box, click OK.
  5. On the displayed page, create a DB instance using the same configurations as the backup. The new DB instance is independent from the original one.

    • You are recommended to deploy the restored DB instance in a different AZ to ensure that applications will not be adversely affected by the failure in any single AZ.
    • The database type, DB instance type, compatible MongoDB version, storage engine, and storage type must be the same as those of the original and cannot be changed.
    • The storage space is the same as that of the original instance by default. You can only increase the storage space.

Method 2

  1. Log in to the DDS console.
  2. In the navigation pane on the left, click Backup Management.
  3. On the Backup Management page, click the Replica Sets tab, locate the backup to restore, and click Restore in the Operation column. In the displayed dialog box, click OK.
  4. On the displayed page, create a DB instance using the same configurations as the backup. The new DB instance is independent from the original one.

    • You are recommended to deploy the restored DB instance in a different AZ to ensure that applications will not be adversely affected by the failure in any single AZ.
    • The database type, DB instance type, compatible MongoDB version, storage engine, and storage type must be the same as those of the original and cannot be changed.
    • The storage space is the same as that of the original instance by default. You can only increase the storage space.