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

Restoring Replica Set Instance to a Point in Time

Scenarios

You can restore the data of a replica set instance to a specified time point.

Restoration Precautions

  • Currently, replica set instances only support restoring backups to a new DB instance when performing a point-in-time recovery.
  • The local database is not included in the databases that can be restored to a specified time point.
  • When you enter the time point that you want to restore the DB instance to, DDS downloads the most recent full backup file from OBS to the DB instance. Then, incremental backups are also restored to the specified point in time on the DB instance. Data is restored at an average speed of 30 MB/s.

Constraints

Data can be restored to a specified time point only after the automated backup policy is enabled.

Procedure

  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, click Restore to Point In Time.
  5. Select the date and time range, select or enter a time point within the acceptable range. Then, click OK.
  6. 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.

Parent topic: Backup and Restore