MongoDB Backup and Restore support matrix
Creating and restoring MongoDB backups in PMM currently has the following limitations and requirements:
- Restoring on different Replica set/Cluster is not supported.
- Physical backups and restores suppoted only for Percona Server for MongoDB
- Physical restores are not supported for deployments with arbiter nodes. For more information, see the Percona Backup for MongoDB documentation.
- All types of backups on sharded cluster setups are currently not supported.
- Retention policy is supported only for snapshot types of scheduled backups and for the S3-compatible storage type.
- Before restoring, make sure to prevent clients from accessing database.
Support matrix
Backup: Logical
| Full or PITR |
Storage type (S3 or Local) |
Support level |
| PITR |
S3 |
Full |
| PITR |
Local |
Full |
| Full |
S3 |
Full |
| Full |
Local |
Full |
Backup: Physical
| Full or PITR |
Storage type (S3 or Local) |
Support level |
| PITR |
S3 |
No |
| PITR |
Local |
No |
| Full |
S3 |
Full |
| Full |
Local |
Full |
Restore: Logical
| Full or PITR |
Storage type (S3 or Local) |
Support level |
| PITR |
S3 |
Full |
| PITR |
Local |
No |
| Full |
S3 |
Full |
| Full |
Local |
Full |
Restore: Physical
| Full or PITR |
Storage type (S3 or Local) |
Support level |
| PITR |
S3 |
No |
| PITR |
Local |
No |
| Full |
S3 |
Partial* |
| Full |
Local |
Partial* |
* Partial support for non-containerized deployments and NO support for containerized deployments.
Last update:
2023-03-30
