About backups

Backing up your database protects your data from loss and corruption, helps ensure business continuity, and lets you quickly recover if something goes wrong.

How backups work

The Operator stores your MySQL backups outside the Kubernetes cluster on cloud storage. You can use:

• Amazon S3 or S3-compatible storage
• Azure Blob Storage
• Google Cloud Storage

The Operator creates physical backups using Percona XtraBackup . Here’s how it works:

1. Each database Pod includes a sidecar container called xtrabackup that runs an HTTP server.
2. When you create a backup, the Operator creates a Job that sends an HTTP request to the backup source pod.
3. The xtrabackup container receives the request and starts the backup process.

The following diagram outlines this workflow:

Configuring backups

You configure backups in the backup section of your deploy/cr.yaml file. This section includes:

• The backup.enabled key, which you set to true to enable backups
• The storages subsection, where you configure access to your cloud storage

Backup types

You can create backups in two ways:

• Scheduled backups: Configure these in your deploy/cr.yaml file. The Operator runs them automatically at the times you specify.
• On-demand backups: Create these manually whenever you need them. You configure them in the deploy/backup/backup.yaml file.

---

Last update: December 2, 2025
Created: December 2, 2025