MongoDB Backup and Restore support matrix¶

Creating and restoring MongoDB backups in PMM currently has the following limitations and requirements:

Physical backups and restores are supported 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.
Creating backups for sharded clusters was included in PMM 2.38 and is available straight from the UI. However, restoring these backup artifacts is only possible via the CLI, using Percona Backup for MongoDB. For information on restoring sharded backups, check the PBM documentation.
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 the 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.

Get expert help¶

If you need assistance, visit the community forum for comprehensive and free database knowledge, or contact our Percona Database Experts for professional support and services.

Community Forum Get a Percona Expert