Skip to content

About backups

You can backup your data in two ways:

  • On-demand. You can do them manually at any moment.
  • Scheduled backups. Configure backups and their schedule in the deploy/cr.yaml. The Operator makes them automatically according to the specified schedule.

To make backups and restores, the Operator uses the Percona Backup for MongoDB tool.

Backup storage

You can store Percona Server for MongoDB backups outside the Kubernetes cluster using the following remote backup storages:

image

Backup types

The Operator can do either logical or physical backups.

  • Logical backup means querying the Percona Server for MongoDB for the database data and writing the retrieved data to the remote backup storage.

  • Physical backup means copying physical files from the Percona Server for MongoDB dbPath data directory to the remote backup storage.

Logical backups use less storage, but are much slower than physical backup/restore.

Also, logical backups are stable, while physical backups are available since the Operator version 1.14.0 and still have the technical preview stauts.

Warning

Logical backups made with the Operator versions before 1.9.0 are incompatible for restore with the Operator 1.9.0 and later. That is because Percona Backup for MongoDB 1.5.0 used by the newer Operator versions processes system collections Users and Roles differently. The recommended approach is to make a fresh backup after upgrading the Operator to version 1.9.0.

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. Join K8S Squad to benefit from early access to features and “ask me anything” sessions with the Experts.


Last update: 2024-01-30