ApsaraDB for MongoDB:Restoration solution overview

Restoration method

Instance architecture

Scenario

Remarks

Restore backup data to a new ApsaraDB for MongoDB instance by backup point

• Standalone instances

• Replica set instances

Applicable to scenarios where an entire instance needs to be restored but data timeliness is not a key requirement.

A new instance is created based on the backup data and data is restored to the new instance.

• The major version of the new instance must be the same as that of the original instance. You must select a zone based on the MongoDB version of the original instance. Instances of different MongoDB versions can be deployed in different zones. For more information about the MongoDB versions supported in different zones, see Limits.

• The storage space of the new instance must be larger than or equal to that of the original instance.

• The backup data of an instance cannot be restored if the major version of the instance is upgraded after the backup data is generated.

• By default, the new instance runs the latest kernel version.

Restore backup data to a new ApsaraDB for MongoDB instance by point in time

• Replica set instances

• Sharded cluster instances

Applicable to scenarios where data of multiple databases in an instance or data of the entire instance needs to be restored to a specific point in time.

Restore one or more databases of an ApsaraDB for MongoDB instance

Replica set instances that meet the following requirements:

• The instances are created after March 26, 2019.

• The instances are deployed in the China (Qingdao), China (Beijing), China (Zhangjiakou), China (Hohhot), China (Hangzhou), China (Shanghai), China (Shenzhen), or Singapore region.

• The instances run MongoDB 4.2 or earlier.

• The instances use local SSDs.

• The storage engine of the instances is WiredTiger.

Applicable to scenarios where one or more databases need to be quickly restored. For example, you can use this solution if you deleted a collection or document by mistake.

Restoration method

Instance architecture

Remarks

Restore data of an ApsaraDB for MongoDB instance to a self-managed MongoDB database by using logical backup

• Replica set instances that run MongoDB 4.2 or earlier and use local SSDs.

• Sharded cluster instances that run MongoDB 4.2 or earlier and use local SSDs.

The mongorestore tool of an earlier version is not supported in MongoDB of a later version. We recommend that you select a mongorestore version that is compatible with your MongoDB version. For more information, see mongorestore.

Restore data of an ApsaraDB for MongoDB instance to a self-managed MongoDB database by using physical backup

Replica set instances that meet the following requirements:

• The Transparent Data Encryption (TDE) feature is not enabled for the instances. For more information about TDE, see Configure TDE for an ApsaraDB for MongoDB instance.

• The storage engine of the instances is WiredTiger or RocksDB.

N/A