This topic describes how to configure automatic backup for an ApsaraDB for MongoDB instance. ApsaraDB for MongoDB can automatically back up data based on the default backup policy or the backup policy you specify.
Usage notes
- If the database version of an instance is 3.2 or 3.4, the number of collections and indexes in the instance cannot exceed 10,000. Otherwise, physical backup may fail. If you want to increase this limit, we recommend that you upgrade MongoDB versions to 4.0 or later. Alternatively, you can select the database version 4.0 or 4.2 when you create the instance. For more information, see Upgrade MongoDB versions.
- After the database version is upgraded, the backup files of the original version cannot be used to restore data of the new version.
Automatic backup
- ApsaraDB for MongoDB stores backup files in Object Storage Service (OSS) to reduce the storage usage of ApsaraDB for MongoDB instances.
- Standalone instances can use only snapshot backup, which affects their I/O performance
in the backup process.
Note Snapshot backup retains the status of disk data at a specific point in time.
- Replica set and sharded cluster instances support physical backup.
Note With physical backup, all physical database files in an ApsaraDB for MongoDB instance are backed up. Physical backup runs on the hidden node of an ApsaraDB for MongoDB instance, and does not affect the I/O performance of the primary and secondary nodes. If the data volume is large, backing up your ApsaraDB for MongoDB instance may require a long time.