This topic describes how to restore one or more databases of an ApsaraDB for MongoDB
instance to a new ApsaraDB for MongoDB instance by using a backup created at a specific
point in time. This method is ideal for quick data restoration.
Background information
Instances created after March 26, 2019 support the restoration of one or more databases.
For information about when this feature will be available to instances created before
March 26, 2019, follow the official website.
Prerequisites
- The instance is created after March 26, 2019.
- The instance is located in the China (Qingdao), China (Beijing), China (Zhangjiakou),
China (Hohhot), China (Hangzhou), China (Shanghai), China (Shenzhen), or Singapore
(Singapore) region.
- The instance is a replica set instance.
- The MongoDB version of the instance is 3.4, 4.0, or 4.2.
Note
- If the MongoDB version of the instance is earlier than required versions, you must
upgrade the database version. For more information, see Upgrade MongoDB versions.
- After the MongoDB version is upgraded, the backup files of the original version cannot
be used to restore data of the new version.
- The storage engine of the instance is WiredTiger.
- The backup file list of the instance contains the backup files of the databases you
want to restore.
Precautions
- You can restore databases only from physical backups.
- The time required varies based on factors such as the data volume, task queue status,
and network conditions. When the status of the new instance changes to Running, the restoration is complete.
Billing
When you restore one or more databases, the system creates an instance and you are
charged for the new instance. For more information, see Billing items and pricing.
Note If you want to restore the databases to a pay-as-you-go instance, make sure that your
account has sufficient balance.
Procedure
- Log on to the ApsaraDB for MongoDB console.
- In the upper-left corner of the page, select the resource group and the region of
the target instance.
- In the left-side navigation pane, click Replica Set Instances.
- Find the target instance and click its ID.
- In the left-side navigation pane, click Backup and Recovery.
- On the Backup and Recovery page, click Create Instance By Time Point.
- In the Create Instance By Time Point panel, configure the following parameters.

Parameter |
Description |
Select recovery time point |
Select a point in time from which you want to restore data. You can select a time
point from the last seven days.
Note The time you select must be earlier than the current time and later than the time
when the source instance was created.
|
Select databases to recover |
|
- Click OK.
- On the instance buy page, select a billing method for the new instance.
Note
- Subscription: You must pay for the subscription when you create an instance. This
method is more cost-effective than the pay-as-you-go method. We recommend that you
select this method for long-term use. A longer subscription period enables a larger
discount.
- Pay-as-you-go: You are billed on an hourly basis based on the used resources. We recommend
that you select this billing method for short-term use. You can reduce costs by releasing
your pay-as-you-go instance if it is no longer needed.
- Configure the new instance. For more information, see Create a replica set instance.
Note
- You cannot change Region, Database Version, Storage Engine, or Replication Factor for the new instance.
- To make sure that the new instance has sufficient space for restoration, we recommend
that you set the storage capacity larger than or equal to that of the source instance.
- Click Buy Now.
- On the Confirm Order page, read and select ApsaraDB for MongoDB Agreement of Service, and complete the payment.