Custom options for xtrabackup not working during the backup phase
General
Escalation
General
Escalation
Description
When doing On-Demand backups , and adding an xtrabackup custom option for the backup phase. It doesn't apply to the backup.
How to reproduce:
Create an On-Demand backup with the --history flag; it doesn’t create the PERCONA_SCHEMA.history table.
On-Demand backup yaml used:
Completed backup:
Checking if the history was correctly set to the pod:
Checking if the database exists:
Environment
None
AFFECTED CS IDs
CS0052348
Activity
Slava Sarzhan
February 11, 2025 at 10:44 AM
We will update the documentation. I have removed the incorrect example. If you want to monitor the status of the backups, you can use k8s objects for these needs:
Slava Sarzhan
January 29, 2025 at 1:55 PM
Hi ,
We do not use xtrabackup for backups in PXC operator at all (we use it only for restoration). That is why this option does not work. You can see how operator performs backup using this link:
Our new PS operator has a different architecture and uses xtrabackup, but it is not a GA now.
P.S. we need to remove section from backup.yaml to avoid misunderstanding.
When doing On-Demand backups , and adding an xtrabackup custom option for the backup phase. It doesn't apply to the backup.
How to reproduce:
Create an On-Demand backup with the --history flag; it doesn’t create the PERCONA_SCHEMA.history table.
On-Demand backup yaml used:
Completed backup:
Checking if the history was correctly set to the pod:
Checking if the database exists: