ApsaraDB for MongoDB:Limits

Item

Limits on instances that use cloud disks

Limits on instances that use local disks

Instance deployment

Replica set instances can be deployed in specific regions and zones. For more information, see Replica set instances.

Minor engine version

If the minor version of an instance expires or is not maintained, ApsaraDB for MongoDB automatically updates the minor version of the instance to the latest version when you perform specific operations. This ensures greater instance performance and stability. These operations include version upgrade, data migration, configuration change, and data restoration.

Database connection

The network type cannot be switched.

• The network type cannot be switched from virtual private cloud (VPC) to the classic network.

• The network type can be switched from the classic network to VPC. For more information, see Switch the network type of an ApsaraDB for MongoDB instance from classic network to VPC.

Data backup

• Physical Backup or Logical Backup is not supported.

• Only Snapshot Backup is supported.

  Note

  A snapshot is a point-in-time backup of disk data.

• Snapshot Backup is not supported.

• Physical Backup and Logical Backup are supported.

  Note

  If the engine version of an instance is MongoDB 3.2 or 3.4, the total number of collections and indexes in the instance cannot exceed 10,000. Otherwise, physical backup may fail. If the number of collections and indexes in your instance exceeds 10,000, we recommend that you select MongoDB 4.0 or 4.2 for an instance when you create the instance, or upgrade the instance to MongoDB 4.0 or 4.2. For more information, see Upgrade the major version of an ApsaraDB for MongoDB instance.

Data security

• Transparent Data Encryption (TDE) is not supported.

• The audit log feature can be enabled for ApsaraDB for MongoDB instances. For more information, see Enable the audit log feature.

• Whitelists are supported. For more information, see Configure a whitelist for an ApsaraDB for MongoDB instance.

• SSL encryption is supported. For more information, see Configure SSL encryption for an ApsaraDB for MongoDB instance.

• Whitelists are supported. For more information, see Configure a whitelist for an ApsaraDB for MongoDB instance.

• SSL encryption is supported. For more information, see Configure SSL encryption for an ApsaraDB for MongoDB instance.

• TDE is supported. For more information, see Configure TDE for an ApsaraDB for MongoDB instance.

• The audit log feature can be enabled for ApsaraDB for MongoDB instances. For more information, see Enable the audit log feature.

Log management

N/A

CloudDBA

N/A

Data migration and synchronization

• The following methods can be used to migrate data of a replica set instance:

  • Migrate a self-managed MongoDB database to ApsaraDB for MongoDB

    • Migrate an ECS-hosted self-managed MongoDB database that uses the standalone or replica set architecture to ApsaraDB for MongoDB

    • Migrate a self-managed standalone MongoDB database to ApsaraDB for MongoDB by using DTS

    • Migrate a self-managed MongoDB database to ApsaraDB for MongoDB by using tools provided by MongoDB

  • Migrate data from a MongoDB database hosted on a third-party cloud to an ApsaraDB for MongoDB instance

    • Migrate an Amazon DynamoDB database to ApsaraDB for MongoDB by using NimoShake

    • Migrate data from MongoDB Atlas to ApsaraDB for MongoDB by using mongodump and mongorestore

    • Migrate data from a MongoDB Atlas database to an ApsaraDB for MongoDB instance

  • Migrate data between ApsaraDB for MongoDB instances

    • Migrate data from an ApsaraDB for MongoDB replica set instance to an ApsaraDB for MongoDB sharded cluster instance

    • Migrate data between ApsaraDB for MongoDB instances of different Alibaba Cloud accounts

    • Migrate data between ApsaraDB for MongoDB instances across regions

  • Migrate data from an ApsaraDB for MongoDB instance to a self-managed MongoDB database

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

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

• The following methods can be used to synchronize data between replica set instances:

  • Synchronize data from an ApsaraDB for MongoDB instance (replica set architecture) to another ApsaraDB for MongoDB instance (replica set architecture or sharded cluster architecture)

  • Use MongoShake to implement one-way synchronization between ApsaraDB for MongoDB replica set instances

  • Use MongoShake to implement delayed synchronization among ApsaraDB for MongoDB instances

Instance connection

The following methods can be used to connect to a replica set instance:

• Connect to an ApsaraDB for MongoDB replica set instance by using DMS

• Connect to a replica set instance by using the mongo shell

• Connect to a replica set instance by using the program code